How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Uplika

Uplika Inbox and contacts API

The Inbox and contacts API from Uplika — 19 operation(s) for inbox and contacts.

Documentation Provider Profile APIs.io OpenAPI GitHub

Uplika Inbox and contacts API is one of 10 APIs that Uplika publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Inbox and contacts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 22 operations across 19 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.uplika.com.

22 operations 19 paths 1 schemas 2 DELETE7 GET1 PATCH12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.uplika.com
Authentication
HTTP Bearer
Contact
https://uplika.com/en/docs
Resource Areas
1

Authentication & Security 1

Uplika Inbox and contacts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey). By default, every request must be authenticated.

  • apiKey — An API key from the dashboard.

Paths & Operations 22

Across 19 paths, the API surfaces 22 operations — 2 DELETE, 7 GET, 1 PATCH, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Inbox and contacts 22
GET
/v1/conversations
Conversations, latest message first.
getV1Conversations 9 params body → default
GET
/v1/conversations/{id}
One conversation with its contact and messages
getV1ConversationsById 1 param → default
POST
/v1/conversations/{id}/messages
Reply as the account: a DM in DM conversations, a public reply in mention and…
postV1ConversationsByIdMessages 1 param body → default
POST
/v1/conversations/{id}/drafts/{messageId}
Send a draft an automation prepared for approval, optionally with edited text
postV1ConversationsByIdDraftsByMessageId 2 params → default
DELETE
/v1/conversations/{id}/drafts/{messageId}
Throw a draft away without sending it
deleteV1ConversationsByIdDraftsByMessageId 2 params → default
POST
/v1/inbox/sync
Import recent conversations from the channel for one account
postV1InboxSync → default
POST
/v1/conversations/{id}/read
Mark it read
postV1ConversationsByIdRead 1 param → default
POST
/v1/conversations/{id}/open
Reopen a closed conversation
postV1ConversationsByIdOpen 1 param → default
POST
/v1/conversations/{id}/close
Close it. It moves out of the open list
postV1ConversationsByIdClose 1 param → default
POST
/v1/conversations/{id}/star
Star it
postV1ConversationsByIdStar 1 param → default
POST
/v1/conversations/{id}/unstar
Remove the star
postV1ConversationsByIdUnstar 1 param → default
POST
/v1/conversations/{id}/assign
Assign it to a person (userId, defaults to you)
postV1ConversationsByIdAssign 1 param → default
POST
/v1/conversations/{id}/unassign
Clear the assignment
postV1ConversationsByIdUnassign 1 param → default
GET
/v1/contacts
People who wrote to your accounts, with tags, fields, opt-out and whether they…
getV1Contacts 5 params body → default
GET
/v1/contacts/{id}
One contact and their conversations
getV1ContactsById 1 param → default
PATCH
/v1/contacts/{id}
Set tags, custom fields or opt-out
patchV1ContactsById 1 param body → default
DELETE
/v1/contacts/{id}
Delete the contact and its conversations and messages on our side.
deleteV1ContactsById 1 param → default
POST
/v1/contacts/{id}/refresh
Read the profile again from the channel
postV1ContactsByIdRefresh 1 param → default
GET
/v1/accounts/{id}/audience
Follower totals, and on Threads a demographic breakdown.
getV1AccountsByIdAudience 1 param → default
GET
/v1/messaging/violations
Messages an automation did not send because a channel rule stopped it, newest…
getV1MessagingViolations → default
GET
/v1/threads/pending-replies
Replies held for approval on a Threads account
getV1ThreadsPendingReplies 1 param body → default
POST
/v1/threads/pending-replies/{replyId}
Approve or ignore one held reply
postV1ThreadsPendingRepliesByReplyId 1 param body → default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uplika-com-inbox-and-contacts-api-openapi.yml Raw ↑

Other APIs Uplika publishes across the network.

Uplika API
AE Profile APIs.io
Uplika Automations API
AE Profile APIs.io
Uplika Connecting channels API
AE Profile APIs.io
Uplika Errors API
AE Profile APIs.io
Uplika Media API
AE Profile APIs.io
Uplika Platforms API
AE Profile APIs.io
Uplika Posts API
AE Profile APIs.io
Uplika Replies and insights API
AE Profile APIs.io
Uplika Troubleshooting and FAQ API
AE Profile APIs.io
#Inbox and contacts
← Back to U APIs
API Details
ID
uplika-com:uplika-com-inbox-and-contacts-api
Base URL
https://api.uplika.com
Docs
https://uplika.com/en/docs
Provider
Uplika
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=uplika-com-inbox-and-contacts-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uplika-com-inbox-and-contacts-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Uplika Inbox and contacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.