curl --request GET \
--url https://api.gigstack.io/v2/teams/integrations \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/teams/integrations', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/teams/integrations"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"message": "API Key inválida.",
"details": "Invalid API Key"
}Get team integrations (not implemented)
Not yet available. The route is registered and reachable — it is declared before
/teams/{id} so it is no longer shadowed by the team-lookup route — but the handler is
still a stub that returns 501 Not Implemented for every request. It never returns
integration data.
Do not build against this endpoint yet. This entry exists so the published surface matches the deployed behavior.
curl --request GET \
--url https://api.gigstack.io/v2/teams/integrations \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/teams/integrations', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/teams/integrations"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"message": "API Key inválida.",
"details": "Invalid API Key"
}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
Response
Rejected by the authentication layer after the credential was recognised. The body is a raw
object (message, sometimes details), not the standardized envelope. Causes:
- The API key was revoked or disabled:
message: "API Key inválida.",details: "Invalid API Key". - The billing account's plan does not include API access.
messageis a Spanish sentence containing an HTML link tohttps://app.gigstack.pro/memberships. Branch on the status code; do not display or match the text. - gigstack Connect: the plan lacks the
multipleIssuerAccountsfeature (Spanish message startingTu plan no incluye múltiples cuentas emisoras.), or an OAuth access token was sent with ateamother than its own (Team mismatch with OAuth token).
An endpoint may also answer 403 for its own reasons; those are documented on the
operation when they exist.
Raw error body produced by the authentication layer (before any endpoint runs). It is not
the standardized envelope: there is no success and no timestamp.
Human-readable reason. Some messages are in Spanish; branch on the HTTP status, not on this text.
"Unauthorized"
OAuth error code. Present only when an OAuth access token was presented.
invalid_token, token_expired, token_revoked, server_error "token_expired"
Same text as message. Present only alongside error.
"Access token has expired. Please refresh your token."
Extra detail, e.g. Invalid API Key when a revoked key is rejected with 403.
"Invalid API Key"