Resubmit Target Plus Fulfillment
POST/api/target-plus/:integrationInstance/fulfillments/:fulfillment/resubmit
Run the tracking push for one SKU.io fulfillment now (the same checks as the automatic push). Tracking numbers Target already has are never sent twice. Target emails the guest once it accepts a shipment.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
200 when Target has every tracking number; 422 when a check blocked it or Target refused it (the reason is in message); 409 when the push does not apply (writes to Target are turned off outside production, the Tracking sync is turned off, or the fulfillment is already submitted); 403 when the fulfillment is not on this integration's orders.
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
Response Headers
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.