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

Supaglue Contacts API

The `Contact` Common Object represents a "contact" in CRMs.

Supaglue Contacts API is one of 41 APIs that Supaglue publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 0.25.7.

Requests are made against 3 base URLs: https://api.supaglue.io/crm/v2, https://api.supaglue.io/engagement/v2, https://api.supaglue.io/ticketing/v2.

6 operations 4 paths 17 schemas 2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.25.7
Base URL
https://api.supaglue.io/crm/v2
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Supaglue Contacts API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key).

  • x-api-key — API key to allow developers to access the API

Paths & Operations 6

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

Contacts 6

The Contact Common Object represents a "contact" in CRMs.

POST
/contacts
Create contact
createContact 2 params body → 201400401403404409422499
GET
/contacts
List contacts
listContacts 8 params → 200400401403404499500501
POST
/contacts/_search
Search contacts
searchContacts 6 params body → 200400401403404409422499
POST
/contacts/_upsert
Upsert contact
upsertContact 2 params body → 201400401403404409422499
GET
/contacts/{contact_id}
Get contact
getContact 5 params → 200400401403404499500501
PATCH
/contacts/{contact_id}
Update contact
updateContact 3 params body → 200400401403404409422499

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are contact_2 (18 properties), contact (15 properties), create_update_contact (9 properties), create_contact (9 properties). Each schema is shown below with its type and property counts.

email_addresses
array
lifecycle_stage
stringnull
addresses
array
errors
array
contact
object
15 properties 15 required
create_update_contact
object
9 properties
warnings
array
pagination
object
3 properties 2 required
custom_fields
object
Custom properties to be inserted that are not covered by the common object. Object keys must match exactly to the corresponding provider API.
created_record
object
1 property 1 required
phone_numbers
array
email_addresses_2
array
contact_2
object
18 properties 16 required
create_contact
object
9 properties
address
objectnull
6 properties 6 required
phone_numbers_2
array
contact_3
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

supaglue-contacts-api-openapi.yml Raw ↑

Other APIs Supaglue publishes across the network.

Supaglue Accounts API
Supaglue Associations API
Supaglue AssociationSchemas API
Supaglue Attachments API
Supaglue Collections API
Supaglue Comments API
Supaglue Connections API
Supaglue ConnectionSyncConfigs API
Supaglue Customers API
Supaglue CustomObjects API
Supaglue CustomObjectSchemas API
Supaglue Destinations API
Where this information came from

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