Sites

Physical sites a job runs at.

Licensed feature

This resource needs the construction 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.
sitecodestring(20)Short code of the site.
dealtextDeal. Stored as text, no practical length limit.
ownerinteger0 when the site is not owned by the associated company.
locationstring(250)The locationcode of the referenced inventorylocations, instead of the id. Send this or locationid, not both unless they agree.
estimate_groundbreakstringEstimated groundbreaking date.
statusintegerSite status code.
cancelbooleanCancelled. Always a boolean on the wire, whatever integer width the column uses (D23).
entrydateread-onlystringWhen the record was created.
sitenamestring(255)Name of the site.
groundbreakingdatestringActual groundbreaking date.
externalidstring(100)Your own key. Scoped to your company.

Endpoints#

POST/sites/batch 207

Create many.

Requires scope jobs: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.
sitecodestring(20)Short code of the site.
dealtextDeal. Stored as text, no practical length limit.
ownerinteger0 when the site is not owned by the associated company.
locationstring(250)The locationcode of the referenced inventorylocations, instead of the id. Send this or locationid, not both unless they agree.
estimate_groundbreakstringEstimated groundbreaking date.
statusintegerSite status code.
cancelbooleanCancelled. Always a boolean on the wire, whatever integer width the column uses (D23).
entrydateread-onlystringWhen the record was created.
sitenamestring(255)Name of the site.
groundbreakingdatestringActual groundbreaking date.
externalidstring(100)Your own key. Scoped to your company.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/sites/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "sitecode": "ACME-01",
        "deal": "Example deal",
        "owner": 1,
        "location": "Example location",
        "estimate_groundbreak": "2026-08-01",
        "status": 1
    }
]'
GET/sites 200403

List sites.

Requires scope jobs:read.

Parameters
NameInTypeNotes
statusquerystringRestrict to one status.
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/sites' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/sites 201400

Create.

Requires scope jobs: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.
sitecodestring(20)Short code of the site.
dealtextDeal. Stored as text, no practical length limit.
ownerinteger0 when the site is not owned by the associated company.
locationstring(250)The locationcode of the referenced inventorylocations, instead of the id. Send this or locationid, not both unless they agree.
estimate_groundbreakstringEstimated groundbreaking date.
statusintegerSite status code.
cancelbooleanCancelled. Always a boolean on the wire, whatever integer width the column uses (D23).
entrydateread-onlystringWhen the record was created.
sitenamestring(255)Name of the site.
groundbreakingdatestringActual groundbreaking date.
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/sites' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}'
Response 201
{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}
GET/sites/{id} 200404

Retrieve one record.

Requires scope jobs: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/sites/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}
PATCH/sites/{id} 200404

Update.

Requires scope jobs: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.
sitecodestring(20)Short code of the site.
dealtextDeal. Stored as text, no practical length limit.
ownerinteger0 when the site is not owned by the associated company.
locationstring(250)The locationcode of the referenced inventorylocations, instead of the id. Send this or locationid, not both unless they agree.
estimate_groundbreakstringEstimated groundbreaking date.
statusintegerSite status code.
cancelbooleanCancelled. Always a boolean on the wire, whatever integer width the column uses (D23).
entrydateread-onlystringWhen the record was created.
sitenamestring(255)Name of the site.
groundbreakingdatestringActual groundbreaking date.
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/sites/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}'
Response 200
{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}
DELETE/sites/{id} 200404

Cancel.

Requires scope jobs: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/sites/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "sitecode": "ACME-01",
    "deal": "Example deal",
    "owner": 1,
    "location": "Example location",
    "estimate_groundbreak": "2026-08-01",
    "status": 1
}