Remove a member from the account
Remove a member from the WHOLE account: it loses every grant, session and API-key scope there. Irreversible.
- To remove access to one tax ID, revoke that grant instead. Returns 204.
- 422 member_is_last_owner for the owner (transfer ownership first); 422 business_rule_violation when removing yourself.
- 404 member_not_found if unknown or of another account. Requires the members:write scope, which * does not cover: the API key must list it explicitly.
Request
- Base URL: https://api.factuarea.com/v1
- URL: https://api.factuarea.com/v1/accounts/{account}/members/{member}
- Auth: one of:
- HTTP bearer
- API key in header X-API-Key
Path parameters
Public identifier (UUID v7) of your account. Get it from GET /v1/me (data.account.id).
Public identifier (UUID v7) of the account member.
Headers
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. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.
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.
Response
No content
Changes
No recorded changes to this operation across all 1 revision of this API.