Submit Target Plus Fulfillments
POST/api/target-plus/:integrationInstance/fulfillments/submit-bulk
Queues a tracking push to Target Plus now for each chosen SKU.io fulfillment Target does not have yet, and returns how many were queued. Fulfillments Target already has, and archived ones, are skipped. Each push runs the same checks as the automatic push but does not wait for its retry delay; a push that is blocked or refused shows up in List Target Plus Fulfillments with its reason. Target emails the guest once it accepts a shipment.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
409 with the reason when no push can run: writes to Target are turned off outside production, or the Tracking sync is turned off for this integration.
Body: ids (required array of SKU.io fulfillment IDs, 1 to 5000). IDs that are not on this integration's orders are ignored.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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.
Conflict
Response Headers
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.