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

Truv Orders API

Verification orders and their lifecycle.

Truv Orders API is one of 20 APIs that Truv publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 9 operations across 7 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://prod.truv.com.

9 operations 7 paths 2 schemas 3 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://prod.truv.com/v1
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Truv Orders API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Access-Client-Id (accessClientId). An API key is passed in the header as X-Access-Secret (accessSecret). By default, every request must be authenticated.

  • accessClientId — Your Truv access client ID.
  • accessSecret — Your Truv access secret.

Paths & Operations 9

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

Orders 9

Verification orders and their lifecycle.

POST
/v1/orders/
Create an order.
createOrder body → 201
POST
/v1/orders/lookup/
Look up an order.
lookupOrder body → 200
GET
/v1/orders/{id}/
Retrieve an order.
getOrder 1 param → 200
POST
/v1/orders/{id}/
Update an order.
updateOrderPost 1 param body → 200
PATCH
/v1/orders/{id}/
Partially update an order.
patchOrder 1 param body → 200
POST
/v1/orders/{id}/cancel/
Cancel an order.
cancelOrder 1 param → 200
POST
/v1/orders/{id}/employers/
Add employers to an order.
addOrderEmployers 1 param body → 200
GET
/v1/orders/{id}/events/
Retrieve events for an order.
getOrderEvents 1 param → 200
GET
/v1/orders/{id}/certifications/
Retrieve certifications for an order.
getOrderCertifications 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are OrderRequest (4 properties), Order (4 properties). Each schema is shown below with its type and property counts.

Order
object
4 properties
OrderRequest
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

truv-orders-api-openapi.yml Raw ↑

Other APIs Truv publishes across the network.

Truv Admin API
Truv Banking API
Truv Bridge Tokens API
Truv Companies & Providers API
Truv Direct Deposit API
Truv Employment API
Truv Identity API
Truv Income API
Truv Insurance API
Truv Links API
Truv Pay Statements API
Truv Payroll & Shifts API
Where this information came from

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