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 Projects API

The Projects API from TrustLayer — 9 operation(s) for projects.

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

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

This API exposes 13 operations across 9 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.

13 operations 9 paths 19 schemas 5 DELETE3 GET4 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 Projects 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 13

Across 9 paths, the API surfaces 13 operations — 5 DELETE, 3 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Projects 13
PUT
/projects/{id}/external-idsdeprecated
Update project external IDs
put-projects-:id-external-ids 1 param body → 200
GET
/projectsdeprecated
List projects
get-projects 5 params → 200
POST
/projectsdeprecated
Create a new project
post-projects body → 201
GET
/projects/{projectId}deprecated
Fetch a project
get-projects-id 2 params → 200
DELETE
/projects/{projectId}deprecated
Delete a project
delete-projects-projectId 1 param → 200
POST
/projects/{projectId}/relationships/partiesdeprecated
Add parties to a project
post-projects-id-relationships-parties 1 param body → 201
DELETE
/projects/{projectId}/relationships/partiesdeprecated
Remove a party from a project
delete-projects-id-relationships-parties 1 param body → 200
POST
/projects/{projectId}/relationships/documentsdeprecated
Attach documents to a project
post-projects-id-relationships-documents 1 param body → 201
DELETE
/projects/{projectId}/relationships/documentsdeprecated
Detach documents from a project
delete-projects-id-relationships-documents 1 param body → 200
DELETE
/projects/{projectId}/relationships/documents/{documentId}deprecated
Remove a document from a project
delete-projects-projectId-relationships-documents-documentId 2 params → 200
DELETE
/projects/{projectId}/relationships/parties/{partyId}deprecated
Remove a party from a project
delete-projects-projectId-relationships-parties-partyId 2 params → 200
GET
/projects/{projectId}/compliance-profiledeprecated
Fetch compliance profile for project
get-projects-projectId-compliance-profile 3 params → 200
POST
/documents/{documentId}/relationships/projectsdeprecated
Associate a document to multiple projects
post-documents-documentId-relationships-projects 1 param body → 200

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
collection-meta
object
4 properties
project-create
object
6 properties 1 required
reference-list-input
array
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
taggging
object
5 properties
party
object
20 properties
response-status
string
The possible values are "success", "fail", and "error".
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-projects-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 Context Records API
TrustLayer custom-fields API
TrustLayer Document Types API
TrustLayer documents API
TrustLayer Parties API
TrustLayer party-types API
TrustLayer Policies API
Where this information came from

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