StreamLive ProAPI keys for developers: create, use and revoke
StreamLive Pro API keys for developers: create a key on the Studio plan, choose its permissions and expiry, call the REST API at /api/v1, and revoke it safely.
An API key lets your own code work with your StreamLive Pro account: list and schedule lives, read the live chat, cut Shorts from a recording, publish them and read analytics. Keys are included in the Studio plan. You create one in Settings, under Security, in Connected apps and API; the key is shown once, and you send it as a Bearer token to https://streamlivepro.io/api/v1. If you only want ChatGPT or Claude to work with the account, you do not need a key: that connection is in every plan, see Use StreamLive Pro from ChatGPT and Claude.
Before you start
- The Studio plan. On other plans the API keys card says that keys are included in the Studio plan, and a key cannot be created; see /pricing?lang=en.
- A safe place for the key. A key is shown only once and we store only a hash of it. Put it in a secrets manager or an environment variable, never in code you share or in a web page.
- Know what you need. Each key carries its own permissions. Give a key only what its program uses.
- The API description. The full machine-readable description is at
https://streamlivepro.io/api/v1/openapi.json. The API is marked as a beta there, so read it before you build.
Steps
- Open the API settings. Choose Settings, then Security, then Connected apps and API.
- Press New key. A short form opens under API keys.
- Name it. For example the name of the program or server that will use it, so you know later which key to revoke.
- Choose permissions. Tick only what the program needs. See the table below. Seeing your account is always included. Seeing the stream key is unticked by default and marked Sensitive.
- Choose an expiry. 90 days (the default), 30 days, 1 year or Never. A key that expires on its own limits the damage of a key that leaked.
- Create and copy. Press Create. The key, starting with slp_, is shown once. Copy it, store it, and press Done.
- Call the API. Send the header Authorization: Bearer followed by the key, to
https://streamlivepro.io/api/v1. A first test: GET /me returns the account name, plan and this month's usage. - Revoke when done. In the same list press Revoke next to a key. Calls with it stop working at once.
Permissions
| Permission | What a key with it can do |
|---|---|
| read:account | See the account name, plan and this month's usage (always on) |
| read:streams | See lives, connected channels and connection health |
| write:streams | Schedule, edit, cancel and end lives |
| read:clips | See the Shorts cut from your recordings |
| write:clips | Cut new Shorts from one of your recordings |
| publish | Publish and schedule posts to your connected channels |
| read:analytics | See performance summaries |
| read:comments | Read the chat of your lives |
| read:stream_keys | See your stream key. Anyone holding it can broadcast as you |
Endpoints
| Method and path | What it does |
|---|---|
| GET /me | Account, plan and usage |
| GET /connections | Connected channels and their health |
| GET /readiness | What is still missing before going live, in order |
| GET /lives, GET /lives/{id} | List lives, one live |
| POST /lives | Prepare a live, or schedule it when you send a start time |
| PATCH /lives/{id} | Change a live |
| DELETE /lives/{id} | Cancel a scheduled live |
| POST /lives/{id}/end | End a live |
| GET /lives/{id}/chat | The live chat |
| GET /lives/{id}/ingest | Ingest details; the key itself only with read:stream_keys and reveal=true |
| GET /clips, POST /clips | List Shorts, cut Shorts from a recording |
| GET /posts, POST /posts, GET, PATCH, DELETE /posts/{id} | List posts, publish a Short, read a post, change or cancel a scheduled post |
| GET /analytics/summary | Results for a period, with the previous period for comparison |
| GET /podcasts/feeds | Podcast feed status |
| GET /help/search | Search the help center |
Uploads and phone camera pairing are listed as planned and answer 501 today.
Rules that protect you
- An API call is a decision. In ChatGPT or Claude the assistant shows a preview and asks before publishing, ending or cancelling. Through the API, a POST or DELETE you send is the decision, with no preview. Test with a scheduled live you can cancel.
- Retries without duplicates. Send an Idempotency-Key header (8 to 100 characters) on POST, PATCH and DELETE. The same key within 24 hours returns the first answer instead of doing the action again; the same key with a different body is refused with 422.
- Rate limits. Every answer carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, and Retry-After when you are over the limit.
- Plan limits apply. Every call runs with the limits of the account, exactly like the website.
- TikTok and Pinterest posts are made in the app by a person, not through the API.
- Limits on keys. Up to 20 active keys per account, and creating keys is rate limited too.
- Keys are not team seats. People who work in the dashboard get their own access: Invite team members to your account. Plan details: Plans, billing and limits.
Errors
Errors come back as error with type, code, message, request_id and doc_url. The ones you will meet first:
| Status and code | Meaning |
|---|---|
| 401 missing_credentials | No Authorization header |
| 401 invalid_api_key | The key is wrong or revoked |
| 401 expired_api_key | The key expired. Create a new one in Settings |
| 403 plan_limit | API keys are not included in the account's plan |
| 404 unknown_endpoint | No such path; check openapi.json |
Keep the request_id when you write to [email protected]. Never send the key itself. For the tools an assistant can use, see StreamLive Pro MCP tools: full list for ChatGPT and Claude.
Frequently asked questions
Which plan includes API keys?
The Studio plan. Connecting ChatGPT or Claude through MCP is included in every plan and does not need a key.
I lost my API key. Can I see it again?
No. A key is shown only once and we keep only a hash. Revoke the lost key and create a new one.
Does the API ask for confirmation before ending a live or publishing?
No. Through the API the request you send is the decision. Use Idempotency-Key for safe retries and test on a live you can cancel.
Can I limit what a key can do?
Yes. When you create a key you tick only the permissions it needs, and you can set it to expire after 30 days, 90 days or a year.
Can I go live through the API?
You can prepare and schedule lives, change, end and cancel them. The picture itself comes from the browser studio, your phone or an encoder such as OBS.
Keep reading
Every StreamLive Pro REST API endpoint under /api/v1 with its parameters, request fields and answer fields: lives, chat, stream keys, Shorts, posts, analytics.
What ChatGPT and Claude cannot do in StreamLive ProThe limits of ChatGPT and Claude in StreamLive Pro, with the reason for each and what to do instead: connecting networks, TikTok posts, uploads, approvals and more.
What ChatGPT and Claude can access: permissions explainedEvery permission ChatGPT or Claude can get on your StreamLive Pro account, what each one allows, which tools need it, which you can leave off, and how to change them.
What is MCP (Model Context Protocol)? A plain explanationWhat MCP, the Model Context Protocol, means in plain words: servers, tools, OAuth and scopes, and how ChatGPT and Claude use it to work with StreamLive Pro.
Want to try it? 7-day trial, no credit card.
Start free