Ably's Rules API routes messages to 14 destinations, and its catalog record points at the wrong host

Ably's Rules API routes messages to 14 destinations, and its catalog record points at the wrong host

The Ably Rules API is one of 12 APIs listed on Ably’s provider page. It manages integration rules, which tell Ably where to forward the messages, presence events and channel lifecycle events that move through a realtime app. The contract has five operations on one resource: list, create, get, update and delete, all under /apps/{app_id}/rules. Every operation requires a bearer token. The OpenAPI is titled “Control API v1 Rules API” and is at version 1.0.32.

What a rule can point at

The ruleType values in the specification show what the API actually connects to:

Family Rule types
Webhooks http, http/zapier, http/ifttt
Serverless functions http/azure-function, http/cloudflare-worker, http/google-cloud-function, aws/lambda
Streams and queues aws/kinesis, aws/sqs, amqp, amqp/external, kafka, pulsar
Inbound ingress-postgres-outbox

That makes 14 destinations behind five operations. Thirteen of them send messages out of Ably. The last one, ingress-postgres-outbox, works the other way: Ably reads an outbox table in your Postgres database and publishes those rows onto channels. A rule is therefore not just a webhook setting. It is how Ably connects its pub/sub system to the rest of your infrastructure, and it is fully scriptable. Because of that, you can keep an app’s whole fan-out topology in version control and recreate it in a new environment with one script, without anyone using the dashboard.

The spec file is 166 KB for five operations. Nearly all of that is the request and response schemas for each rule type. Each destination has its own shape: Kafka needs brokers and auth, SQS needs a region and queue ARN, and the Cloudflare Worker type needs a URL plus signing. That level of detail is useful to an integrator or an agent writing a rule, because the schema says what each target needs before the first request fails.

What is ours to fix

The catalog record does not match the contract it describes:

  • baseURL says https://rest.ably.io, the realtime REST host. The specification’s server is https://control.ably.net/v1, which is the Control API. A client that took our base URL would call the wrong service.
  • The description says “2 operation(s) for rules”. The same record’s operation_count is 5, and the spec has five.
  • humanURL links to the REST API docs. The record’s own properties already include the correct Control API documentation page, so we linked that one above.

The same split probably affects the Apps, Keys, Namespaces and Queues records too, since all four belong to the Control API. The provider page also lists 12 APIs while the provider record’s published api_count is 2. Ably’s Kin Score is 48.5 (developing), and its agent band is agent-aware.

Takeaway

Treat the Rules API as infrastructure-as-code for Ably’s integrations. It has 14 destination types and one inbound path, all behind five predictable operations. Take the base URL from the specification, not from our record, until we fix it. The rule schemas are in the OpenAPI, and the rest of the surface is on apis.io/providers/ably/.

← SERP APIs are built for agents and govern their own contracts least
AsyncAPI on apis.io is 3,664 documents, and one crypto exchange wrote 41 of them →