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

Papercups Conversations API

Threads of messages between customers and agents.

Papercups Conversations API is one of 7 APIs that Papercups publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://app.papercups.io/api/v1, https://{host}/api/v1.

5 operations 2 paths 5 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://app.papercups.io/api/v1
Authentication
HTTP Bearer
Contact
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Papercups Conversations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer API key (personal API key / token) from the Papercups dashboard, sent as Authorization: Bearer .

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Conversations 5

Threads of messages between customers and agents.

GET
/conversations
List conversations
listConversations 4 params → 200401
POST
/conversations
Create a conversation
createConversation body → 201401
GET
/conversations/{id}
Retrieve a conversation
getConversation 1 param → 200404
PUT
/conversations/{id}
Update a conversation
updateConversation 1 param body → 200404
DELETE
/conversations/{id}
Delete a conversation
deleteConversation 1 param → 204404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Conversation (10 properties), ConversationInput (5 properties), Error (1 property), ConversationResponse (1 property). Each schema is shown below with its type and property counts.

ConversationListResponse
object
1 property
Conversation
object
10 properties
ConversationInput
object
5 properties
ConversationResponse
object
1 property
Error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

papercups-conversations-api-openapi.yml Raw ↑

Other APIs Papercups publishes across the network.

Papercups Notifications & Webhooks API
Papercups Realtime Chat API (WebSocket / Phoenix Channels)
Papercups Webhooks
Papercups Customers API
Papercups Messages API
Papercups Users API
Where this information came from

This is an independent, third-party profile of Papercups Conversations 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.