Item price special rows

Special pricing rows for an item.

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.
itempricespecialidintegerItempricespecialid. Id only.
itemidintegerReference to items, by id. Write either this or item.
itemstring(255)The sku of the referenced items, instead of the id. Send this or itemid, not both unless they agree.
pricemoneystring(6dp)Stored as decimal(18,6).
begindatestringDate the special price starts.
enddatestringDate the special price ends.
marginmoneystring(6dp)Stored as decimal(18,6).
mincostmoneystring(6dp)Stored as decimal(18,6).
notesstring(255)Notes on the special price.
periodstring(1)Rental period the special price applies to: D = daily, W = weekly, M = monthly. Empty for non-rental pricing.
externalidstring(100)Your own key. Scoped to your company.

Endpoints#

POST/itempricespecialdetails/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.
itempricespecialidintegerItempricespecialid. Id only.
itemidintegerReference to items, by id. Write either this or item.
itemstring(255)The sku of the referenced items, instead of the id. Send this or itemid, not both unless they agree.
pricemoneystring(6dp)Stored as decimal(18,6).
begindatestringDate the special price starts.
enddatestringDate the special price ends.
marginmoneystring(6dp)Stored as decimal(18,6).
mincostmoneystring(6dp)Stored as decimal(18,6).
notesstring(255)Notes on the special price.
periodstring(1)Rental period the special price applies to: D = daily, W = weekly, M = monthly. Empty for non-rental pricing.
externalidstring(100)Your own key. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/itempricespecialdetails/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "itempricespecialid": 104,
        "itemid": 104,
        "item": "Example item",
        "price": "125.0000",
        "begindate": "2026-08-01",
        "enddate": "2026-08-01"
    }
]'
GET/itempricespecialdetails 200403

List item price specials.

Requires scope items:read.

Parameters
NameInTypeNotes
itemidquerystringRestrict to one itemid.
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/itempricespecialdetails' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/itempricespecialdetails 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.
itempricespecialidintegerItempricespecialid. Id only.
itemidintegerReference to items, by id. Write either this or item.
itemstring(255)The sku of the referenced items, instead of the id. Send this or itemid, not both unless they agree.
pricemoneystring(6dp)Stored as decimal(18,6).
begindatestringDate the special price starts.
enddatestringDate the special price ends.
marginmoneystring(6dp)Stored as decimal(18,6).
mincostmoneystring(6dp)Stored as decimal(18,6).
notesstring(255)Notes on the special price.
periodstring(1)Rental period the special price applies to: D = daily, W = weekly, M = monthly. Empty for non-rental pricing.
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/itempricespecialdetails' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "itempricespecialid": 104,
    "itemid": 104,
    "item": "Example item",
    "price": "125.0000",
    "begindate": "2026-08-01",
    "enddate": "2026-08-01"
}'
Response 201
{
    "itempricespecialid": 104,
    "itemid": 104,
    "item": "Example item",
    "price": "125.0000",
    "begindate": "2026-08-01",
    "enddate": "2026-08-01"
}
GET/itempricespecialdetails/{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/itempricespecialdetails/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "itempricespecialid": 104,
    "itemid": 104,
    "item": "Example item",
    "price": "125.0000",
    "begindate": "2026-08-01",
    "enddate": "2026-08-01"
}
PATCH/itempricespecialdetails/{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.
itempricespecialidintegerItempricespecialid. Id only.
itemidintegerReference to items, by id. Write either this or item.
itemstring(255)The sku of the referenced items, instead of the id. Send this or itemid, not both unless they agree.
pricemoneystring(6dp)Stored as decimal(18,6).
begindatestringDate the special price starts.
enddatestringDate the special price ends.
marginmoneystring(6dp)Stored as decimal(18,6).
mincostmoneystring(6dp)Stored as decimal(18,6).
notesstring(255)Notes on the special price.
periodstring(1)Rental period the special price applies to: D = daily, W = weekly, M = monthly. Empty for non-rental pricing.
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/itempricespecialdetails/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "itempricespecialid": 104,
    "itemid": 104,
    "item": "Example item",
    "price": "125.0000",
    "begindate": "2026-08-01",
    "enddate": "2026-08-01"
}'
Response 200
{
    "itempricespecialid": 104,
    "itemid": 104,
    "item": "Example item",
    "price": "125.0000",
    "begindate": "2026-08-01",
    "enddate": "2026-08-01"
}