Item identifier types

What this company tracks per item: serial number, lot, expiry. datatype is the value shape; singleton means one unit per value, which is how a serial number differs from a lot.

Licensed feature

This resource needs all of the inventory and serialnuminnotes features 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.
namestring(255)Name of the identifier, shown wherever values are entered (e.g. Serial #, Lot).
datatypestring(1)Value type: empty = text, D = date (dates get parsed and expiration handling).
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
showonpicklistbooleanTrue prints the identifier value on pick lists.
showonorderconfbooleanTrue prints the identifier value on order confirmations.
showoninvoicebooleanTrue prints the identifier value on invoices.
showonpackingslipbooleanTrue prints the identifier value on packing slips.
singletonbooleanTrue when each value tracks a single unit (serial numbers); false when a value can cover a quantity (lots).
externalidstring(100)Your own key. Scoped to your company.

Endpoints#

POST/itemidentifiers/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.
namestring(255)Name of the identifier, shown wherever values are entered (e.g. Serial #, Lot).
datatypestring(1)Value type: empty = text, D = date (dates get parsed and expiration handling).
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
showonpicklistbooleanTrue prints the identifier value on pick lists.
showonorderconfbooleanTrue prints the identifier value on order confirmations.
showoninvoicebooleanTrue prints the identifier value on invoices.
showonpackingslipbooleanTrue prints the identifier value on packing slips.
singletonbooleanTrue when each value tracks a single unit (serial numbers); false when a value can cover a quantity (lots).
externalidstring(100)Your own key. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/itemidentifiers/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "name": "Example name",
        "datatype": "Example datatype",
        "showonpicklist": false,
        "showonorderconf": false,
        "showoninvoice": false,
        "showonpackingslip": false
    }
]'
GET/itemidentifiers 200403

List item identifier types.

Requires scope items:read.

Parameters
NameInTypeNotes
namequerystringPartial 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/itemidentifiers' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/itemidentifiers 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.
namestring(255)Name of the identifier, shown wherever values are entered (e.g. Serial #, Lot).
datatypestring(1)Value type: empty = text, D = date (dates get parsed and expiration handling).
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
showonpicklistbooleanTrue prints the identifier value on pick lists.
showonorderconfbooleanTrue prints the identifier value on order confirmations.
showoninvoicebooleanTrue prints the identifier value on invoices.
showonpackingslipbooleanTrue prints the identifier value on packing slips.
singletonbooleanTrue when each value tracks a single unit (serial numbers); false when a value can cover a quantity (lots).
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/itemidentifiers' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}'
Response 201
{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}
GET/itemidentifiers/{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/itemidentifiers/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}
PATCH/itemidentifiers/{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.
namestring(255)Name of the identifier, shown wherever values are entered (e.g. Serial #, Lot).
datatypestring(1)Value type: empty = text, D = date (dates get parsed and expiration handling).
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
showonpicklistbooleanTrue prints the identifier value on pick lists.
showonorderconfbooleanTrue prints the identifier value on order confirmations.
showoninvoicebooleanTrue prints the identifier value on invoices.
showonpackingslipbooleanTrue prints the identifier value on packing slips.
singletonbooleanTrue when each value tracks a single unit (serial numbers); false when a value can cover a quantity (lots).
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/itemidentifiers/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}'
Response 200
{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}
DELETE/itemidentifiers/{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/itemidentifiers/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "name": "Example name",
    "datatype": "Example datatype",
    "showonpicklist": false,
    "showonorderconf": false,
    "showoninvoice": false,
    "showonpackingslip": false
}