SightCall

SightCall REST API

SightCall's REST API is used by application back ends to request session tokens, manage users and sessions, provision providers and pull reporting. Authentication is by API key in the Authorization header. The full reference lives on the SightCall developer portal, which is gated - docs.sightcall.com now redirects to the admin console login and SightCall's own llms.txt says "contact SightCall for access".

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/sightcall/refs/heads/main/authentication/sightcall-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/sightcall/refs/heads/main/rate-limits/sightcall-rate-limits.yml

Other Resources

🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/sightcall/refs/heads/main/apis.yml

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/rest-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 email required.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: sightcall:rest-api
name: SightCall REST API
description: SightCall's REST API is used by application back ends to request session tokens, manage users
  and sessions, provision providers and pull reporting. Authentication is by API key in the Authorization
  header. The full reference lives on the SightCall developer portal, which is gated - docs.sightcall.com
  now redirects to the admin console login and SightCall's own llms.txt says "contact SightCall for access".
humanURL: https://sightcall.com/platform/
baseURL: https://api.rtccloud.net/v2.0/
x-base-url-note: 'The REST base is on rtccloud.net, not sightcall.com, and that is correct: rtccloud.net
  is SightCall''s own platform infrastructure domain (SightCall''s roots are the RTCCloud/Weemo WebRTC
  platform), it is named as the REST base by SightCall''s own documentation at docs.sightcall.com/gd/rest-api,
  and the live VISION application at vision.sightcall.com whitelists https://*.rtccloud.net in its Content-Security-Policy
  connect-src today. Both domains also carry the same DNSSEC/SPF/DMARC posture (see security/sightcall-domain-security.yml).
  The host did not answer an anonymous TLS connection during this pass, so nothing was harvested from
  it.'
tags:
- Video
- WebRTC
- Remote Support
properties:
- type: Authentication
  url: authentication/sightcall-authentication.yml
- type: RateLimits
  url: rate-limits/sightcall-rate-limits.yml