curl --request POST \
--url https://api.gigstack.io/v2/users/login-link \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"user_id": "abc123xyz"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({user_id: 'abc123xyz'})
};
fetch('https://api.gigstack.io/v2/users/login-link', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/login-link"
payload = { "user_id": "abc123xyz" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"data": {
"login_link": "https://app.gigstack.pro/auth/token-login?token=<single-use-token>",
"valid_until": 1767229200000,
"method": "token"
},
"message": "Login link generated",
"timestamp": 1767225600000
}Generate login link
Generate a login link for a user. The link contains a custom Firebase token that allows the user to authenticate directly.
Requirements:
- User must have been created via API (
from: 'api') - User must belong to the billing account making the request
If requirements are not met, returns a 404 error.
gigstack Connect: Generate login links for other teams’ users using the team parameter.
curl --request POST \
--url https://api.gigstack.io/v2/users/login-link \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"user_id": "abc123xyz"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({user_id: 'abc123xyz'})
};
fetch('https://api.gigstack.io/v2/users/login-link', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/login-link"
payload = { "user_id": "abc123xyz" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"data": {
"login_link": "https://app.gigstack.pro/auth/token-login?token=<single-use-token>",
"valid_until": 1767229200000,
"method": "token"
},
"message": "Login link generated",
"timestamp": 1767225600000
}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.
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
Body
The Firebase UID of the user
"abc123xyz"