Task tag links

Links a tag to a task.

Licensed feature

This resource needs the teamproject 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.
teamprojecttaskidintegerTeamprojecttaskid. Id only - teamprojecttask is read-only or has no code key.
teamprojecttagidintegerReference to teamprojecttags, by id. Write either this or teamprojecttag.
teamprojecttagstring(100)Code for the referenced teamprojecttag, instead of the id.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
externalidstring(100)Your own key. Scoped to your company.

Endpoints#

POST/teamprojecttasktags/batch 207

Create many.

Requires scope projects: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
teamprojecttagidintegerReference to teamprojecttags, by id. Write either this or teamprojecttag.
teamprojecttagstring(100)Code for the referenced teamprojecttag, instead of the id.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
externalidstring(100)Your own key. Scoped to your company.
teamprojecttaskidintegerTeamprojecttaskid. Id only - teamprojecttask is read-only or has no code key.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/teamprojecttasktags/batch' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '[
    {
        "teamprojecttagid": 104,
        "teamprojecttag": "Example teamprojecttag",
        "teamprojecttaskid": 104
    }
]'
GET/teamprojecttasktags 200403

List task tag links.

Requires scope projects:read.

Parameters
NameInTypeNotes
cancelquerystringDefaults to false. Pass true or any.
modifiedsincequerystringRFC 3339 UTC timestamp. Returns only records changed since then, including cancelled ones - so cancel defaults to any rather than false when this is used. The response carries _meta.synced_through; store it and send it back next time.
externalidquerystringExact match on your own key.
teamprojecttaskidquerystringFilter to one task.
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/teamprojecttasktags' \
  -H 'Authorization: Bearer $NP_TOKEN'
POST/teamprojecttasktags 201400

Create.

Requires scope projects: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
teamprojecttagidintegerReference to teamprojecttags, by id. Write either this or teamprojecttag.
teamprojecttagstring(100)Code for the referenced teamprojecttag, instead of the id.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
externalidstring(100)Your own key. Scoped to your company.
teamprojecttaskidintegerTeamprojecttaskid. Id only - teamprojecttask is read-only or has no code key.
When it fails
StatusCodeMeaning
400invalid_requestA required field was missing.
curl -X POST \
  'https://acme.nolapro.com/!/api/v2/teamprojecttasktags' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag",
    "teamprojecttaskid": 104
}'
Response 201
{
    "teamprojecttaskid": 104,
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag"
}
GET/teamprojecttasktags/{id} 200404

Retrieve one record.

Requires scope projects: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/teamprojecttasktags/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "teamprojecttaskid": 104,
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag"
}
PATCH/teamprojecttasktags/{id} 200404

Update.

Requires scope projects: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.
teamprojecttaskidintegerTeamprojecttaskid. Id only - teamprojecttask is read-only or has no code key.
teamprojecttagidintegerReference to teamprojecttags, by id. Write either this or teamprojecttag.
teamprojecttagstring(100)Code for the referenced teamprojecttag, instead of the id.
cancelbooleanCancelled. NolaPro cancels rather than deletes, so a cancelled row is still readable.
entrydateread-onlystringWhen the record was created.
lastchangedateread-onlystringLast modification. Drives modifiedsince.
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/teamprojecttasktags/104' \
  -H 'Authorization: Bearer $NP_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-key' \
  -d '{
    "teamprojecttaskid": 104,
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag"
}'
Response 200
{
    "teamprojecttaskid": 104,
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag"
}
DELETE/teamprojecttasktags/{id} 200404

Cancel.

Requires scope projects: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/teamprojecttasktags/104' \
  -H 'Authorization: Bearer $NP_TOKEN'
Response 200
{
    "teamprojecttaskid": 104,
    "teamprojecttagid": 104,
    "teamprojecttag": "Example teamprojecttag"
}