API reference
PreviewDEAP API
Run the same commands the DEAP app runs across finance, operations, workforce and the records around them.
- Version
- 1.0.0
- Endpoints
- 1,195
- Areas
- 156
Base address
Requests go to your own workspace address, the one you sign in at.
Authentication
Send the access token of a signed-in user as a Bearer token. The token carries the tenant, the user and their roles, so no tenant header is needed.
How the API behaves
- One command per call
- Every operation is a POST to its own path. The JSON body is the command itself; it is not wrapped in another object.
- The tenant comes from the token
- The access token decides which tenant a command acts on. A tenant, user or role sent in a header is discarded.
- Choosing a company
- Send
X-Company-IDto act on a company other than the session's own. The call is refused with 403 if the caller has no access to it. - Retries
- Send
Idempotency-Keywith a value unique to the attempt, so a retry is not applied twice. - Execution authority
- Some actions need a separate grant. Without it the call answers 403 with
EXECUTION_AUTHORITY_REQUIREDand says whether to ask for the grant or to re-authenticate. - Request fields
- The fields each command takes are not published per operation yet. Refusals answer 422 with a message that names what was wrong.
Headers on every request
Each endpoint page lists these again, with any header that is its own.
AuthorizationstringRequiredAccess token of a signed-in user. It carries the tenant, the user and their roles.
Idempotency-KeystringOptionalA key you choose that is unique to this attempt, so a retry is not applied twice.
X-Company-IDstringOptionalCompany the command acts on. Refused with 403 if the caller has no access to it.
Content-TypestringRequiredAlways
application/json.
Errors every endpoint can return
Every error carries an HTTP status. Where it also carries a code, branch on the code, not on the message.
- 400The body is not one JSON value.
- 401The access token is missing, expired or not valid.
- 422The command was refused: a field is invalid, or the record is not in a state that allows the action. The message says which.
All endpoints
Bangladesh
Operations goods receipt
2
Cross domain
Bangladesh customer
3Bangladesh supplier
3Project accounting
6Serial generation
5Transfer pricing rule
5US customer
3US supplier
3
Finance
AP Bangladesh bill
4AP Bangladesh bill match exception
3AP Bangladesh payment run
4AP Bangladesh vendor bank account
3AP US payment run
3AP US vendor bank account
3AR Bangladesh collection account
3AR Bangladesh receipt
4AR collection account
17AR invoice
24- POSTApprove
- POSTCancel
- POSTCreate
- POSTCreate adjustment
- POSTDeliver
- POSTGet
- POSTGet adjustment eligibility
- POSTGet approval policy
- POSTGet by idempotency key
- POSTGet open items
- POSTHold
- POSTList
- POSTList events
- POSTPost
- POSTRegister approval policy
- POSTReject
- POSTRelease hold
- POSTRequest write off
- POSTReturn to draft
- POSTReverse and rebill
- POSTSend
- POSTSubmit
- POSTUpdate
- POSTValidate
AR receipt
21- POSTApply
- POSTCancel
- POSTCheck duplicate
- POSTCreate
- POSTGet
- POSTGet by idempotency key
- POSTIdentify
- POSTImport bank event
- POSTList
- POSTList applications
- POSTList events
- POSTMark returned
- POSTPut on account
- POSTReconcile
- POSTReverse
- POSTStart reconciliation
- POSTStop
- POSTSuggest applications
- POSTUnapply
- POSTUpdate
- POSTValidate
COA Bangladesh account
4Consolidation group
4Cost accounting allocation cycle
4Cost accounting allocation run
5Cost accounting cost pool
4GL accounting period
21- POSTApprove reopen
- POSTClose period
- POSTCreate
- POSTCreate fiscal year
- POSTGet
- POSTGet available transitions
- POSTGet GL close readiness
- POSTGet impact
- POSTGet readiness
- POSTList
- POSTList events
- POSTLock period
- POSTOpen period
- POSTReclose period
- POSTReject reopen
- POSTReopen period
- POSTRequest reopen
- POSTResolve for date
- POSTReturn to open
- POSTRun readiness checks
- POSTSoft close period
GL Bangladesh journal entry
5GL journal entry
24- POSTApprove
- POSTCreate
- POSTCreate manual
- POSTGet
- POSTGet approval policy
- POSTGet by idempotency key
- POSTGet regional completion
- POSTList
- POSTList events
- POSTList manual entry modes
- POSTList projection policies
- POSTPost
- POSTProject business event
- POSTRegister approval policy
- POSTRegister projection policy
- POSTReject
- POSTRetry regional publication
- POSTReturn to draft
- POSTReverse
- POSTSubmit
- POSTValidate
- POSTValidate manual
- POSTVerify posting
- POSTVoid
GL US journal entry
1Leases lease schedule
3Planning budget cycle
4Shareholders share class
5Shareholders shareholder
5Tax return
3Trade finance instrument amendment
6Trade finance instrument settlement
4Trade finance presentation
7Trade finance trade instrument
9
Identity
Approval authority
5Legal entity access
3User preference
2Workspace profile
3
Operations
Billing invoice
6Emissions record
6Purchase requisition
8Quality management
6Supplier qualification
6
Organization
Currency policy
4Document governance
4Fiscal calendar
5Number sequence
4
Platform
Approval instance
4Integration run
4
Sales
Sales order
5
System
Workforce
Employee Bangladesh employee
4Employee US employee
3Final settlement
4Job requisition
6Onboarding journey
6Payroll history
2Payroll payment
4Payroll reporting
2Payroll run
27- POSTApprove
- POSTCancel
- POSTClose
- POSTCollect inputs
- POSTCreate
- POSTFail
- POSTFreeze inputs
- POSTGet
- POSTList
- POSTMark paid
- POSTMark posted
- POSTPreflight
- POSTRaise exception
- POSTRecord calculation
- POSTRecord payment
- POSTRecord posting
- POSTResolve exception
- POSTRetry calculation
- POSTRetry payment
- POSTRetry posting
- POSTReturn to calculated
- POSTStart calculation
- POSTStart payment
- POSTStart posting
- POSTSubmit
- POSTUpdate
- POSTVerify totals
Payroll run Bangladesh payroll run
7Payroll run US payroll run
4Payroll US garnishment order
5Training course
6Work schedule
4