RubiConnect

RubiConnect Capabilities API

The Capabilities API from RubiConnect — 1 operation(s) for capabilities.

Documentation GitHub OpenAPI

Operations 1

POST /capabilities/check Check RCS capability #

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/rubiconnect-capabilities-api"

All apis

curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: RubiConnect Messaging Platform & MCP Server Capabilities API
  description: Model Context Protocol (MCP) server and programmatic interface for RubiConnect. Enables external AI agents and developers to check RCS & WhatsApp capability, dispatch rich interactive messages, manage campaigns & templates, access inbox conversations, and query real-time delivery analytics.
  version: 1.0.0
servers:
- url: https://console.rubiconnect.com/api/v1
  description: Production Server
tags:
- name: Capabilities
paths:
  /capabilities/check:
    post:
      summary: Check RCS capability
      description: Verifies whether a recipient phone number is capable of receiving rich RCS messages for a specific agent context.
      operationId: checkCapability
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CapabilityCheckRequest'
      responses:
        '200':
          description: Capability check successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CapabilityCheckResponse'
        '400':
          description: Bad request (invalid parameter validation)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized (missing or invalid API key)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Agent not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
      - ApiKeyAuth: []
      - BearerAuth: []
      tags:
      - Capabilities
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
          example: 'Invalid or missing parameter: recipient is required.'
    CapabilityCheckRequest:
      type: object
      required:
      - recipient
      - agentId
      properties:
        recipient:
          type: string
          description: Destination phone number in E.164 format.
          example: '+15555551234'
        agentId:
          type: string
          description: The registered agent identifier.
          example: marketing-agent
    CapabilityCheckResponse:
      type: object
      properties:
        success:
          type: boolean
          example: true
        recipient:
          type: string
          description: Normalized E.164 phone number.
          example: '+15555551234'
        isRcs:
          type: boolean
          description: Whether the recipient is RCS-capable.
          example: true
        status:
          type: string
          description: Detailed RCS capability status.
          example: CAPABILITY_FULL
        features:
          type: array
          items:
            type: string
          description: Supported features/capabilities of the handset.
          example:
          - UP_2_0
          - GEO_PUSH
        optedOut:
          type: boolean
          description: Whether the recipient has opted out of communication.
          example: false
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
    BearerAuth:
      type: http
      scheme: bearer