TRANXACT.AI Help

Accounting · Finance Configuration

Posting Roles

What every posting role resolves to for this company, and how. A role with no account refuses the postings that need it. Create default accounts makes the missing ones; Lock mapping tags what is being used today and stops all guessing.

Type REST3 operationsBase path /api/accounting/account-roles

Download specification (OpenAPI 3.1) Screen: Posting Roles

Overview

PackageAccounting
AuthenticationBearer token: a service account's token (POST /api/auth/service-token) or, for the published path, an API key
AuthorizationThe caller's roles must hold Accounting › Posting Roles on the Roles screen: display for GET, add for POST, change for PUT, delete for DELETE; an action needs the grant of the button that runs it on the screen.
RulesThe same as the screen: validation, numbering, approvals, posting, the company the caller belongs to, and the audit trail.

API reference

3 operations. Open one for its parameters, bodies, responses and a sample request.

GET/api/accounting/account-rolesRead posting roles

Response

200 with the data as JSON.

Sample request

curl "https://demo.tranxact.ai/api/accounting/account-roles" \
  -H "Authorization: Bearer $TOKEN"
POST/api/accounting/account-roles/create-defaultsCreate defaults

No body is required.

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X POST "https://demo.tranxact.ai/api/accounting/account-roles/create-defaults" \
  -H "Authorization: Bearer $TOKEN"
POST/api/accounting/account-roles/lockLock

No body is required.

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X POST "https://demo.tranxact.ai/api/accounting/account-roles/lock" \
  -H "Authorization: Bearer $TOKEN"

Errors

StatusMeaning
400The request could not be read: a filter that is not JSON, a bad parameter
401No credential, or it is wrong, revoked or expired
403The caller's roles do not hold Accounting › Posting Roles for this verb, or the address or origin is not allowed
404No record with that id is visible to the caller
409A conflict: a duplicate number, a document in a state that does not allow it, or a record changed or locked by someone else
422Refused by the same validation as the screen; the error names the field and why

Every error is JSON: {"error": "a sentence saying what was wrong"}, with field where it applies.