Re-attribute Bills
POST/api/shipbob/:instance/bills/reattribute
Queue re-attribution of ShipBob billing transactions: the given transaction ids, every transaction of one fee name, or (when neither is sent) every transaction since the billing start date. Previous targets are removed and rebuilt, so a re-run never double counts. Returns the tracked job id.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Authentication: Requires Bearer token.
Request Body:
- transaction_ids (integer[], optional, max 5000) — local transaction ids.
- fee_name (string, optional, max 150) — re-attribute one fee.
Returns 422 when billing sync is disabled for the instance.
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 — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
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.