Accounting · Services and actions
Revenue
The revenue service of Accounting: 5 operation(s).
/api/accounting/revenueOverview
| Package | Accounting |
|---|---|
| Authentication | Bearer token: a service account's token (POST /api/auth/service-token) or, for the published path, an API key |
| Authorization | The caller's roles must hold Accounting › Revenue 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. |
| Rules | The same as the screen: validation, numbering, approvals, posting, the company the caller belongs to, and the audit trail. |
API reference
5 operations. Open one for its parameters, bodies, responses and a sample request.
POST/api/accounting/revenue/contracts/{id}/allocateContracts allocate
Path parameters
| Name | Type | Description |
|---|---|---|
id | string (uuid) | The record's id, as a list returns it. |
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/revenue/contracts/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73/allocate" \
-H "Authorization: Bearer $TOKEN"POST/api/accounting/revenue/runRun
Request body
The keys this action reads (* = required; "one of" lists the only values):
ledgerId*, periodCode, isTestRunResponse
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/revenue/run" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"ledgerId":"value","periodCode":"value","isTestRun":"value"}'POST/api/accounting/revenue/contracts/{id}/modifyContracts modify
Path parameters
| Name | Type | Description |
|---|---|---|
id | string (uuid) | The record's id, as a list returns it. |
Request body
The keys this action reads (* = required; "one of" lists the only values):
modificationType, additionalValue, reason, obligations; modificationType one of separate_contract|termination_and_new|prospective|cumulative_catch_upResponse
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/revenue/contracts/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73/modify" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"modificationType":"value","additionalValue":"value","reason":"value","obligations;":"value"}'GET/api/accounting/revenue/waterfallWaterfall
Response
200 with the data as JSON.
Sample request
curl "https://demo.tranxact.ai/api/accounting/revenue/waterfall" \
-H "Authorization: Bearer $TOKEN"GET/api/accounting/revenue/contract-balancesContract balances
Response
200 with the data as JSON.
Sample request
curl "https://demo.tranxact.ai/api/accounting/revenue/contract-balances" \
-H "Authorization: Bearer $TOKEN"Errors
| Status | Meaning |
|---|---|
| 400 | The request could not be read: a filter that is not JSON, a bad parameter |
| 401 | No credential, or it is wrong, revoked or expired |
| 403 | The caller's roles do not hold Accounting › Revenue for this verb, or the address or origin is not allowed |
| 404 | No record with that id is visible to the caller |
| 409 | A conflict: a duplicate number, a document in a state that does not allow it, or a record changed or locked by someone else |
| 422 | Refused 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.