Submit Bill Payment Request
POST/api/bills/:bill/payment-request/submit
Raise a payment request for a landed-cost bill's outstanding balance under the bill payment approval policy. It routes to the approvers of the matching tier; when you could approve every step yourself it completes in the same call. A bill that already has an approved amount can be submitted again for an increase — the earlier approval keeps covering what it authorized.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
No request body.
Authentication: Requires Bearer token.
Answers the bill (same shape as Get Bill) with its updated payment_approval_status and approval summary. Returns 409 approval_state_conflict when the tenant's bill payment approval policy is off — without the policy, landed-cost bills are paid without a payment request. The one bill payment approval policy covers purchase invoices and landed-cost bills alike.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.