Bulk action expense reports
Perform bulk actions on expense reports.
Authorizations
API key authentication for public API requests.
Keys come in two flavors:
- Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
- User-scoped keys are pinned to a user and span every legal
entity that user has access to. Every request made with a
user-scoped key (except
GET /legal-entity, which lists the legal entities the user can access) must include anx-legal-entityheader naming the legal entity the request is operating on. Requests without the header are rejected with400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with403.
Query Parameters
The legal entity ID. Required if authenticating with access to multiple legal entities.
Body
The action to perform on the expense reports.
approve, reject, cancel List of expense report IDs to act on.
Required for approve and reject actions. The user ID of the admin performing the action.
Deprecated and ignored. The acting user is derived from your credentials. For the cancel action, bearer tokens and user-scoped API keys can cancel only reports submitted by that user; legal-entity API keys must hold the reimbursements.approve permission and can cancel any pending report in the legal entity.
Required for reject action. The reason for rejecting.