List Target Plus Fulfillments
GET/api/target-plus/:integrationInstance/fulfillments
Paginated list of shipped SKU.io fulfillments on this integration's Target Plus orders, with each one's tracking-push state.
integrations:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
submission.status: submitted (Target has every tracking number), pending (not tried yet), blocked (a check stopped it before anything was sent: unmapped shipping method, carrier Target does not accept, missing tracking number, ship date in the future; reason says which and fix names where to fix it: settings-shipping or sales-order), failed (Target refused it or could not be reached; retried on a growing wait that never stops).
Archived fulfillments are excluded unless filter[archived.is] is sent.
Allowed sorts: id, fulfilled_at, tracking_number, submitted_to_sales_channel_at, created_at, updated_at (prefix with - for descending; default -id).
Request
Responses
- 200
- 401
- 403
- 404
- 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.
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.