{
  "id": "p_1aucy1d2zmulWTja",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_1aucy1d2zmulWTja",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Say you run the realtime layer for a product, and you have been asked to rebuild your app's messaging setup in a fresh environment. Messages, presence events and channel lifecycle events all need to land in the same places they do today. Right now that setup lives in a dashboard that someone clicked through months ago. You want it in a script.\n\nThe Ably Rules API is where that script would start. It is one of 12 APIs on Ably's provider page at apis.io, and it manages integration rules, which tell Ably where to forward the messages, presence events and channel lifecycle events moving through a realtime app. The contract is small: 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.\n\nWhat catches your attention is how much sits behind those five operations. The ruleType values in the specification show what the API actually connects to. You find webhooks: http, http/zapier and http/ifttt. You find serverless functions: http/azure-function, http/cloudflare-worker, http/google-cloud-function and aws/lambda. You find streams and queues: aws/kinesis, aws/sqs, amqp, amqp/external, kafka and pulsar. And you find one inbound type, ingress-postgres-outbox. That makes 14 destinations.\n\nThirteen of them send messages out of Ably. The last works the other way: Ably reads an outbox table in your Postgres database and publishes those rows onto channels. So a rule is 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. For you, that means the whole fan-out topology of an app can sit in version control and be recreated in a new environment with one script, without anyone opening the dashboard.\n\nThe spec file runs to 166 KB for five operations, and nearly all of that is 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. If you are writing a rule yourself, or an agent is writing one for you, that detail is useful, because the schema says what each target needs before the first request fails.\n\nThen the post turns on itself, and it is worth your attention because you were about to rely on it. The APIs.io catalog record for this API does not match the contract it describes. Its 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. If your script took the base URL from the catalog record, it would call the wrong service.\n\nThere are smaller mismatches too. The description says \"2 operation(s) for rules\", while the same record's operation_count is 5, and the spec has five. The humanURL links to the REST API docs, though the record's own properties already include the correct Control API documentation page. The post says the same split probably affects the Apps, Keys, Namespaces and Queues records, since all four belong to the Control API. And the provider page lists 12 APIs while the provider record's published api_count is 2. The catalog files all of this against itself, as its own to fix. For context, Ably's Kin Score is 48.5, in the developing band, and its agent band is agent-aware.\n\nWhat you take away is practical. Treat the Rules API as infrastructure-as-code for Ably's integrations: 14 destination types and one inbound path, all behind five predictable operations. Pull the rule schemas from the OpenAPI file, and take the base URL from the specification rather than from the catalog record, at least until the record is fixed. Check the host before your first call, not after.\n\nRead the original: https://apis.io/2026/11/16/ablys-rules-api-routes-messages-to-fourteen-destinations-and-its-catalog-record-points-at-the-wrong-host/",
  "title": "You need to script Ably's integrations, and the catalog record points you at the wrong host",
  "topics": [
    "ably",
    "integrations",
    "infrastructure-as-code",
    "catalog-accuracy"
  ],
  "published_at": "2026-11-16T13:37:19.576Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
