Get a division

Get a division

curl --request GET \
  --url https://api.jobhandy.io/v1/divisions/{id} \
  --header 'X-API-Key: <api-key>'

const options = {method: 'GET', headers: {'X-API-Key': '<api-key>'}};

fetch('https://api.jobhandy.io/v1/divisions/{id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

using RestSharp;


var options = new RestClientOptions("https://api.jobhandy.io/v1/divisions/{id}");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("X-API-Key", "<api-key>");
var response = await client.GetAsync(request);

Console.WriteLine("{0}", response.Content);

{
  "id": "68920e08eeaea4f2301eecb3",
  "tenant": "68a000000000000000000010",
  "name": "Sales",
  "parentId": null,
  "order": 1,
  "costCenter": "CC-SALES",
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-07-01T08:15:00.000Z"
}

GET

https://api.jobhandy.io/v1

divisions

{id}

Get a division

curl --request GET \
  --url https://api.jobhandy.io/v1/divisions/{id} \
  --header 'X-API-Key: <api-key>'

const options = {method: 'GET', headers: {'X-API-Key': '<api-key>'}};

fetch('https://api.jobhandy.io/v1/divisions/{id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

using RestSharp;


var options = new RestClientOptions("https://api.jobhandy.io/v1/divisions/{id}");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("X-API-Key", "<api-key>");
var response = await client.GetAsync(request);

Console.WriteLine("{0}", response.Content);

{
  "id": "68920e08eeaea4f2301eecb3",
  "tenant": "68a000000000000000000010",
  "name": "Sales",
  "parentId": null,
  "order": 1,
  "costCenter": "CC-SALES",
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-07-01T08:15:00.000Z"
}

At a glance

Property	Behavior
Authentication	Required in X-API-Key
Tenant context	Optional narrowing; resource and references must remain in scope
Dry run	Not supported
Request body	None
Response	JSON
Primary success	`200`
Side effects	None beyond reading or downloading the authorized resource
Retry guidance	Transient read failures are generally safe to retry with bounded backoff

Operational behavior

Returns the division if it is in the API key’s scope.

The division must be visible through the API-key scope and optional tenant context.

Common errors

Error code	Meaning
`VALIDATION_ERROR`	Schema or business validation failed
`INVALID_REQUEST_ID`	X-Request-ID is not UUID v4 or v7
`INVALID_API_KEY`	Missing, invalid, deleted, or inactive API key
`TENANT_NOT_IN_SCOPE`	Selected tenant is outside API-key scope
`NOT_FOUND`	Resource is absent or not accessible in scope
`NOT_ACCEPTABLE`	Requested response media type is unavailable
`RATE_LIMIT_EXCEEDED`	API-key rate limit was exceeded
`INTERNAL_SERVER_ERROR`	Unexpected server failure

The operation response list and Error handling page are authoritative for complete handling.

Before implementation

Generate and log a new X-Request-ID for the attempt.
Handle every documented response status.
Do not log X-API-Key or unnecessary personal data.
Reconcile current resource state before replaying an ambiguous write.

Related integration guidance

Review the complete process, state, retry, and operational pattern for this operation.

Authorizations

X-API-Key

string

header

required

JobHandy integration API key. Send the credential in the X-API-Key header. Treat the key as a secret and use it only from trusted server-side environments.

Headers

X-Tenant-ID

string

inactive

optional

not sent by default

Narrows the operation to one tenant in the API key's scope. Any referenced or target resource must be accessible through that tenant. In interactive clients, use the {{tenantId}} variable when a tenant must be selected. Keep the header disabled when tenant selection is not required.

Pattern: ^[0-9a-fA-F]{24}$

X-Request-ID

string<uuid>

inactive

optional

not sent by default

Optional request identifier. If supplied, it must be a UUID v4 or v7 and is returned unchanged in every response. If omitted, the API generates one. Invalid values return 400 INVALID_REQUEST_ID. If your client uses a {{requestId}} variable, refresh it with a new UUID version 4 or 7 for every HTTP request attempt. Keep the header disabled to let the API generate the request identifier.

Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[47][0-9a-fA-F]{3}-[89aAbB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$

Path Parameters

string

required

Division ID.

Pattern: ^[0-9a-fA-F]{24}$

Example:

"68920e08eeaea4f2301eecb3"

Response

The requested division.

Division details.

string

required

read-only

Division ID. A create dry run returns a preview ID that cannot be used in later requests.

Example:

"68920e08eeaea4f2301eecb3"

tenant

string

required

read-only

ID of the tenant that owns the division.

Pattern: ^[0-9a-fA-F]{24}$

Example:

"68a000000000000000000010"

name

string

required

Division name.

Example:

"Sales"

parentId

string | null

required

nullable

Parent division ID, or null for a root division.

Minimum string length: 1

Pattern: ^[0-9a-fA-F]{24}$

Example:

null

order

number

required

Display order among sibling divisions.

Example:

1

costCenter

string | null

required

nullable

Customer-defined cost center, or null when none is assigned.

Minimum string length: 1

Example:

"CC-SALES"

createdAt

string<date-time>

required

read-only

UTC creation timestamp.

Minimum string length: 1

Pattern: Z$

Example:

"2026-01-15T10:30:00.000Z"

updatedAt

string<date-time>

required

read-only

UTC timestamp of the latest update.

Minimum string length: 1

Pattern: Z$

Example:

"2026-07-01T08:15:00.000Z"

Last modified on August 27, 2026

Overview

Data Models

Specification

At a glance

Operational behavior

Common errors

Before implementation

Related integration guidance

Authorizations

Headers

Path Parameters

Response

​At a glance

​Operational behavior

​Common errors

​Before implementation

Related integration guidance

Authorizations

Headers

Path Parameters

Response

At a glance

Operational behavior

Common errors

Before implementation