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

Checkr Nodes and Hierarchy API

Tree of nodes modeling account/organization structure.

Checkr Nodes and Hierarchy API is one of 14 APIs that Checkr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Nodes and Hierarchy. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.checkr.com/v1, https://api.checkr-staging.com/v1.

7 operations 5 paths 1 schemas 1 DELETE3 GET1 PATCH2 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.checkr.com/v1
Authentication
HTTP Basic
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Checkr Nodes and Hierarchy API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic auth with your secret API key as the username and an empty password. Checkr Partner integrations authenticate on behalf of customer accounts using O…

Paths & Operations 7

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

Nodes and Hierarchy 7

Tree of nodes modeling account/organization structure.

POST
/hierarchy
Create a hierarchy
createHierarchy body → 200
POST
/hierarchy/nodes
Add nodes to the hierarchy
addHierarchyNodes body → 200
GET
/hierarchy/status
Retrieve hierarchy update status
getHierarchyStatus → 200
GET
/nodes
List nodes
listNodes → 200
GET
/nodes/{id}
Retrieve a node
getNode 1 param → 200
PATCH
/nodes/{id}
Update a node
updateNode 1 param body → 200
DELETE
/nodes/{id}
Delete a node
deleteNode 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Node (6 properties). Each schema is shown below with its type and property counts.

Node
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

checkr-nodes-and-hierarchy-api-openapi.yml Raw ↑

Other APIs Checkr publishes across the network.

Checkr Account API
Checkr Adverse Actions API
Checkr Candidates API
Checkr Continuous Checks API
Checkr Documents API
Checkr Geos API
Checkr Invitations API
Checkr Packages API
Checkr Reports API
Checkr Screenings API
Checkr Subscriptions API
Checkr Verifications API
Where this information came from

This is an independent, third-party profile of Checkr Nodes and Hierarchy 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.