SyncList sync-notification subscriptions

List sync-notification subscriptions

Endpoints of yours that Mythic forwards Airbyte sync notifications to.

Airbyte allows exactly ONE webhook URL per event type per workspace, and Mythic holds it — every figure under /sync-events, /stats, /health and each connection's last_sync is built from those posts. Rather than take the slot from us, subscribe here: our receiver writes its own record and then relays the event to each subscription.

The returned url is REDACTED. Every query-string value is replaced with ***, because the credential for these endpoints normally lives in the query string. The full URL is stored encrypted and is never readable back through the API.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/airbyte/webhooks" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": [
    {
      "id": "123e4567-e89b-12d3-a456-426614174000",
      "label": "example_string",
      "url": "https://example.com/hooks/airbyte?secret=***",
      "active": true,
      "last_delivery_at": "2024-12-25T10:00:00Z",
      "last_error": "example_string",
      "consecutive_failures": 42,
      "created_at": "2024-12-25T10:00:00Z"
    }
  ]
}
GET
/webhooks
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key as bearer token, format Bearer ak_.... Grants full read-write access scoped to the agency. Agency-wide scoped keys (mcp_ with no fixed location) are accepted too and need airbyte:read or airbyte:write; a client-bound mcp_ key gets 403 agency_key_required. See Using an mcp_ key over HTTP.

Agency key as bearer token, format Bearer ak_.... Grants full read-write access scoped to the agency. Agency-wide scoped keys (mcp_ with no fixed location) are accepted too and need airbyte:read or airbyte:write; a client-bound mcp_ key gets 403 agency_key_required. See Using an mcp_ key over HTTP.
Bearer Token
Bearer Tokenstring
Required

Location secret key as bearer token, format Bearer sk_.... Grants read-only access; the agency is resolved from the location. Write endpoints return 403.

Location secret key as bearer token, format Bearer sk_.... Grants read-only access; the agency is resolved from the location. Write endpoints return 403.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key as bearer token, format Bearer ak_.... Grants full read-write access scoped to the agency. Agency-wide scoped keys (mcp_ with no fixed location) are accepted too and need airbyte:read or airbyte:write; a client-bound mcp_ key gets 403 agency_key_required. See Using an mcp_ key over HTTP.

header
Authorizationstring
Required

Bearer token. Location secret key as bearer token, format Bearer sk_.... Grants read-only access; the agency is resolved from the location. Write endpoints return 403.

Responses

successboolean
dataarray