Send Numeral Sales History
POST/api/numeral/instances/:instance/backfill
Starts a background send of every reportable sale dated on or after start_date (named "Numeral: send sales history (since YYYY-MM-DD)"). Live changes are always sent before history. Moves the connection start date earlier when needed. Cancelling the background job holds every not-yet-sent history record (reason backfill_cancelled); records already sent stay sent. Sending must be switched on first (422 push_disabled). Only one history send runs at a time (422 backfill_running with the running tracked_job_log_id).
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body fields:
- start_date (date, Y-m-d, required, not in the future).
Returns the background job id to track progress.
Authentication: Requires a Bearer token. Requires the integrations.sync permission.
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.