Account

Add a Stripe Connect return domain

Allow a host as the return_url destination of Stripe Connect authorizations started by your account.

  • domain is the bare lower-cased host (422 subcode invalid_return_domain).
  • Returns 201 without Location; a duplicate returns 409 connect_return_domain_already_exists.
  • Needs a live key from an owner or admin.
post/accounts/{account}/connected-accounts/return-domains

Request

  • Base URL: https://api.factuarea.com/v1
  • URL: https://api.factuarea.com/v1/accounts/{account}/connected-accounts/return-domains
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Path parameters

accountstring uuid required

Public identifier (UUID v7) of your account. Get it from GET /v1/me (data.account.id).

Headers

Idempotency-Keystring
Example:01928f10-7c0e-7c4a-9b7d-2f8a6e3c1d4b

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.

Factuarea-Versionstring date
Example:2026-06-01

Pin 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.

Request body

domainstring required

Host that may be used in the return_url of an authorization, for example app.example.com (up to 253 characters). Host only: no scheme, no port, no path and no wildcard. It is normalized to lower case, so App.Example.com and app.example.com are the same domain.

Response

The return domain was registered. There is no Location header: a return domain has no individual read; use the list.

Example response

{
  "data": {
    "id": "01993c4f-52b8-7c16-a3d9-4e7b1f2c8a30",
    "object": "connect_return_domain",
    "domain": "portal.example.com",
    "created_at": "2026-10-05T10:15:00+00:00"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.