> ## 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. # Inspect remote Airtable webhooks > Requires a verified Firebase person or signed personal MCP credential and current team authority. Airtable uses one shared production connection; gigstack live/test mode controls imported payment records. This reads scoped metadata; it does not change provider state. HTTP 200 may contain processing or outcome_unknown; inspect data.status. See the Airtable lifecycle guide for pagination, shared effects and reviewed OAuth recovery. ## OpenAPI ````yaml openapi.json GET /teams/{id}/integrations/airtable/bases/{baseId}/webhooks/remote 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. Internal partner provisioning is outside this public contract; 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: [] externalDocs: description: Complete API Documentation & Guides url: https://docs.gigstack.io paths: /teams/{id}/integrations/airtable/bases/{baseId}/webhooks/remote: get: tags: - Account Integrations summary: Inspect remote Airtable webhooks description: >- Requires a verified Firebase person or signed personal MCP credential and current team authority. Airtable uses one shared production connection; gigstack live/test mode controls imported payment records. This reads scoped metadata; it does not change provider state. HTTP 200 may contain processing or outcome_unknown; inspect data.status. See the Airtable lifecycle guide for pagination, shared effects and reviewed OAuth recovery. operationId: listAirtableRemoteWebhooks parameters: - name: id in: path required: true schema: type: string pattern: ^[A-Za-z0-9_-]{1,128}$ - name: baseId in: path required: true schema: type: string pattern: ^[A-Za-z0-9_-]{1,128}$ responses: '200': description: Safe scoped result. Operation status determines completion. content: application/json: schema: type: object additionalProperties: false properties: success: type: boolean enum: - true data: $ref: '#/components/schemas/AirtableRemoteWebhooks' timestamp: type: number required: - success - data - timestamp example: success: true data: data: [] has_more: false next_cursor: null effect_scope: shared_connection provider_environment: production timestamp: 1700000000000 '400': description: Invalid identifier, mapping, mode assertion or acknowledgment. '401': description: Verified personal credential required. '403': description: Current account, membership or provider authority refused. '404': description: Resource unavailable in authorized scope. '409': description: >- Mode changed, setup/lifecycle locked, or uncertain recovery requires review. '503': description: Runtime environment or internal service authorization unavailable. '504': description: >- Result unknown. Keep operation_id and read the receipt; do not automatically repeat provider effects. security: - bearerAuth: [] components: schemas: AirtableRemoteWebhooks: type: object additionalProperties: false properties: data: type: array items: type: object additionalProperties: false properties: id: type: string notifications_enabled: type: boolean enabled: type: boolean expires_at: type: number nullable: true local_match: type: boolean required: - id - notifications_enabled - enabled - expires_at - local_match has_more: type: boolean next_cursor: type: string nullable: true effect_scope: type: string enum: - shared_connection provider_environment: type: string enum: - production required: - data - has_more - next_cursor - effect_scope - provider_environment 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.