Remove a Stripe Connect return domain
Remove a return domain of your account; responds 204 with no body. - Later return_url values on that host are rejected with 422 connect_return_url_not_allowed; started authorizations keep theirs. - An unknown domain, or one of another account, returns 404 connect_return_domain_not_found. - Needs a live key from an owner or admin; undo by adding the host again.
Your API key as a bearer token: fact_live_… in production, fact_test_… in sandbox. See the authentication guide.
In: header
Path Parameters
Public identifier (UUID v7) of your account. Get it from GET /v1/me (data.account.id).
uuidPublic identifier (UUID v7) of the return domain.
uuidHeaders
Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide.
1 <= length <= 255Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.
dateResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json