Void Bill
POST/api/shipbob/:instance/bills/:transaction/void
Mark a billing transaction void — use it when ShipBob dropped a charge, since no later sync will report the removal. Its attribution is removed (order or purchase order cost lines deleted, its monthly cost entry rebuilt, billed freight re-applied to the fulfillment, the order's margin recalculated) and it is left excluded with reason manually_voided. Re-syncs and re-attribution never touch a voided transaction until it is un-voided. Returns the updated bill.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Authentication: Requires Bearer token.
Returns 422 when the bill's fee was capitalised into a purchase order whose receipts fall in a locked accounting period.
Request
Responses
- 200
- 401
- 403
- 404
- 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
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.