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 compliance-profiles API

The compliance-profiles API from TrustLayer — 8 operation(s) for compliance-profiles.

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

Tagged areas include compliance-profiles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 14 operations across 8 paths, and defines 19 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.

14 operations 8 paths 19 schemas 2 DELETE6 GET2 PATCH4 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 compliance-profiles 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 14

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

compliance-profiles 14
GET
/compliance-profilesdeprecated
List global compliance profiles
get-compliance-profiles 4 params → 200
POST
/compliance-profiles
Create a new Global compliance profile in the caller's organization. The owning organization is derived from the access token. Returns the created profile.
body → 201400401403404500
GET
/compliance-profiles/{profileId}deprecated
Fetch a compliance profile
get-compliance-profiles-id 1 param → 200
GET
/projects/{projectId}/compliance-profiledeprecated
Fetch compliance profile for project
get-projects-projectId-compliance-profile 3 params → 200
GET
/parties/{partyId}/compliance-profiledeprecated
Fetch a party's compliance profile
get-parties-partyId-compliance-profile 3 params → 200
POST
/parties/{partyId}/compliance-profiledeprecated
Assign compliance profile to a party
post-parties-partyId-compliance-profile 3 params body → 200
POST
/parties/{partyId}/relationships/compliance-profiledeprecated
Assign a compliance profile to a party
post-parties-partyId-relationships-compliance-profile 3 params body → 200
DELETE
/parties/{partyId}/relationships/compliance-profiledeprecated
Remove the compliance profile from a party
delete-parties-partyId-relationships-compliance-profile 1 param → 200
PATCH
/compliance-profiles/{id}
Rename a Global compliance profile in the caller's organization. Only profiles with context Global may be renamed via this endpoint. Returns the updated profile.
1 param body → 200400401403404500
POST
/compliance-profiles/{id}/requirements
Add requirements to a compliance profile. Each item is either a library reference (libraryRequirementId or attributeCode) or a custom definition (module/subject by code or label, attribute by label).…
1 param body → 200400401403404500
GET
/compliance-profiles/{id}/requirements
List the requirements of a compliance profile, paginated. Requirements are returned regardless of the profile context. Each rule is serialized as a requirement response alongside pagination metadata.…
3 params → 200400401403404500
GET
/compliance-profiles/{id}/requirements/{attributeCode}
Read a single requirement from a compliance profile by its attributeCode, regardless of the profile context. A missing profile, a missing requirement, or cross-org access returns 404.
2 params → 200400401403404500
PATCH
/compliance-profiles/{id}/requirements/{attributeCode}
Partially update a requirement on a compliance profile. Only the supplied fields are changed; omitted fields retain their current values. Updates are accepted on profiles of any context, with context…
2 params body → 200400401403404500
DELETE
/compliance-profiles/{id}/requirements/{attributeCode}
Remove a requirement from a Global compliance profile. Returns 204 with no body on success.
2 params → 204400401403404500

Schemas 19

The contract defines 19 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.

reference
object
Generic object reference
2 properties
compliance-profile
object
6 properties
objectId
string
collection-meta
object
4 properties
compliance-document
object
3 properties
reference-input
object
1 property 1 required
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-compliance-profiles-api-openapi.yml Raw ↑

Other APIs TrustLayer publishes across the network.

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