Departments

Departments, used for payroll expense allocation. Each carries the GL accounts wages and taxes post to.

Licensed feature

This resource needs the payroll feature active on the install you are calling. Without that every endpoint here answers 403 with feature_not_licensed - that is a licensing answer, not a permissions one, so check the company's features before the token's scopes.

The object#

FieldTypeDescription
idread-onlyintegerNolaPro id.
codestring(45)The code.
namestring(100)Label.
glwageexpenseidintegerWage expense account. Id only - the table this points at is not identifiable from the column name, so there is no human key to send instead.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this departments. Scoped to your company.

Endpoints#

POST/departments/batch 207

Create many.

Requires scope payroll:write.

Parameters
NameInTypeNotes
Idempotency-KeyheaderstringMakes the write safely retryable. Any unique string per logical operation; a UUID is fine. The failure this prevents is specific: the request succeeds, the response is lost to a timeout, you retry, and the customer is billed twice. With a key, the retry returns the original response - same status, same body, same id - and creates nothing. The body is part of the key's identity. Reusing a key with a different body is a bug on your side, not a retry, and answers 409 idempotency_replay rather than silently handing back the old response. Keys are remembered for 24 hours.
Body array
FieldTypeDescription
idread-onlyintegerNolaPro id.
codestring(45)The code.
namestring(100)Label.
glwageexpenseidintegerWage expense account. Id only - the table this points at is not identifiable from the column name, so there is no human key to send instead.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this departments. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/departments/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "id": 1,
        "code": "SHIP",
        "name": "Shipping",
        "glwageexpenseid": 0,
        "cancel": false
    }
]'
GET/departments 200403

List departments.

Requires scope payroll:read.

Parameters
NameInTypeNotes
namequerystringname. Partial match, case-insensitive.
codequerystringcode. Partial match, case-insensitive.
cancelquerystringDefaults to false. Pass true or any.
externalidquerystringExact match on your own key. Scoped to your company.
includequerystringComma-separated extras to embed. Only custom_fields is available: the extra fields this install has defined on the record. Off by default, and an unrecognised value is refused rather than ignored. See Conventions.
When it fails
StatusCodeMeaning
403insufficient_scopeToken lacks departments:read.
curl \
  'https://acme.nolapro.com/!/api/v2/departments' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/departments 201400409

Create.

Requires scope payroll:write.

Parameters
NameInTypeNotes
Idempotency-KeyheaderstringMakes the write safely retryable. Any unique string per logical operation; a UUID is fine. The failure this prevents is specific: the request succeeds, the response is lost to a timeout, you retry, and the customer is billed twice. With a key, the retry returns the original response - same status, same body, same id - and creates nothing. The body is part of the key's identity. Reusing a key with a different body is a bug on your side, not a retry, and answers 409 idempotency_replay rather than silently handing back the old response. Keys are remembered for 24 hours.
Body
FieldTypeDescription
idread-onlyintegerNolaPro id.
codestring(45)The code.
namestring(100)Label.
glwageexpenseidintegerWage expense account. Id only - the table this points at is not identifiable from the column name, so there is no human key to send instead.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this departments. Scoped to your company.
When it fails
StatusCodeMeaning
400invalid_requestA required field was missing.
409duplicateThat code is already in use.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/departments' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}'
Response 201
{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}
GET/departments/{id} 200404

Retrieve one record.

Requires scope payroll:read.

Parameters
NameInTypeNotes
idrequiredpathintegerThe record id.
includequerystringComma-separated extras to embed. Only custom_fields is available: the extra fields this install has defined on the record. Off by default, and an unrecognised value is refused rather than ignored. See Conventions.
When it fails
StatusCodeMeaning
404not_foundNo record with that id.
curl \
  'https://acme.nolapro.com/!/api/v2/departments/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}
PATCH/departments/{id} 200404409

Update.

Requires scope payroll:write.

Parameters
NameInTypeNotes
idrequiredpathintegerThe record id.
Idempotency-KeyheaderstringMakes the write safely retryable. Any unique string per logical operation; a UUID is fine. The failure this prevents is specific: the request succeeds, the response is lost to a timeout, you retry, and the customer is billed twice. With a key, the retry returns the original response - same status, same body, same id - and creates nothing. The body is part of the key's identity. Reusing a key with a different body is a bug on your side, not a retry, and answers 409 idempotency_replay rather than silently handing back the old response. Keys are remembered for 24 hours.
Body
FieldTypeDescription
idread-onlyintegerNolaPro id.
codestring(45)The code.
namestring(100)Label.
glwageexpenseidintegerWage expense account. Id only - the table this points at is not identifiable from the column name, so there is no human key to send instead.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this departments. Scoped to your company.
When it fails
StatusCodeMeaning
404not_foundNo record with that id.
409stale_recordIf-Match did not match.
curl -X PATCH \
  'https://acme.nolapro.com/!/api/v2/departments/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}'
Response 200
{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}
DELETE/departments/{id} 200403404

Cancel.

Requires scope payroll:cancel.

Parameters
NameInTypeNotes
idrequiredpathintegerThe record id.
Idempotency-KeyheaderstringMakes the write safely retryable. Any unique string per logical operation; a UUID is fine. The failure this prevents is specific: the request succeeds, the response is lost to a timeout, you retry, and the customer is billed twice. With a key, the retry returns the original response - same status, same body, same id - and creates nothing. The body is part of the key's identity. Reusing a key with a different body is a bug on your side, not a retry, and answers 409 idempotency_replay rather than silently handing back the old response. Keys are remembered for 24 hours.
When it fails
StatusCodeMeaning
403insufficient_scopeNeeds departments:cancel.
404not_foundNo record with that id.
curl -X DELETE \
  'https://acme.nolapro.com/!/api/v2/departments/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "id": 1,
    "code": "SHIP",
    "name": "Shipping",
    "glwageexpenseid": 0,
    "cancel": false
}