This article gives you the map before you start integrating: what the Video API covers, how requests are addressed to your tenant, and where to get a machine-readable copy of the specification.
What the Video API does
The MeetOne Video API lets you manage video rooms programmatically. With it you can create rooms for consultations, fetch and update their configuration, close them once a call is over, and — with the right token — review participant feedback submitted after calls.
Resource model
The API is organized around two resources:
| Resource | Description |
|---|---|
| Rooms | Video rooms for hosting calls between a host and one or more guests. Covers creation, retrieval, updates, closing, and WebRTC signaling. |
| Feedbacks | Ratings and comments submitted by participants after a call, plus aggregated summaries. Requires an Instance API Token. |
For the full endpoint reference see Rooms endpoints, Room lifecycle, and Room feedbacks. If you're building a custom video client instead of using the hosted join pages, see WebRTC signaling.
Base URL and tenants
Every request is made against your own tenant subdomain:
https://{tenant}.meetone.io
Replace {tenant} with your organization's subdomain, for example https://acme.meetone.io. There is no shared or global endpoint — all room and feedback data is scoped to the tenant the request is sent to.
Versioning
This documentation describes version 1 of the MeetOne Video API, as declared in the OpenAPI document itself.
Authentication
Every request must include a valid API token in the Authorization header:
Authorization: Bearer eyJhbGciOiJIUzI1****
There are two token types with different scopes — see Authentication & API tokens for how to obtain one and what each type can do.
The OpenAPI specification
The full API is described in a downloadable OpenAPI 3.0 document available at /meetone-video-api.yml.
You can:
- Paste its contents into editor.swagger.io for a browsable, interactive version of this reference.
- Feed the file into OpenAPI Generator or Swagger Codegen to generate a typed client library in the language of your choice.
Generating a client from the spec is the fastest way to get request/response types for your language without hand-writing HTTP calls.
Next steps
Ready to make your first request? Continue with the quickstart: create your first room.
Related
Questions? Contact us at support@meetone.io.