Jicofo REST API

Operations REST API exposed by Jicofo (Jitsi Conference Focus) for inspecting in-progress conferences, listing the bridge selection state, and triggering graceful shutdowns. Used by operators and orchestrators when running self-hosted Jitsi deployments at scale.

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/jicofo-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 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.

API entry from apis.yml

apis.yml Raw ↑
aid: jitsi:jicofo-rest-api
name: Jicofo REST API
tags:
- Jicofo
- Conference Focus
- REST
- Self-Hosted
tags_raw:
- Jicofo
- Conference Focus
- REST
- Self-Hosted
- Operations
humanURL: https://github.com/jitsi/jicofo
baseURL: http://localhost:8888
properties:
- url: https://github.com/jitsi/jicofo
  name: Jicofo
  type: Documentation
- url: https://github.com/jitsi/jicofo
  type: SourceCode
description: Operations REST API exposed by Jicofo (Jitsi Conference Focus) for inspecting in-progress
  conferences, listing the bridge selection state, and triggering graceful shutdowns. Used by operators
  and orchestrators when running self-hosted Jitsi deployments at scale.