One endpoint, one key, one HTTP call: create a meeting on behalf of one of your users and get back a host link and a guest link. No separate Elyon Meet account needed for the person you're creating it for.
Keys are issued by an Elyon Meet superadmin, one per integrating project or client. Contact support with the name of your project and what you're building — a superadmin mints the key from the admin panel, labels it with your project name, and sends you the raw key. It's shown once at creation time and can't be retrieved again after that, only revoked and reissued, so store it somewhere safe (a secrets manager or environment variable, not source control).
Send your key as a bearer token on every request:
Authorization: Bearer emk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
POST /api/v1/integrations/meetings
Authorization: Bearer <api_key>
Content-Type: application/json
{
"hostName": "Mrs. Mensah",
"hostEmail": "mensah@example.com",
"title": "Biology Class - Form 2A"
}
| Field | Required | Notes |
|---|---|---|
hostName | Yes | Name shown to attendees as the meeting host. |
hostEmail | No | Accepted for future use, not yet surfaced anywhere. |
title | No | Defaults to "<hostName>'s Meeting". |
Response:
{
"room": "room-da95e7741309a2ec",
"code": "800639761",
"codeFormatted": "800 639 761",
"hostJoinUrl": "https://elmeet.falits.com/room-...?jwt=...",
"guestJoinUrl": "https://elmeet.falits.com/room-..."
}
| Field | Give it to | Notes |
|---|---|---|
hostJoinUrl | The host | Signed, room-scoped, valid 4 hours. Skips the device-check screen. |
guestJoinUrl | Attendees | No account or token needed to use it. |
codeFormatted | Attendees | Alternative to the guest link — typed into /join by hand. |
| Status | Meaning |
|---|---|
| 400 | Missing or blank hostName. |
| 401 | Missing, invalid, or revoked API key. |
| 429 | Rate limit exceeded — back off and retry. |
| 500 | Transient server error — safe to retry. |
Meeting creation is the only thing exposed via API key today. Recordings, transcripts, and participant data all stay behind a signed-in portal session — they're not reachable this way. If your integration needs more than "create a meeting and hand out the links," talk to a superadmin before building around it; the API grows as real integrations need it, not ahead of that.