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 Context Records API

The Context Records API from TrustLayer — 7 operation(s) for context records.

TrustLayer Context Records API is one of 21 APIs that TrustLayer publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Context Records. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 16 operations across 7 paths, and defines 2 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.

16 operations 7 paths 2 schemas 3 DELETE7 GET2 PATCH3 POST1 PUT

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 Context Records 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 16

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

Context Records 16
POST
/context-records
Create a new context record in the caller's organization. The owning organization is derived from the access token. Returns the new record's identifier.
body → 201400401403404500
GET
/context-records
List context records in the caller's organization. Results are always scoped to the caller's organization. Supports pagination via limit and skip. Filtering: id (objectId), createdAt (date), updatedA…
14 params → 200400401403404500
DELETE
/context-records/{id}
Delete a context record. Returns the deleted record id on success. Deleting a record that does not exist returns 404 with the shared NotFoundError shape.
1 param → 200400401403404500
GET
/context-records/{id}
Read a single context record by id, scoped to the caller's organization. Use the fields query parameter to limit the response to a projection of the record.
2 params → 200400401403404500
PATCH
/context-records/{id}
Partially update a context record. Any subset of writable fields may be provided; omitted fields are left unchanged. Returns the full updated record.
1 param body → 200400401403404500
DELETE
/context-records/{id}/attributes/{attributeId}
Delete an attribute (custom field value) from a context record. Returns 404 when the context record or the specific attribute does not exist.
2 params → 200400401403404500
GET
/context-records/{id}/attributes/{attributeId}
Read a single attribute (custom field value) embedded in a context record. Returns 404 when the context record or the specific attribute does not exist.
2 params → 200400401403404500
PUT
/context-records/{id}/attributes/{attributeId}
Create or replace an attribute (custom field value) on a context record. This is a full replacement — omitting value or optionIds clears that field. Returns 404 when the context record or the referen…
2 params body → 200400401403404500
GET
/context-records/{id}/attributes
List attributes (custom field values) embedded in a context record. Attributes are stored as an embedded array on the record — there is no separate filtering beyond pagination. Results are scoped to…
3 params → 200400401403404500
GET
/context-records/{id}/request-records
List request records scoped to a specific context record. The contextRecordId filter is always fixed to the :id path parameter and cannot be overridden by the caller. Supports pagination via limit an…
14 params → 200400401403404500
POST
/context-records/{id}/request-records
Create a new request record and assign it to a context record. The context record is identified by the :id path parameter. Returns the new request record's identifier.
1 param body → 201400401403404500
GET
/context-records/{id}/request-records/{recordId}
Read a single request record scoped to a specific context record. Returns 404 if the request record does not exist or does not belong to the specified context record.
3 params → 200400401403404500
PATCH
/context-records/{id}/request-records/{recordId}
Partially update a request record scoped to a specific context record. Any subset of the request body fields may be provided; omitted fields are left unchanged. Returns the full updated request recor…
2 params body → 200400401403404500
DELETE
/context-records/{id}/request-records/{recordId}
Delete a request record scoped to a specific context record. Returns 404 if the request record does not exist or does not belong to the specified context record.
2 params → 200400401403404500
GET
/context-records/{id}/request-records/{recordId}/compliance-certificate
Get compliance certificate for a request record in a context record
3 params → 200400401403404500
POST
/context-records/{id}/request-records/{recordId}/compliance-certificate
Create compliance certificate for a request record in a context record
2 params body → 201400401403404500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

objectIdInput
string
objectId
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trustlayer-context-records-api-openapi.yml Raw ↑

Other APIs TrustLayer publishes across the network.

TrustLayer Auth API
TrustLayer branding API
TrustLayer compliance-profiles API
TrustLayer contacts API
TrustLayer Context Objects 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 Context Records 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.