Reuse Existing Connection
POST/api/faire/instances/:integrationInstance/reuse-connection
Reuse the connection from another authorized Faire integration instance instead of authorizing again.
Why this exists: Faire allows only one live access token per brand, and the brand portal does not let you revoke or re-issue it. When you add a second Faire integration for the same brand — typically a Fulfilled-by-Faire (FBF) integration alongside an existing Fulfilled-by-Merchant (FBM) one — authorizing again could invalidate the first integration's token. Reuse copies the existing integration's long-lived token onto this one so both work on the same Faire account.
What it does:
- Copies the source integration's access token and scopes onto this integration
- Verifies the copied token against Faire before saving it (an invalid source connection is rejected, nothing is persisted)
- Records the Faire brand so both integrations are grouped as one shared connection
- After success,
is_authorizedbecomestrueandauth_methodisreused
Requirements: the source integration must be authorized and must have the opposite fulfillment mode (FBM ↔ FBF). Reusing from a same-mode integration is rejected, because one Faire account can only be one mode at a time.
Disconnecting a shared connection clears the token from that one integration only — it does not sign the shared Faire login out, so the other integration keeps working.
Path Parameters:
integrationInstance(required) — the integration receiving the reused connection
Request Body:
source_instance_id(required, integer) — the authorized, opposite-mode integration to copy the connection from
Auth: Requires Bearer token.
Errors:
422— the source does not exist, is not authorized, is the same integration, is the same fulfillment mode, or its token failed verification with Faire
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.