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

TrustLayer contacts API

The contacts API from TrustLayer — 4 operation(s) for contacts.

TrustLayer contacts API is one of 21 APIs that TrustLayer 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 and API documentation.

This API exposes 10 operations across 4 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: http://localhost:4000/v1, https://api.trustlayer.io/v1.

10 operations 4 paths 20 schemas 2 DELETE4 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.trustlayer.io/v2
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

TrustLayer contacts API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Token). By default, every request must be authenticated.

Paths & Operations 10

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

contacts 10
GET
/contacts/{contactId}deprecated
Fetch a party contact's information
get-contacts-id 2 params → 200
PATCH
/contacts/{contactId}deprecated
Update a party contact's information
patch-contacts-id 1 param body → 200
DELETE
/contacts/{contactId}deprecated
Remove contact information from a party
delete-contacts-id 1 param → 200
POST
/parties/{partyId}/contactsdeprecated
Create a party contact
post-parties-id-contacts 1 param body → 201
GET
/parties/{partyId}/contactsdeprecated
List a party's contacts
get-parties-id-contacts 1 param → 200
GET
/contacts
List contacts in the caller's organization. Results are always scoped to the caller's organization. Supports filtering, sorting, and pagination via limit and skip. Filtering: id (objectId), createdAt…
10 params → 200400401403404500
POST
/contacts
Create a new contact in the caller's organization. The owning organization is derived from the access token and cannot be set in the body. Returns the new contact's identifier.
body → 201400401403404500
GET
/contacts/{id}
Read a single contact by id, scoped to the caller's organization. Use the fields query parameter to limit the response to a projection of the contact.
2 params → 200400401403404500
PATCH
/contacts/{id}
Partially update a contact. Any subset of writable fields may be provided; omitted fields are left unchanged. Returns the contact's identifier.
1 param body → 200400401403404500
DELETE
/contacts/{id}
Delete a contact by ID. The contact must not be assigned to any primary records — if it is still referenced, the request returns 409 with the referencing record ids in the error details. Note: deleti…
1 param → 200400401403404409500

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are document (23 properties), party (20 properties), project (13 properties), contact (13 properties). Each schema is shown below with its type and property counts.

contact-update
object
10 properties
reference
object
Generic object reference
2 properties
compliance-profile
object
6 properties
objectId
string
collection-meta
object
4 properties
contact-create
object
10 properties 1 required
compliance-document
object
3 properties
taggging-full
object
6 properties
custom-field
object
9 properties
party-type
object
5 properties
user
object
5 properties
party
object
20 properties
taggging
object
5 properties
response-status
string
The possible values are "success", "fail", and "error".
objectIdInput
string
contact
object
13 properties
document
object
23 properties
document-type
object
5 properties 4 required
compliance-status
object
8 properties 5 required
project
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trustlayer-contacts-api-openapi.yml Raw ↑

Other APIs TrustLayer publishes across the network.

TrustLayer Auth API
TrustLayer branding API
TrustLayer compliance-profiles API
TrustLayer Context Objects API
TrustLayer Context Records API
TrustLayer custom-fields API
TrustLayer Document Types API
TrustLayer documents API
TrustLayer Parties API
TrustLayer party-types API
TrustLayer Policies API
TrustLayer Primary Objects API
Where this information came from

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