Cost codes

Cost codes for job and project costing.

The object#

FieldTypeDescription
idread-onlyintegerNolaPro id.
codestring(20)The code.
descriptionstring(255)Label.
blocksalesbooleanBlocked from use on sales.
inactivebooleanNot in use. Distinct from cancel.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this cost codes. Scoped to your company.

Endpoints#

POST/costcodes/batch 207

Create many.

Requires scope glaccounts: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(20)The code.
descriptionstring(255)Label.
blocksalesbooleanBlocked from use on sales.
inactivebooleanNot in use. Distinct from cancel.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this cost codes. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/costcodes/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "id": 4,
        "code": "LAB",
        "description": "Labour",
        "blocksales": false,
        "inactive": false,
        "cancel": false
    }
]'
GET/costcodes 200403

List cost codes.

Requires scope glaccounts:read.

Parameters
NameInTypeNotes
descriptionquerystringdescription. 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 costcodes:read.
curl \
  'https://acme.nolapro.com/!/api/v2/costcodes' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/costcodes 201400409

Create.

Requires scope glaccounts: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(20)The code.
descriptionstring(255)Label.
blocksalesbooleanBlocked from use on sales.
inactivebooleanNot in use. Distinct from cancel.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this cost codes. 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/costcodes' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}'
Response 201
{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}
GET/costcodes/{id} 200404

Retrieve one record.

Requires scope glaccounts: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/costcodes/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}
PATCH/costcodes/{id} 200404409

Update.

Requires scope glaccounts: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(20)The code.
descriptionstring(255)Label.
blocksalesbooleanBlocked from use on sales.
inactivebooleanNot in use. Distinct from cancel.
cancelbooleanTrue once cancelled.
externalidstring(100)Your own key for this cost codes. 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/costcodes/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}'
Response 200
{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}
DELETE/costcodes/{id} 200403404

Cancel.

Requires scope glaccounts: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 costcodes:cancel.
404not_foundNo record with that id.
curl -X DELETE \
  'https://acme.nolapro.com/!/api/v2/costcodes/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "id": 4,
    "code": "LAB",
    "description": "Labour",
    "blocksales": false,
    "inactive": false,
    "cancel": false
}