Convoy
Convoy is an open-source, cloud-native webhooks gateway used to securely ingest, persist, debug, deliver, and manage events. It positions itself as "the complete solution for secure, scalable, and reliable webhook delivery," covering both outbound (sending) and inbound (receiving) webhooks with retries, payload signing, fan-out, rate limiting, message broker ingestion, and customer-facing portals. Convoy is offered as a self-hosted open-source project (Elastic License v2.0, with the OpenAPI spec under MPL 2.0) and a fully managed cloud service in US and EU regions.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Convoy the way a machine reads it — 128 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Convoy scores 66.3/100 (exemplar), with a separate agent-readiness read of 37/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-03 · rubric v0.9
Put this on your own site. The badge is drawn live from Convoy's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/convoy/"
title="Convoy on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/convoy.svg"
alt="Convoy Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/convoy/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/convoy/"
title="Convoy on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/convoy/card.svg"
alt="Convoy Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Convoy
Each block below is one kind of artifact we hold for Convoy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Convoy Delivery Attempts API
Delivery Attempt related APIs
Convoy Endpoints API
Endpoint related APIs
Convoy Event Deliveries API
EventDelivery related APIs
Convoy Events API
Event related APIs
Convoy EventTypes API
Event Types related APIs
Convoy Filters API
Filters related APIs
Convoy Meta Events API
Meta Events related APIs
Convoy Onboard API
Onboard related APIs
Convoy Portal Links API
Portal Links related APIs
Convoy Sources API
Source related APIs
Convoy Subscriptions API
Subscription related APIs
Scroll within the panel for all 11 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Convoy API Reference
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Convoy API Reference
OPEN COLLECTIONArazzo Workflows 12
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Convoy Attach Filter to Subscription
Create a subscription, attach a body-matching filter, and confirm the filter list.
ARAZZOConvoy Batch Retry Failed Deliveries
Detect failed deliveries for an endpoint and batch retry them in one call.
ARAZZOConvoy Broadcast Event and Track
Broadcast an event to all matching subscriptions and trace the resulting event.
ARAZZOConvoy Create Event and Trace Delivery
Publish an event to an endpoint, find its delivery, and read the delivery attempts.
ARAZZOConvoy Define Event Type and Subscribe
Define a project event type, create an endpoint, and subscribe filtered to that type.
ARAZZOConvoy Fan Out Event to Owner
Confirm endpoints exist for an owner, fan out an event to them, and verify it landed.
ARAZZOConvoy Force Resend Successful Deliveries
Find a recent successful delivery for an endpoint and force resend it by ID.
ARAZZOConvoy Inspect Delivery Attempts
Retrieve an event delivery, list its attempts, and drill into a single attempt.
ARAZZOConvoy Provision Endpoint and Subscription
Stand up a webhook endpoint, subscribe it, send a first event, and confirm delivery.
ARAZZOConvoy Register Incoming Source
Create an HMAC-verified incoming source and subscribe it to an endpoint.
ARAZZOConvoy Replay Event
Pick a recent event, replay it as a fresh event, and trace the new deliveries.
ARAZZOConvoy Retry a Failed Delivery
Find a failed event delivery, retry it, and inspect the resulting delivery attempts.
ARAZZOScroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Convoy Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Convoy Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Convoy Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Convoy Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Convoy API Rules
SPECTRALConvoy API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Convoy DeliveryAttempt
JSON SCHEMAConvoy Endpoint
JSON SCHEMAConvoy EventDelivery
JSON SCHEMAConvoy Event
JSON SCHEMAConvoy EventType
JSON SCHEMAConvoy PortalLink
JSON SCHEMAConvoy Source
JSON SCHEMAConvoy Subscription
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Convoy Delivery Attempt Structure
JSON STRUCTUREConvoy Endpoint Structure
JSON STRUCTUREConvoy Event Delivery Structure
JSON STRUCTUREConvoy Event Structure
JSON STRUCTUREConvoy Event Type Structure
JSON STRUCTUREConvoy Portal Link Structure
JSON STRUCTUREConvoy Source Structure
JSON STRUCTUREConvoy Subscription Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 68
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Convoy Endpoint Example
EXAMPLEConvoy Event Example
EXAMPLEConvoy Event Type Example
EXAMPLEConvoy Op Getfilter Example
EXAMPLEConvoy Op Getfilters Example
EXAMPLEConvoy Op Getsource Example
EXAMPLEConvoy Op Testfilter Example
EXAMPLEConvoy Portal Link Example
EXAMPLEConvoy Source Example
EXAMPLEConvoy Subscription Example
EXAMPLEScroll within the panel for all 68 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Resources
Every other property we hold for Convoy — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 12
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 12 ·
Build 13
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 13 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/convoy · machine-readable index on apis.io
This is an independent, third-party profile of Convoy, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
[email protected]
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.