# Connect an apideck-backed service

> POST /connections/apideck/{service_id}/connect

Source: https://docs.trykintsugi.com/reference/2026-07-21/connect-an-apideck-backed-service

POST /connections/apideck/{service_id}/connect

Connect an apideck-backed service

Open an Apideck Vault session to connect one of the Apideck-backed services (BigCommerce, QuickBooks, Deel, Rippling, Gusto, WooCommerce, Amazon Seller Central, Etsy, Walmart, Magento, Shopware, Xero, NetSuite, Sage Intacct, Wix, Microsoft Dynamics 365 Business Central, DualEntry, Intuit Enterprise Suite). The returned `token` opens the Vault widget; complete the OAuth/credential flow there, then call the activate route with the resulting `connectionId`. `shopId`/`shopUrl` apply only to Shopware. A multi-org credential must send an `Organization-Id`, `Connection-Id` or `Entity-Id` selector, or gets a 400. Returns 503 if the Vault session call fails; retrying may succeed.

Category: Connections

Path parameters:
service_id (ApiDeckServiceEnum, required) - The Apideck service to connect.
  allowed values: bigcommerce, quickbooks, deel, rippling, gusto, woocommerce, amazon-seller-central, etsy, walmart, magento, shopware, xero (and 6 more, see the reference page)

Request body:
defaultCountry (CountryCodeEnum) - Default country for transactions imported through this connection.
  allowed values: AF, AX, AL, DZ, AS, AD, AO, AI, AQ, AG, AR, AM (and 239 more, see the reference page)
shopId (string) - Shopware only: the shop's Apideck shop id.
shopUrl (string) - Shopware only: the shop's storefront URL.

Response fields:
connectionId (string, required) - The new connection's id, INACTIVE until Vault activation completes.
token (string, required) - Apideck Vault session token to open the connect widget.

Response statuses: 200, 400, 401, 403, 404, 422, 503

---

Index of every page: https://docs.trykintsugi.com/llms.txt