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

Front Conversations API

The Conversations API from Front — 11 operation(s) for conversations.

Front Conversations API is one of 39 APIs that Front publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

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

This API exposes 18 operations across 11 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api2.frontapp.com.

18 operations 11 paths 20 schemas 4 DELETE7 GET2 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api2.frontapp.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 18

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

Conversations 18
GET
/conversations
List conversations
list-conversations 5 params → 200
POST
/conversations
Create discussion conversation
create-conversation body → 201
GET
/conversations/search/{query}
Search conversations
search-conversations 3 params → 200
GET
/conversations/{conversation_id}
Get conversation
get-conversation-by-id 1 param → 200301
PATCH
/conversations/{conversation_id}
Update conversation
update-conversation 1 param body → 204301400
DELETE
/conversations/{conversation_id}
Delete conversation
delete-conversation 1 param → 204400403404
PUT
/conversations/{conversation_id}/assignee
Update conversation assignee
update-conversation-assignee 1 param body → 204301
GET
/conversations/{conversation_id}/events
List conversation events
list-conversation-events 3 params → 200301
GET
/conversations/{conversation_id}/followers
List conversation followers
list-conversation-followers 1 param → 200301
POST
/conversations/{conversation_id}/followers
Add conversation followers
add-conversation-followers 2 params body → 204301
DELETE
/conversations/{conversation_id}/followers
Delete conversation followers
delete-conversation-followers 1 param body → 204301
GET
/conversations/{conversation_id}/inboxes
List conversation inboxes
list-conversation-inboxes 1 param → 200301
POST
/conversations/{conversation_id}/links
Add conversation link
add-conversation-link 1 param body → 204301
DELETE
/conversations/{conversation_id}/links
Remove conversation links
remove-conversation-links 1 param body → 204301
GET
/conversations/{conversation_id}/messages
List conversation messages
list-conversation-messages 5 params → 200301
PATCH
/conversations/{conversation_id}/reminders
Update conversation reminders
update-conversation-reminders 1 param body → 204301
POST
/conversations/{conversation_id}/tags
Add conversation tag
add-conversation-tag 1 param body → 204301
DELETE
/conversations/{conversation_id}/tags
Remove conversation tag
remove-conversation-tag 1 param body → 204301

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ConversationResponse (18 properties), MessageResponse (18 properties), TeammateResponse (11 properties), SignatureResponse (9 properties). Each schema is shown below with its type and property counts.

ConversationResponse
object
18 properties 13 required
ResourceID
string
UpdateConversationReminders
object
3 properties 2 required
UpdateConversation
object
6 properties
LinkResponse
object
A link used to connect a Front conversation to an external resource.
6 properties 6 required
RecipientResponse
object
4 properties 4 required
RuleResponse
object
5 properties 5 required
EventResponse
object
An event is created every time something interesting is happening in Front.
7 properties
SignatureResponse
object
9 properties 9 required
Reminder
object
4 properties 1 required
InboxResponse
object
6 properties
TagIds
object
1 property 1 required
TeammateResponse
object
A teammate is a user in Front.
11 properties 12 required
CommentResponse
object
7 properties 6 required
TagResponse
object
A tag is a label that can be used to classify conversations.
9 properties 7 required
MessageResponse
object
18 properties
UpdateConversationAssignee
object
1 property 1 required
Attachment
object
6 properties 6 required
CustomFieldParameter
object
An object whose key is the name property defined for the custom field in the Front UI. The value of the key must use the same type specified for the custom fie…
CreateConversation
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

front-conversations-api-openapi.yml Raw ↑

Other APIs Front publishes across the network.

Front Plugin SDK
Front Chat Widget
Front Connectors
Front Accounts API
Front Analytics API
Front Application Message Templates API
Front Applications API
Front Attachments API
Front Calls API
Front Channels API
Front Comments API
Front Contact Groups API
Where this information came from

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