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 Contacts API

The Contacts API from Front — 6 operation(s) for contacts.

Front Contacts 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 Contacts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 11 operations across 6 paths, and defines 13 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.

11 operations 6 paths 13 schemas 1 DELETE5 GET1 PATCH4 POST

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 Contacts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (http). By default, every request must be authenticated.

Paths & Operations 11

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

Contacts 11
GET
/contacts
List contacts
list-contacts 5 params → 200
POST
/contacts
Create contact
create-contact body → 201
POST
/contacts/merge
Merge contacts
merge-contacts body → 200
GET
/contacts/{contact_id}
Get contact
get-contact 1 param → 200
PATCH
/contacts/{contact_id}
Update a contact
update-a-contact 1 param body → 204
DELETE
/contacts/{contact_id}
Delete a contact
delete-a-contact 1 param → 204
GET
/contacts/{contact_id}/conversations
List contact conversations
list-contact-conversations 4 params → 200
GET
/teammates/{teammate_id}/contacts
List teammate contacts
list-teammate-contacts 6 params → 200
POST
/teammates/{teammate_id}/contacts
Create teammate contact
create-teammate-contact 1 param body → 201
GET
/teams/{team_id}/contacts
List team contacts
list-team-contacts 6 params → 200
POST
/teams/{team_id}/contacts
Create team contact
create-team-contact 1 param body → 201

Schemas 13

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

ConversationResponse
object
18 properties 13 required
LinkResponse
object
A link used to connect a Front conversation to an external resource.
6 properties 6 required
RecipientResponse
object
4 properties 4 required
Reminder
object
4 properties 1 required
TeammateResponse
object
A teammate is a user in Front.
11 properties 12 required
ContactHandle
object
2 properties 2 required
ContactListResponses
object
4 properties
MergeContacts
object
2 properties 1 required
TagResponse
object
A tag is a label that can be used to classify conversations.
9 properties 7 required
ContactResponse
object
11 properties
CreateContact
1 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…
Contact
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

front-contacts-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 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.