Confirm Placement Option
POST/api/tiktok-shop/:integrationInstance/fbt/inbound-plans/:plan/placement/confirm
Confirm a placement option. This is the call that creates the inbound orders — one per allocation shipment — and moves the plan to CONFIRMED.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Body
option_id(integer, required) — the placement option's SKU.io id. It must belong to the plan in the path, otherwise the request answers404, and it must name a live offered option from the current generation.
Confirming is not idempotent at TikTok, so re-list the options and re-fetch the detail rather than reusing an id the client has been holding. The plan must be PLANNED with its source reservations in place — can_confirm and can_confirm_reason on the plan say whether it is.
The response returns the updated plan alongside the inbound orders that were created.
Requires the integrations.update 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 Content
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.