Peliqan · AsyncAPI Specification

Peliqan Webhooks

Version

View Spec View on GitHub CompanyData PlatformAIETLReverse ETLAsyncAPIEvents

AsyncAPI Specification

peliqan-webhooks.yml Raw ↑
generated: '2026-10-21'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://help.peliqan.io/pipeline-webhooks.md
sources:
- https://help.peliqan.io/pipeline-webhooks.md
- https://help.peliqan.io/low-code-python-data-apps/by-protocol-rest-webhooks-mqtt/mcp-model-context-protocol/build-a-remote-mcp-server-on-peliqan.md
- https://help.peliqan.io/low-code-python-data-apps/by-protocol-rest-webhooks-mqtt.md
- https://help.peliqan.io/incoming-webhooks.md
description: Outbound webhook events for ELT pipelines.
events:
- event: connection_added
  description: A new data connection has been created on the account.
- event: connection_removed
  description: A data connection has been deleted from the account.
- event: pipeline_run_started
  description: The Peliqan worker picks up the run and execution begins. Fires once per run, before any data is fetched.
- event: pipeline_run_completed
  description: All enabled streams synced to the destination without any row-level errors.
- event: pipeline_run_completed_with_errors
  description: Sync finished but at least one stream had row-level write failures. Data was partially synced - other streams may be complete.
- event: pipeline_run_internal_error
  description: Peliqan's own task runner crashed - unhandled exception inside the pipeline orchestrator, not inside the connector.
- event: pipeline_run_error
  description: The Singer tap/connector process exited with a non-zero code or raised an exception during execution.
- event: pipeline_run_remote_error
  description: The remote data source returned an error - e.g. database connection refused, credentials rejected, or the source API returned a
    5xx.
- event: pipeline_run_killed
  description: A user manually cancelled the run via the UI or API.
- event: pipeline_run_killed_for_system_upgrade
  description: Peliqan stopped the run automatically to perform a rolling system upgrade. Safe to re-trigger; no data corruption occurs.
- event: pipeline_run_timeout
  description: The run exceeded the maximum execution duration configured for the connector. The process was force-terminated.
- event: pipeline_run_rate_limited
  description: The source API returned an HTTP 429 or a connector-specific rate limit that cannot be retried within the allowed window.
- event: pipeline_run_no_streams
  description: The connector found no streams/tables to sync - either none are enabled on the connection, or discovery returned an empty catalog.
- event: pipeline_run_failed
  description: Catch‑all for any terminal status not covered above. Should not occur in normal operation.
delivery:
  signature: HMAC‑SHA256 of "{unix_timestamp}.{canonical_json}" using the configured signing secret
  retries: up to 4 attempts with exponential backoff (0 s, 1 s, 2 s, 4 s)
  content_type: application/json
note: Signing secret is optional but recommended; when configured the request includes X‑Peliqan‑Signature header.
docs: https://help.peliqan.io/pipeline-webhooks.md

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/peliqan-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.