- Retrieve an existing node
Returns an existing node by custom_id.
If
include=packagesis passed, the response will include a "packages" field. This will be an array of strings representing the slugs of the account Packages that are assigned (directly or indirectly) to the given Node. This field can be used to build UIs that truncate the list of Packages displayed to a requester, or to display only the nodes that are relevant to the requester.If
include=packagesis not passed, no package information will be included in the response.
- Mock serverhttps://docs.checkr.com/_mock/apis/openapi/nodes/{custom_id}
- Staginghttps://api.checkr-staging.com/v1/nodes/{custom_id}
curl -i -X GET \
-u '<username>:<password>' \
'https://docs.checkr.com/_mock/apis/openapi/nodes/{custom_id}?include=packages'Node
The name for the node. This name will be displayed in the Checkr Dashboard.
Customer-defined unique ID for the node. Must be unique within your account. Note: Custom IDs may contain only letters, numbers, spaces, hyphens, colons, ampersands, and/or underscores.
Customer-defined label for this level of the hierarchy. (For example "Department" or "Division".)
The custom_id for the parent of this node. If not provided, this node will be placed at the top level of the hierarchy. Note: If provided, this node must be a valid and previously loaded custom_id, and may contain only letters, numbers, spaces, hyphens, colons, ampersands, and/or underscores.
{ "name": "Acme Staffing", "custom_id": "zpy8orej4r614ize", "tier": "department", "parent_custom_id": "parent custom id", "packages": [ "driver_pro", "tasker_pro" ] }