Update Bill Sync Settings
PUT/api/accounting/bill-sync
Save a connection's expense bill mode and start date, and optionally switch landed cost bill sync on or off.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Choosing send also queues the existing expense bills it now covers (unlinked, dated on or after the start date, from suppliers without their own rule). That runs in the background: the response carries tracked_job_log_id, which you can poll with GET /api/tracked-job-logs/{trackedJobLog}. For other modes it is null. Bills already linked to the provider stay linked; nothing is voided. Call Preview Bill Sync Change first to see what a change would do.
Request fields:
mode(required) -send,provider_ownedorsku_only.start_date(optional, Y-m-d) - only send bills dated on or after this date. Send null to remove the limit.landed_cost_enabled(optional, boolean) - switch landed cost bill sync on or off. Omit to leave it unchanged.connection_id(optional, integer) - the connection to change. Defaults to the first Xero / QuickBooks connection.
Modes:
send- SKU.io sends its expense bills to the provider.provider_owned- the provider owns expense bills; keep entering them there and bring them into SKU.io with the provider bill review endpoints. SKU.io does not send them.sku_only- expense bills stay in SKU.io and are never sent.
Returns 422 when there is no Xero or QuickBooks connection, the connection is unknown, or a field is invalid. Response data is the same shape as Get Bill Sync Settings plus tracked_job_log_id.
Authentication: Requires Bearer token. Scope: accounting (read/write). The user must hold the Manage bill sync permission (accounting.bill_sync).
Request
Responses
- 200
- 401
- 403
- 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.
Unprocessable Content
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.