Backfill Shipment Trackings
POST/api/shipment-trackings/backfill
Kick off a background job that scans recent rows of the selected entity types and registers any that have a tracking_number but no shipment_trackings row yet.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Returns the tracked_job_log_id which can be polled for progress via the tracked job log endpoints.
Optional Fields:
entity_types— array of strings. Defaults to all five. Each value must be one of:sales_order_fulfillments,inbound_shipments,warehouse_transfer_shipments,rmas,vendor_credit_shipments.since_days— integer, 1–365. Defaults to 30. Look-back window in days.
Responses:
200 OK— backfill dispatched; payload containstracked_job_log_id422 Unprocessable Entitywithcode: not_connected— no active 17TRACK instance
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 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.