Vibes Platform · OpenAPI Overlay 1.0.0

API Evangelist enhancements — Vibes RCS Business Messaging API

6 actions 6 updates documentation extends openapi/vibes-platform-rcs-business-messaging-openapi.json
Derived by API Evangelist Built from the contracts Vibes Platform publishes. Vibes Platform did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

operationIdx-api-evangelist-note

Targets 6

$.paths['/{connect_customer_key}/capabilities/{msisdn}'].get
$.paths['/{connect_customer_key}/agentMessages/{msisdn}'].post
$.paths['/{connect_customer_key}/agentEvents/{msisdn}'].post
$.paths['/{connect_customer_key}/agentMessages/{msisdn}/{messageId}'].delete
$.paths['/{connect_customer_key}/testers/{msisdn}'].post
$.info

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements — Vibes RCS Business Messaging API
  version: 1.0.0
  x-description: >-
    Non-destructive enhancements on top of the OpenAPI Vibes publishes for its RCS Business
    Messaging API at developer-aggregation.vibes.com. Two real defects in the published document are
    corrected here without touching anything else: five of the eight operations carry operationIds
    containing SPACES ("Get Mobile Device Capabilities", "Send Agent Message", "Send Agent Event",
    "Revoke Agent Message", "Invite Agent Tester"), which is invalid for code generation and for
    tool naming — the remaining three (getTester, deleteTester, listTesters) already use camelCase,
    so the document is internally inconsistent as well. info.version also reads 0.0.0. Generated
    2026-08-13 by the API Evangelist enrichment pipeline.
extends: openapi/vibes-platform-rcs-business-messaging-openapi.json
actions:
  - target: $.paths['/{connect_customer_key}/capabilities/{msisdn}'].get
    description: Replace the space-separated operationId with a camelCase identifier.
    update:
      operationId: getMobileDeviceCapabilities
  - target: $.paths['/{connect_customer_key}/agentMessages/{msisdn}'].post
    description: Replace the space-separated operationId with a camelCase identifier.
    update:
      operationId: sendAgentMessage
  - target: $.paths['/{connect_customer_key}/agentEvents/{msisdn}'].post
    description: Replace the space-separated operationId with a camelCase identifier.
    update:
      operationId: sendAgentEvent
  - target: $.paths['/{connect_customer_key}/agentMessages/{msisdn}/{messageId}'].delete
    description: Replace the space-separated operationId with a camelCase identifier.
    update:
      operationId: revokeAgentMessage
  - target: $.paths['/{connect_customer_key}/testers/{msisdn}'].post
    description: Replace the space-separated operationId with a camelCase identifier.
    update:
      operationId: inviteAgentTester
  - target: $.info
    description: >-
      Record that the published document carries info.version 0.0.0 while the surface is in
      production; annotated rather than renumbered, since only Vibes can assign a real version.
    update:
      x-api-evangelist-note: >-
        Published as version 0.0.0 by the provider. The API is live and documented as
        "RCS for Business"; the version string in the contract does not reflect that.

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay 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 overlay
curl "https://apis.io/api/v1/overlays/vibes-platform-rcs-business-messaging-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.