curl --request DELETE \
--url https://api.gigstack.io/v2/users/{id} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/users/{id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/{id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"message": "User deleted successfully",
"timestamp": 1767225600000,
"data": {
"id": "user_1234567890",
"deleted": true,
"account_deleted": true,
"removed_from_teams": [
"team_1234567890"
]
}
}Delete user
Availability: This operation has no configured public API gateway route and is not available through the documented base URL.
Remove a user from your teams, and delete their account when it is yours.
The user must be a member of the team the request is authenticated for. They are removed from every team of your billing account you administer: your own team, and (for a master-team API key, or a dashboard admin) its sibling teams. Memberships in teams you do not administer are left untouched.
The login (Firebase Auth) and the users/{id} document are deleted only when that
leaves the user in no team at all and the account belongs to your billing account
(created by it, or tied to no other billing account, and not the owner of one). Otherwise
the user keeps their login, and account_deleted is false. An Auth deletion failure is
logged but does not fail the request.
You cannot delete yourself. If the id matches the user behind the API key the call
is rejected with 400 / business_rule_violation.
gigstack Connect: Delete other teams’ users using the team parameter.
curl --request DELETE \
--url https://api.gigstack.io/v2/users/{id} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/users/{id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/{id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"message": "User deleted successfully",
"timestamp": 1767225600000,
"data": {
"id": "user_1234567890",
"deleted": true,
"account_deleted": true,
"removed_from_teams": [
"team_1234567890"
]
}
}Authorizations
Authentication Method: HTTP Bearer token.
The runtime requires the literal Bearer prefix — a bare token in the
Authorization header is rejected with 401 unauthorized.
Header Format: Authorization: Bearer YOUR_API_KEY
Your API key is a JWT. Live keys operate on live data (livemode: true);
test keys operate on isolated test data (livemode: false).
Get your key at: app.gigstack.pro/settings?tab=api
Errors: credential failures are answered by the authentication layer with a raw
{ "message": … } body, not the standardized envelope — 401 for a missing, malformed or
expired token, 403 for a revoked key or a plan without API access. See the Unauthorized
and AuthForbidden responses.
Path Parameters
Id of the user to delete.
Query Parameters
gigstack Connect: Target team ID for multi-team access.
Requires gigstack Connect enabled on your team and shared billing account.
Also requires the multipleIssuerAccounts feature on your plan. Requests targeting a
team other than the one your API key belongs to return 403 without it.
Only API keys can use it: an OAuth access token sent with another team's id is rejected with
403 Team mismatch with OAuth token.
Optional — omit it entirely unless you are acting on another team. It deliberately
carries no example value so generated snippets do not emit ?team=undefined; when the
parameter is absent, the team is derived from your API key.
Example: ?team=team_xyz789
Response
User deleted successfully.
Standardized success envelope emitted by sendSuccessResponse.
true true
The operation payload.
Show child attributes
Show child attributes
Server time in epoch milliseconds (Luxon.now().toMillis()).
1767225600000
Human-readable summary. Present only when the handler supplies one.
"Operation completed successfully"