Create Integration Instance

POST 
/api/shipfusion/integration-instances

Create a new Shipfusion integration instance.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Authentication: Requires Bearer token.

Request Body:

• name (string, required) — Unique name for the integration instance
• integration_id (integer, required) — ID of the integration record (must exist in integrations table)
• connection_settings (object, optional) — Shipfusion API credentials
  • username (string) — Shipfusion API username
  • password (string) — Shipfusion API password
• integration_settings (object, optional) — Integration behavior settings
  • enable_fulfillment (boolean) — Enable automated fulfillment via Shipfusion
  • pass_tags (boolean) — Pass order tags to Shipfusion
• is_automatic_sync_enabled (boolean, optional, default: false) — Enable automatic order/inventory syncing

Request

Responses

201

Created

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

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.

422

Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.

429

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.