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 custom-fields API

The custom-fields API from TrustLayer — 4 operation(s) for custom-fields.

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

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

This API exposes 6 operations across 4 paths, and defines 21 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.

6 operations 4 paths 21 schemas 1 DELETE1 GET3 PATCH1 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 custom-fields 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 6

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

custom-fields 6
PATCH
/projects/{projectId}deprecated
Update a custom field
patch-custom-fields 1 param body → 200
GET
/custom-fieldsdeprecated
List custom fields
get-custom-fields → 200
POST
/custom-fieldsdeprecated
Create a new custom field
post-custom-fields body → 201
PATCH
/custom-fields/{fieldId}deprecated
Update a custom field
patch-custom-fields-fieldId 1 param body → 200
DELETE
/custom-fields/{fieldId}deprecated
Delete a custom field
delete-custom-fields-fieldId 1 param → 200
PATCH
/parties/{partyId}/custom-datadeprecated
Update party custom data
patch-parties-partyId-custom-data 3 params body → 200

Schemas 21

The contract defines 21 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
custom-field-update
object
6 properties
compliance-profile
object
6 properties
collection-meta
object
4 properties
project-update
object
6 properties 1 required
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
custom-data-update
array
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
custom-field-create
object
7 properties 2 required
compliance-status
object
8 properties 5 required
project
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trustlayer-custom-fields-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 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 custom-fields 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.