Skip to main content

Create Target Plus Integration

POST 

/api/target-plus

Connects a Target Plus seller. The credentials are checked against Target first; then the integration is created and a background setup job syncs the seller's distribution centers and shipping methods. tracked_job_log_id identifies that job.

Required scope: integrations:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Body: name (required, unique across all integrations), seller_id (required, digits only — the Seller ID from the Target Plus Partner Portal, Business Info → Basic Info), api_token (required — generated in Partner Settings → API Token; Target shows it once and only portal admins can generate it), environment (optional, production only), store_id (optional, defaults to the account's default store), start_date (optional, Y-m-d, on or after the inventory start date), buyer_cancel_hold_minutes (optional, 0–120, default 30: how long SKU.io waits before creating a sales order, because the shopper can cancel within 30 minutes), auto_link_products, auto_create_products, is_automatic_sync_enabled (optional booleans), and five optional accounting nominal code IDs: sales_nominal_code_id, cogs_nominal_code_id, shipping_revenue_nominal_code_id, shipping_refund_nominal_code_id, sales_returns_allowances_nominal_code_id.

Connecting a Seller ID that is already connected returns 422 with existing_instance. Credentials Target rejects return 422 with the reason.

Request​

Responses​

Created

Response Headers
    Content-Type