---
title: "Add a Stripe Connect return domain"
method: POST
path: "/accounts/{account}/connected-accounts/return-domains"
tags: ["Account"]
---

# Add a Stripe Connect return domain

`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`

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.

## Path parameters

- `account` string, uuid, required

## Headers

- `Idempotency-Key` string
- `Factuarea-Version` string, date

## Request body

- AddConnectReturnDomainV1Request: Register a return domain of your account. `domain` is required: the host only (up to 253 characters), without scheme, port or path; it is lower-cased and normalized, wildcards are rejected, and a host that is not a valid public name returns 422 `business_rule_violation` with subcode `invalid_return_domain`. Any other key in the body or the query returns 400 `parameter_unknown`.
  - `domain` string, 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 `201`

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

- object
  - `data` ConnectReturnDomain, required: A host your account allows as the destination of the `return_url` of Stripe Connect authorizations.
    - `id` string, uuid, required: Opaque identifier (UUID v7) of the return domain.
    - `object` 'connect_return_domain', required: Always `connect_return_domain`.
    - `domain` string, required: The host, lower-cased and normalized: no scheme, port, path or wildcard.
    - `created_at` string, date-time, required: Instant the domain was registered.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company. `account_not_found`: the account in the path does not exist or is not the account of the API key.
- `409`: The request conflicts with data that already exists or with a request running at the same time. `connect_return_domain_already_exists`: that host is already one of the return domains of your account. It is not an error to keep it: use the list operation to see it. The `param` is `domain`.
- `422`: Validation failed — e.g. the API key plan limit was reached, or an invoice language outside the allowed catalog (`es`, `en`, `ca`). The `error.param` field identifies which input is invalid, if any.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)