Item price specials

Special pricing headers. The rows live in itempricespecialdetails.

Licensed feature

This resource needs the inventory 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.
customeridintegerReference to customers, by id. Write either this or customer.
customerstring(30)Code for the referenced customer, instead of the id.
jobidintegerJobid. Id only.
descriptiontextDescription. Stored as text, no practical length limit.
inventorylocationidintegerInventorylocationid. Id only.
inventorylocationstring(20)The locationcode of the referenced inventorylocations, instead of the id. Send this or inventorylocationid, not both unless they agree.
begindatestringDate the special pricing starts.
enddatestringDate the special pricing ends.
entrydateread-onlystringWhen the record was created.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
staticboolean1 when the special is a static price rather than a discount off the regular price.
externalidstring(100)Your own key. Scoped to your company.

Endpoints#

POST/itempricespecials/batch 207

Create many.

Requires scope items: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.
customeridintegerReference to customers, by id. Write either this or customer.
customerstring(30)Code for the referenced customer, instead of the id.
jobidintegerJobid. Id only.
descriptiontextDescription. Stored as text, no practical length limit.
inventorylocationidintegerInventorylocationid. Id only.
inventorylocationstring(20)The locationcode of the referenced inventorylocations, instead of the id. Send this or inventorylocationid, not both unless they agree.
begindatestringDate the special pricing starts.
enddatestringDate the special pricing ends.
entrydateread-onlystringWhen the record was created.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
staticboolean1 when the special is a static price rather than a discount off the regular price.
externalidstring(100)Your own key. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/itempricespecials/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "customerid": 104,
        "customer": "Example customer",
        "jobid": 104,
        "description": "Example description",
        "inventorylocationid": 104,
        "inventorylocation": "Example inventorylocation"
    }
]'
GET/itempricespecials 200403

List item price specials.

Requires scope items:read.

Parameters
NameInTypeNotes
customeridquerystringRestrict to one customerid.
inventorylocationidquerystringRestrict to one inventorylocationid.
jobidquerystringRestrict to one jobid.
descriptionquerystringdescription. Partial match, case-insensitive.
cancelquerystringDefaults to false. Pass true or any.
externalidquerystringExact match on your own key.
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 read scope.
curl \
  'https://acme.nolapro.com/!/api/v2/itempricespecials' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/itempricespecials 201400

Create.

Requires scope items: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.
customeridintegerReference to customers, by id. Write either this or customer.
customerstring(30)Code for the referenced customer, instead of the id.
jobidintegerJobid. Id only.
descriptiontextDescription. Stored as text, no practical length limit.
inventorylocationidintegerInventorylocationid. Id only.
inventorylocationstring(20)The locationcode of the referenced inventorylocations, instead of the id. Send this or inventorylocationid, not both unless they agree.
begindatestringDate the special pricing starts.
enddatestringDate the special pricing ends.
entrydateread-onlystringWhen the record was created.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
staticboolean1 when the special is a static price rather than a discount off the regular price.
externalidstring(100)Your own key. Scoped to your company.
When it fails
StatusCodeMeaning
400invalid_requestA required field was missing.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/itempricespecials' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}'
Response 201
{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}
GET/itempricespecials/{id} 200404

Retrieve one record.

Requires scope items: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/itempricespecials/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}
PATCH/itempricespecials/{id} 200404

Update.

Requires scope items: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.
customeridintegerReference to customers, by id. Write either this or customer.
customerstring(30)Code for the referenced customer, instead of the id.
jobidintegerJobid. Id only.
descriptiontextDescription. Stored as text, no practical length limit.
inventorylocationidintegerInventorylocationid. Id only.
inventorylocationstring(20)The locationcode of the referenced inventorylocations, instead of the id. Send this or inventorylocationid, not both unless they agree.
begindatestringDate the special pricing starts.
enddatestringDate the special pricing ends.
entrydateread-onlystringWhen the record was created.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
staticboolean1 when the special is a static price rather than a discount off the regular price.
externalidstring(100)Your own key. Scoped to your company.
When it fails
StatusCodeMeaning
404not_foundNo record with that id.
curl -X PATCH \
  'https://acme.nolapro.com/!/api/v2/itempricespecials/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}'
Response 200
{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}
DELETE/itempricespecials/{id} 200404

Cancel.

Requires scope items: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
404not_foundNo record with that id.
curl -X DELETE \
  'https://acme.nolapro.com/!/api/v2/itempricespecials/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "customerid": 104,
    "customer": "Example customer",
    "jobid": 104,
    "description": "Example description",
    "inventorylocationid": 104,
    "inventorylocation": "Example inventorylocation"
}