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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
TrustLayer

TrustLayer Requirements API

The Requirements API from TrustLayer — 2 operation(s) for requirements.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 4 operations across 2 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.

4 operations 2 paths 2 schemas 2 GET1 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
Contact
TrustLayer Support
License
Apache 2.0
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

TrustLayer Requirements 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 4

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

Requirements 4
POST
/requirements
Create a library requirement in the caller's organization (derived from the access token). Define the module/subject by label to create new ones, or by code/label to reuse an existing template, plus…
body → 201400401403404500
GET
/requirements
List library requirements in the caller's organization. Results are always scoped to the caller's organization and never include system requirement templates. Supports pagination via limit and skip.…
9 params → 200400401403404500
PATCH
/requirements/{id}
Partially update a library requirement in the caller's organization. Supply any subset of the editable fields; omitted fields keep their stored values, and the merged (attributeType, operator, target…
1 param body → 200400401403404500
GET
/requirements/{id}
Read a single library requirement by id, scoped to the caller's organization.
2 params → 200400401403404500

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-requirements-api-openapi.yml Raw ↑

Other APIs TrustLayer publishes across the network.

TrustLayer Auth API
AE Profile APIs.io
TrustLayer branding API
AE Profile APIs.io
TrustLayer compliance-profiles API
AE Profile APIs.io
TrustLayer contacts API
AE Profile APIs.io
TrustLayer Context Objects API
AE Profile APIs.io
TrustLayer Context Records API
AE Profile APIs.io
TrustLayer custom-fields API
AE Profile APIs.io
TrustLayer Document Types API
AE Profile APIs.io
TrustLayer documents API
AE Profile APIs.io
TrustLayer Parties API
AE Profile APIs.io
TrustLayer party-types API
AE Profile APIs.io
TrustLayer Policies API
AE Profile APIs.io
#Requirements
← Back to T APIs
API Details
ID
trustlayer:trustlayer-requirements-api
Base URL
https://api.trustlayer.io/v2
Docs
https://developers.trustlayer.io/v2
Provider
TrustLayer
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=trustlayer-requirements-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/trustlayer-requirements-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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