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

Unified.to contact API

The contact API from Unified.to — 6 operation(s) for contact.

Unified.to contact API is one of 140 APIs that Unified.to publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 13 JSON Schema definitions.

Tagged areas include Contact. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 13 JSON Schemas.

This API exposes 18 operations across 6 paths, and defines 31 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 3 base URLs: https://api.unified.to, https://api-eu.unified.to, https://api-au.unified.to.

18 operations 6 paths 31 schemas 3 DELETE6 GET3 PATCH3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Servers
https://api.unified.to
https://api-eu.unified.to
https://api-au.unified.to
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Unified.to contact API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (jwt). By default, every request must be authenticated.

Paths & Operations 18

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

contact 18
GET
/accounting/{connection_id}/contact
List all contacts
listAccountingContacts 11 params → 200
POST
/accounting/{connection_id}/contact
Create a contact
createAccountingContact 3 params body → 200
DELETE
/accounting/{connection_id}/contact/{id}
Remove a contact
removeAccountingContact 2 params → 200default
GET
/accounting/{connection_id}/contact/{id}
Retrieve a contact
getAccountingContact 4 params → 200
PATCH
/accounting/{connection_id}/contact/{id}
Update a contact
patchAccountingContact 4 params body → 200
PUT
/accounting/{connection_id}/contact/{id}
Update a contact
updateAccountingContact 4 params body → 200
GET
/crm/{connection_id}/contact
List all contacts
listCrmContacts 12 params → 200
POST
/crm/{connection_id}/contact
Create a contact
createCrmContact 3 params body → 200
DELETE
/crm/{connection_id}/contact/{id}
Remove a contact
removeCrmContact 2 params → 200default
GET
/crm/{connection_id}/contact/{id}
Retrieve a contact
getCrmContact 4 params → 200
PATCH
/crm/{connection_id}/contact/{id}
Update a contact
patchCrmContact 4 params body → 200
PUT
/crm/{connection_id}/contact/{id}
Update a contact
updateCrmContact 4 params body → 200
GET
/uc/{connection_id}/contact
List All Contacts
listUcContacts 10 params → 200
POST
/uc/{connection_id}/contact
Create a Contact
createUcContact 3 params body → 200
DELETE
/uc/{connection_id}/contact/{id}
Remove a Contact
removeUcContact 2 params → 200default
GET
/uc/{connection_id}/contact/{id}
Retrieve a Contact
getUcContact 4 params → 200
PATCH
/uc/{connection_id}/contact/{id}
Update a Contact
patchUcContact 4 params body → 200
PUT
/uc/{connection_id}/contact/{id}
Update a Contact
updateUcContact 4 params body → 200

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are AccountingContact (23 properties), CrmContact (19 properties), UcContact (11 properties), property_AccountingContact_billing_address (8 properties). Each schema is shown below with its type and property counts.

AccountingContactPaymentMethod
object
4 properties 1 required
CrmEmail
object
2 properties
CrmContacts
array
UcEmail
object
2 properties 1 required
UcTelephone
object
2 properties 1 required
AccountingEmail
object
2 properties
property_AccountingContact_telephones
array
AccountingContact
object
23 properties
property_UcContact_emails
array
An array of email addresses for this contact
property_AccountingContact_payment_methods
array
property_UcContact_telephones
array
An array of telephones for this contact
property_AccountingAssociatedContact_emails
array
property_AccountingContact_emails
array
CrmTelephone
object
2 properties 1 required
UcContacts
array
property_CrmContact_link_urls
array
Additional URLs associated with the contact e.g., LinkedIn, website, etc
AccountingContacts
array
CrmContact
object
A contact represents a person that optionally is associated with a deal and/or a company
19 properties
property_CrmContact_deal_ids
array
An array of deal IDs associated with this contact
property_AccountingContact_billing_address
object
8 properties
property_CrmContact_address
object
8 properties
property_CrmContact_company_ids
array
An array of company IDs associated with this contact
property_AccountingContact_shipping_address
object
8 properties
CrmMetadata
object
6 properties
property_CrmContact_telephones
array
An array of telephones for this contact
AccountingTelephone
object
2 properties
property_CrmContact_metadata
array
AccountingAssociatedContact
object
3 properties
property_CrmContact_emails
array
An array of email addresses for this contact
property_AccountingContact_associated_contacts
array
UcContact
object
A contact represents a person that optionally is associated with a call
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unified-to-contact-api-openapi.yml Raw ↑

Other APIs Unified.to publishes across the network.

Unified.to
Unified.to Authentication API
Unified.to account API
Unified.to accounting API
Unified.to activity API
Unified.to ad API
Unified.to ads API
Unified.to apicall API
Unified.to application API
Unified.to applicationstatus API
Unified.to assessment API
Unified.to ats API
Where this information came from

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