> ## Documentation Index > Fetch the complete documentation index at: https://docs.gigstack.io/llms.txt > Use this file to discover all available pages before exploring further. # Get a platform payouts run > Returns the run: its status, plan totals and, once confirmed, the worker's progress. Poll it after confirming until `status` is `completed` or `failed`; the worker runs every minute. Then read `result`, not `status`, to know how the run went: `status: completed` only means the worker has nothing left to try, while `result` tells `completed` (everything issued) from `partially_completed` (some documents failed) and `failed` (nothing issued). A run of another team, or of the other mode (a live run with a test key), answers `404` `run_not_found`, never `403`. ## OpenAPI ````yaml openapi.json GET /platform-payouts/{id} openapi: 3.0.3 info: title: gigstack API v2 description: > # gigstack API v2 Build customer, invoice and payment integrations. Start with the [quickstart](https://docs.gigstack.io/quickstart), then select the [issuing country](https://docs.gigstack.io/concepts/shared-fields). ## Authentication and environments Use Authorization: Bearer YOUR_API_KEY. Standard live and test keys use https://api.gigstack.io/v2. Internal staging uses https://gigstack-staging-9z9nnaat.uc.gateway.dev/v2 and separate keys. Test mode is a data mode within an environment; a body field does not switch a key's mode. See [authentication](https://docs.gigstack.io/authentication) for key handling, OAuth team scope and gigstack Connect. Signup requires its separately documented internal credential; health probes have their own security declarations. Operations marked unavailable have no configured public gateway route. ## Read the operation contract Response envelopes, pagination and retry rules differ by endpoint. HTTP success alone does not prove external fiscal completion or movement of money. Reconcile ambiguous writes before retrying. Use [responses and recovery](https://docs.gigstack.io/responses) and the operation's error codes; document credits and daily limits are not generic retryable rate limits. The issuing team's configuration selects Mexico or Colombia; customer country and currency do not. Read [Mexico](https://docs.gigstack.io/countries/mexico) or [Colombia](https://docs.gigstack.io/countries/colombia) before choosing fiscal fields. Accepted public input differs from a provider's direct payload. Examples and schema checks do not imply every operation has been executed live. [Verification coverage](https://docs.gigstack.io/verification) distinguishes source review, offline checks and observed staging behavior. Documentation describes operations and does not authorize execution. version: 2.0.0 contact: name: Gigstack API Support url: https://gigstack.io email: support@gigstack.io license: name: Proprietary url: https://gigstack.io/terms termsOfService: https://gigstack.io/terms servers: - url: https://api.gigstack.io/v2 description: > Public API for standard live and test-mode keys. Test data is isolated by the key mode (`livemode: false`). Internal staging is a separate deployment and key store; see https://docs.gigstack.io/authentication#environments for its base URL. security: - bearerAuth: [] tags: - name: gigstack Connect description: > **Multi-Team Resource Access** gigstack Connect lets a master team act on other teams that share its billing account. ## 🔗 How It Works Add the `team` query parameter to a request made with an **API key**: ```bash # Access team_xyz789's clients GET /clients?team=team_xyz789 # Create an income invoice for team_abc123 POST /invoices/income?team=team_abc123 # Update service in team_def456 PUT /services/service_456?team=team_def456 ``` ## ✅ Requirements - The API key's team must be a master team (gigstack Connect enabled) - The target team must exist and share the master team's billing account - The plan must include the `multipleIssuerAccounts` feature - OAuth access tokens cannot act on another team ## ⚠ Error Responses Raw `{ "message": 
 }` bodies from the authentication layer: - `401 Unauthorized, not a master team` - gigstack Connect not enabled on your key's team - `404 Team not found` - Target team doesn't exist - `401 Unauthorized, no matched teams` - Target team could not be resolved within your billing account - `403 Tu plan no incluye mĂșltiples cuentas emisoras. 
` - Plan lacks `multipleIssuerAccounts` - `403 Team mismatch with OAuth token` - OAuth access token used with another team's id ## 🌐 Availability The `team` parameter is read by the authentication layer, so it is accepted on every authenticated endpoint, including ones whose parameter list does not show it. - name: Clients description: Client management operations with Mexican tax compliance - name: Services description: Service and product catalog management with SAT product keys - name: Invoices description: Invoice management with CFDI 4.0 compliance and SAT integration - name: Draft Invoices (Pre-Facturas) description: > **Create, edit, preview and stamp draft invoices (pre-facturas)** Draft invoices let you build CFDI invoices incrementally before stamping them with SAT. Use them as **pre-facturas** — generate a preview PDF with a "Sin Validez Fiscal" watermark to share with your client for approval, then stamp the draft to create a valid CFDI when ready. ## Typical Workflow 1. `POST /invoices/draft` — Create a draft with minimal data 2. `PUT /invoices/draft/{id}` — Update as more data becomes available 3. `POST /invoices/draft/{id}/preview` — Generate a preview PDF (pre-factura) 4. `POST /invoices/draft/{id}/stamp` — Finalize into a valid CFDI invoice - name: Descarga Masiva SAT description: > **SAT bulk invoice download via FIEL authentication** Download all your issued and received CFDI invoices directly from the SAT (Servicio de AdministraciĂłn Tributaria) using your FIEL (Firma ElectrĂłnica Avanzada). ## Setup flow 1. `GET /invoices/download/activate/status` — Check if activated and what's needed 2. `POST /invoices/download/activate` — Activate billing (adds Stripe meter/add-on) 3. `POST /invoices/download/fiel` — Upload `.cer` + `.key` files (auto-registers with SAT) 4. `PUT /invoices/download/schedule` — Configure daily auto-sync 5. `POST /invoices/download/request` — Submit manual download requests ## Pricing - Included in Pro/Business plans: only the download meter ($0.20 MXN/XML) - Other paid plans: the same $0.20 MXN/XML download meter, no monthly base fee - name: Payments description: Payment processing, tracking, and refund management - name: Receipts description: Receipt creation and management with CFDI stamping capabilities - name: Retentions description: >- Tax retention documents (CFDI Retenciones 2.0) — creation, stamping, cancellation, and file retrieval - name: Platform Payouts description: > **Plan and stamp a marketplace's provider payouts from two files.** For marketplaces and digital platforms that pay providers under the SAT digital-platforms scheme (Plataformas TecnolĂłgicas, RESICO 625, retention key 26): ride-hailing drivers, delivery couriers, lodging hosts, sellers of goods. Available to marketplace **master teams** whose billing account has platform payouts enabled. Upload a movements file and a commissions file. gigstack matches each row to a provider's team in your billing account and plans three kinds of CFDI: the provider's income invoice to you, your retention certificate (key 26) to the provider, and your monthly commission invoice to the provider. **Not for your own sales.** This is for a platform invoicing on behalf of its providers. A company invoicing its own sales, one CFDI per sale, should use `POST /invoices/income`. **Tax policy per account.** Which documents are issued, and with which SAT keys and rates, is set per master account at onboarding: allowed tax regimes, CSD requirement, service type (`tipoDeServ` / `subTipServ`), ISR and IVA withholding rates, product keys and concept descriptions. The defaults are for ground passenger transport (service type `01`, 2.1% ISR withholding). Contact support to configure your account's policy; it can't be changed through the API. 1. `POST /platform-payouts` with an `Idempotency-Key` - upload and plan (synchronous) 2. `GET /platform-payouts/{id}` and `GET /platform-payouts/{id}/movements` - review the plan 3. `POST /platform-payouts/{id}/confirm` - irreversible hand-off to the stamping worker 4. `GET /platform-payouts/{id}` - poll until `completed` or `failed`, then read `result` (`completed`, `partially_completed` or `failed`) Error messages and exclusion reasons are Spanish sentences for end users; branch on `error.code`, `reason_code` and `exclusion_codes`. - name: Documents description: > SAT supporting documentation (contracts, delivery/payment proofs, communications) — upload metadata, compliance review, AI extraction, and linking to invoices, payments, receipts and clients. - name: Teams description: Team management, settings, and member administration - name: Users description: User account management and password operations - name: Auth description: > **API-only signup for AI agents and partner integrations.** A single `POST /v2/auth/signup` call provisions a Firebase Auth user, billing account, team, plan subscription, and returns API keys — no UI, no FIEL upload, no human onboarding required. Designed for the AI-agents-as-customers use case. RFC defaults to genĂ©rico (`XAXX010101000`) so agents can transact under pĂșblico en general until/unless their customer uploads their own RFC. Authenticated with `X-Internal-API-Key` (partner-issued) — Bearer tokens are team-scoped and a brand-new caller doesn't have one yet. See `AGENTS.md` in the gigstack-cli repo for end-to-end integration guide. - name: Webhooks description: Webhook management for real-time event notifications - name: Catalogs description: > **Read-only search over the SAT catalogs** Look up the SAT codes required on CFDI line items without hardcoding them: - `GET /catalogs/product-keys` — `c_ClaveProdServ`, the item `product_key` - `GET /catalogs/unit-keys` — `c_ClaveUnidad`, the item `unit_key` / `unit_name` Both are typo-tolerant full-text searches ranked by relevance. The catalogs are published by the SAT and identical for every team, so results carry no team data and ignore `livemode` — but a valid API key is still required. - name: SAT Lists description: > Read-only access to the RFC lists the SAT publishes under ArtĂ­culo 69, 69-B and 69-B Bis. gigstack re-syncs all 22 lists from the SAT's published CSVs every Sunday, so you can screen a counterparty's RFC before invoicing it without scraping the SAT yourself. externalDocs: description: Complete API Documentation & Guides url: https://docs.gigstack.io paths: /platform-payouts/{id}: get: tags: - Platform Payouts summary: Get a platform payouts run description: > Returns the run: its status, plan totals and, once confirmed, the worker's progress. Poll it after confirming until `status` is `completed` or `failed`; the worker runs every minute. Then read `result`, not `status`, to know how the run went: `status: completed` only means the worker has nothing left to try, while `result` tells `completed` (everything issued) from `partially_completed` (some documents failed) and `failed` (nothing issued). A run of another team, or of the other mode (a live run with a test key), answers `404` `run_not_found`, never `403`. operationId: getPlatformPayoutRun parameters: - name: id in: path required: true description: Run id, as returned by `POST /platform-payouts`. schema: type: string pattern: ^batchrun_[A-Za-z0-9]{6,40}$ example: batchrun_3f9a1c7e2b4d6f8a0c1e3a5b7d9f1a2c responses: '200': description: > The run. Once it is finished, `result` says how it went: `completed`, `partially_completed` or `failed`. content: application/json: schema: allOf: - $ref: '#/components/schemas/StandardSuccessResponse' - type: object properties: data: $ref: '#/components/schemas/ApiPublicPlatformPayoutRun' examples: stamping: summary: Confirmed, worker in progress value: success: true data: id: batchrun_3f9a1c7e2b4d6f8a0c1e3a5b7d9f1a2c status: stamping result: null livemode: true team: team_1234567890 created_at: 1788220800000 plan_ready_at: 1788220804120 confirmed_at: 1788221400000 completed_at: null files: movements: movimientos-agosto-2026.csv commissions: comisiones-agosto-2026.xlsx months: - 2026-08 total_movements: 412 included_count: 398 excluded_count: 14 planned_documents: income: 398 certificate: 398 commission: 57 exclusion_summary: Sin sellos (CSD) en Gigstack: 9 El proveedor no tiene cuenta en Gigstack: 5 exclusion_code_summary: missing_csd: 9 provider_not_found: 5 progress: stamped_count: 120 failed_count: 2 income_invoices_count: 122 certificates_count: 120 commission_invoices_count: 0 commission_failed_count: 0 income_invoices_amount: 161497.5 error: null timestamp: 1788221700000 partially_completed: summary: Finished, some documents failed value: success: true data: id: batchrun_3f9a1c7e2b4d6f8a0c1e3a5b7d9f1a2c status: completed result: partially_completed livemode: true team: team_1234567890 created_at: 1788220800000 plan_ready_at: 1788220804120 confirmed_at: 1788221400000 completed_at: 1788224100000 files: movements: movimientos-agosto-2026.csv commissions: comisiones-agosto-2026.xlsx months: - 2026-08 total_movements: 412 included_count: 398 excluded_count: 14 planned_documents: income: 398 certificate: 398 commission: 57 exclusion_summary: Sin sellos (CSD) en Gigstack: 9 El proveedor no tiene cuenta en Gigstack: 5 exclusion_code_summary: missing_csd: 9 provider_not_found: 5 progress: stamped_count: 395 failed_count: 3 income_invoices_count: 397 certificates_count: 396 commission_invoices_count: 56 commission_failed_count: 1 income_invoices_amount: 525528.75 error: null timestamp: 1788224160000 '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/AuthForbidden' '404': description: > No run with this id in your team and mode (`run_not_found`). A user-scoped token whose user is not a member of the team gets `resource_not_found` (`Batch run not found`) instead. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' example: success: false error: code: run_not_found message: No encontramos esta corrida. timestamp: 1788221700000 '500': $ref: '#/components/responses/ServerError' security: - bearerAuth: [] components: schemas: StandardSuccessResponse: type: object description: | Standardized success envelope emitted by `sendSuccessResponse`. required: - success - data - timestamp properties: success: type: boolean enum: - true example: true data: type: object description: The operation payload. message: type: string description: Human-readable summary. Present only when the handler supplies one. example: Operation completed successfully timestamp: type: integer format: int64 description: Server time in **epoch milliseconds** (`Luxon.now().toMillis()`). example: 1767225600000 ApiPublicPlatformPayoutRun: type: object description: > A platform payouts run: the files it was planned from, the plan totals, and the stamping progress. Amounts are MXN in pesos (not cents). Timestamps are epoch milliseconds. required: - id - status - result - livemode - team - created_at - plan_ready_at - confirmed_at - completed_at - files - months - total_movements - included_count - excluded_count - planned_documents - exclusion_summary - exclusion_code_summary - progress - error properties: id: type: string description: > Run id. Derived from your team, the key's mode and the `Idempotency-Key` you sent, so the same key always names the same run. pattern: ^batchrun_[A-Za-z0-9]{6,40}$ example: batchrun_3f9a1c7e2b4d6f8a0c1e3a5b7d9f1a2c status: $ref: '#/components/schemas/PlatformPayoutRunStatusEnum' result: $ref: '#/components/schemas/PlatformPayoutRunResultEnum' livemode: type: boolean description: >- Mode of the credential that created the run. A test key only ever sees test runs. example: true team: type: string description: The master team the run issues from. example: team_1234567890 created_at: type: integer format: int64 description: When the run was created (epoch ms). example: 1788220800000 plan_ready_at: type: integer format: int64 nullable: true description: >- When planning ended, successfully (`plan_ready`) or not (`plan_failed`). `null` while `planning`. example: 1788220804120 confirmed_at: type: integer format: int64 nullable: true description: When the run was confirmed for stamping. `null` until then. example: null completed_at: type: integer format: int64 nullable: true description: >- When the worker finished (`completed`) or stopped the run (`failed`). `null` otherwise. example: null files: type: object description: Names of the uploaded files, as sent. required: - movements - commissions properties: movements: type: string example: movimientos-agosto-2026.csv commissions: type: string example: comisiones-agosto-2026.xlsx months: type: array description: The `YYYY-MM` months present in the movements file, ascending. items: type: string example: 2026-08 total_movements: type: integer description: Rows read from the movements file. example: 412 included_count: type: integer description: Movements with at least one document to issue. example: 398 excluded_count: type: integer description: Movements with nothing to issue (see `exclusion_summary`). example: 14 planned_documents: type: object description: > CFDIs the plan will issue, by kind. `income`: one invoice per movement, issued by the provider's team to the master team. `certificate`: one retention certificate (Constancia de Retenciones, key 26) per movement, issued by the master team to the provider. `commission`: one invoice per provider-month from the commissions file, issued by the master team to the provider. required: - income - certificate - commission properties: income: type: integer example: 398 certificate: type: integer example: 398 commission: type: integer example: 57 exclusion_summary: type: object description: > Excluded movements, counted by reason, for people. Keys are the Spanish reason sentences shown to users (free text that may be reworded); a movement excluded for two reasons has them joined with ` · `. Programs should read `exclusion_code_summary` instead. additionalProperties: type: integer example: Sin sellos (CSD) en Gigstack: 9 El proveedor no tiene cuenta en Gigstack: 5 exclusion_code_summary: type: object description: > Excluded movements, counted by exclusion code (see `PlatformPayoutExclusionCode`), for programs. Keys are exclusion codes; only codes that occur are present. A movement excluded for two different reasons counts once under **each** of its codes, so the values can add up to more than `excluded_count`. `{}` on runs planned before codes existed. properties: invalid_row: type: integer provider_not_found: type: integer missing_tax_id: type: integer missing_legal_name: type: integer missing_zip: type: integer missing_fiscal_data: type: integer csd_expired: type: integer missing_csd: type: integer tax_system_not_allowed: type: integer duplicate_tax_id: type: integer name_mismatch: type: integer missing_series: type: integer public_general_not_allowed: type: integer certificate_month_reserved: type: integer missing_commission: type: integer zero_commission: type: integer additionalProperties: type: integer example: missing_csd: 9 provider_not_found: 5 progress: type: object description: > What the worker has done so far. All zero until the run is confirmed. `stamped_count` and `failed_count` count **movements**; the three `*_count` document counters count comprobantes. required: - stamped_count - failed_count - income_invoices_count - certificates_count - commission_invoices_count - commission_failed_count - income_invoices_amount properties: stamped_count: type: integer description: Movements whose planned documents were all stamped. example: 0 failed_count: type: integer description: > Movements with at least one document that failed for good. Does not include commission invoices (see `commission_failed_count`). example: 0 income_invoices_count: type: integer description: Income invoices stamped. example: 0 certificates_count: type: integer description: Retention certificates stamped. example: 0 commission_invoices_count: type: integer description: Commission invoices stamped. example: 0 commission_failed_count: type: integer description: >- Commission invoices that failed for good. `0` on runs counted before it existed. example: 0 income_invoices_amount: type: number description: Sum of the totals of the stamped income invoices, MXN. example: 0 error: type: string nullable: true description: >- Why the plan (`plan_failed`) or the run (`failed`) failed, as a Spanish sentence for end users. `null` otherwise. example: null StandardErrorResponse: type: object description: > Standardized error envelope emitted by `sendErrorResponse` and its helpers (`sendValidationError`, `sendNotFoundError`, `sendUnauthorizedError`, `sendForbiddenError`, `sendConflictError`, `sendBadRequestError`, `sendInternalServerError`). required: - success - error - timestamp properties: success: type: boolean enum: - false example: false error: type: object required: - code - message properties: code: type: string description: > Stable machine-readable code. Values emitted by the shared helpers: `unauthorized`, `forbidden`, `invalid_token`, `validation_failed`, `invalid_request_body`, `missing_required_field`, `invalid_field_value`, `resource_not_found`, `resource_already_exists`, `resource_conflict`, `business_rule_violation`, `operation_not_allowed`, `insufficient_permissions`, `external_service_error`, `payment_processor_error`, `cfdi_service_error`, `internal_server_error`, `service_unavailable`, `rate_limit_exceeded`, `database_error`, `data_integrity_error`, `file_not_found`, `file_upload_error`, `invalid_file_format`. Individual handlers may emit additional endpoint-specific codes, documented per operation. example: validation_failed message: type: string example: Request validation failed details: oneOf: - type: string - type: array items: type: string description: > Present only when the handler supplies detail. Validation failures emit an array of `": "` strings. example: - 'currency: Field is required' timestamp: type: integer format: int64 description: Server time in epoch milliseconds. example: 1767225600000 PlatformPayoutRunStatusEnum: type: string description: > Where a platform payouts run is in its lifecycle. - `planning` - the files are being read and the plan computed. Normally only seen by a retry that arrives while the first request is still working. - `plan_ready` - the plan is computed and waiting for `POST /platform-payouts/{id}/confirm`. - `plan_failed` - the plan could not be computed (see `error`). Terminal: upload corrected files under a **new** `Idempotency-Key`. - `stamping` - confirmed; the background worker is issuing the CFDIs. - `completed` - the worker has nothing left to try. This says nothing about how much was issued: read the run's `result` (`completed`, `partially_completed` or `failed`) to know how it went. - `failed` - the worker stopped the whole run (see `error`), for example because the master team no longer has seals (CSD) or the run made no progress after repeated attempts. enum: - planning - plan_ready - plan_failed - stamping - completed - failed example: plan_ready PlatformPayoutRunResultEnum: type: string nullable: true description: > How a finished run turned out. `null` while the run is not finished (`planning`, `plan_ready`, `plan_failed`, `stamping`). Read this, not `status`, to know how a run went: - `completed` - no document failed: everything planned was issued. - `partially_completed` - some documents failed and at least one was issued. - `failed` - the run itself failed (`status: failed`), or it finished having issued nothing while something failed. Counted as: failures = `progress.failed_count` (movements with at least one failed document) + `progress.commission_failed_count`; issued = `income_invoices_count` + `certificates_count` + `commission_invoices_count`. enum: - completed - partially_completed - failed - null example: partially_completed AuthMiddlewareError: type: object description: > 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`. required: - message properties: message: type: string description: >- Human-readable reason. Some messages are in Spanish; branch on the HTTP status, not on this text. example: Unauthorized error: type: string description: >- OAuth error code. Present only when an OAuth access token was presented. enum: - invalid_token - token_expired - token_revoked - server_error example: token_expired error_description: type: string description: Same text as `message`. Present only alongside `error`. example: Access token has expired. Please refresh your token. details: description: >- Extra detail, e.g. `Invalid API Key` when a revoked key is rejected with `403`. oneOf: - type: string - type: object example: Invalid API Key UnauthorizedError: allOf: - $ref: '#/components/schemas/StandardErrorResponse' example: success: false error: code: unauthorized message: Unauthorized access timestamp: 1767225600000 responses: Unauthorized: description: > Authentication failed. Two different bodies can come back with a `401`: 1. **From the authentication layer**, before the endpoint runs: a raw object with `message` and — for OAuth access tokens only — `error` / `error_description`. It does **not** use the standardized envelope (`success` and `timestamp` are absent). Messages: `Unauthorized` (missing header, missing `Bearer ` prefix, unparseable token), `Unauthorized, missing team in token`, `Unauthorized, not a master team` and `Unauthorized, no matched teams` (gigstack Connect), `Invalid access token`, `Access token has expired. Please refresh your token.`, `Access token has been revoked`. 2. **From the endpoint itself**: the standardized envelope with `error.code: unauthorized`. Branch on the HTTP status, not on the body shape. content: application/json: schema: anyOf: - $ref: '#/components/schemas/AuthMiddlewareError' - $ref: '#/components/schemas/UnauthorizedError' examples: missing_or_invalid_key: summary: Authentication layer — missing or unparseable API key value: message: Unauthorized oauth_token_expired: summary: Authentication layer — expired OAuth access token value: message: Access token has expired. Please refresh your token. error: token_expired error_description: Access token has expired. Please refresh your token. connect_not_master_team: summary: >- Authentication layer — `team` sent by a team without gigstack Connect value: message: Unauthorized, not a master team endpoint_envelope: summary: Endpoint — standardized envelope value: success: false error: code: unauthorized message: Unauthorized access timestamp: 1767225600000 AuthForbidden: description: > 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. `message` is a Spanish sentence containing an HTML link to `https://app.gigstack.pro/memberships`. Branch on the status code; do not display or match the text. - gigstack Connect: the plan lacks the `multipleIssuerAccounts` feature (Spanish message starting `Tu plan no incluye mĂșltiples cuentas emisoras.`), or an OAuth access token was sent with a `team` other 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. content: application/json: schema: $ref: '#/components/schemas/AuthMiddlewareError' examples: revoked_api_key: summary: API key revoked or disabled value: message: API Key invĂĄlida. details: Invalid API Key plan_without_api_access: summary: Plan does not include API access value: message: >- La API se encuentra disponible para un plan mĂĄs grande, por favor actualiza tu plan aquĂ­ o ponte en contacto con soporte. connect_plan_without_multiple_issuers: summary: gigstack Connect — plan lacks multipleIssuerAccounts value: message: >- Tu plan no incluye mĂșltiples cuentas emisoras. Actualiza tu plan en https://app.gigstack.pro/memberships o ponte en contacto con soporte para operar sobre otros equipos. oauth_team_mismatch: summary: gigstack Connect — OAuth token used for another team value: message: Team mismatch with OAuth token ServerError: description: >- Unexpected server error (`error.code: internal_server_error`). The failure is logged on gigstack's side. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' example: success: false error: code: internal_server_error message: An internal server error occurred timestamp: 1767225600000 securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > **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](https://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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.