Pick the token context
Use user tokens for user-approved actions and app tokens for server-to-server reads where the endpoint accepts a target id.
APIs
Introduction
Blaze APIs are the request-response layer for the parts of the platform you want to read, shape, or automate. Start with https://api.blaze.stream, choose whether the request belongs to a user access token or an app access token, then follow the endpoint card for scopes, parameters, and response shape. Every https://api.blaze.stream/v1 request must include the Client ID header: client-id.
Base URL
https://api.blaze.streamAll REST paths in this section are mounted here; every /v1 request requires client-id.The API loop
Treat every request as a small contract: token context, permission, resource, and response. Once those four pieces are clear, the reference pages become much faster to scan.
Check the scope
Endpoint cards list the scopes required for each accepted authorization type.
Choose the resource
Channels cover stream and audience state; Users cover identity, stats, subscriptions, and profile updates; Chat covers message create and delete actions; Categories cover browseable taxonomy; Moderation covers ban, remove-ban, and mute actions.
Follow the card
Each card keeps method, URL, auth options, parameters, examples, and response shape in one place.
Where to go first
Open the resource family that matches the object your integration is touching. If your workflow needs push updates after the first read, continue into Events.
/v1/channels
Channels
Read stream state, channel stats, followers, roles, subscribers, activity feeds, and editable channel metadata.
/v1/users
Users
Read profiles, creator stats, subscription state, and user-owned public profile fields.
/v1/chats
Chat
Send chat messages and delete existing chat messages for the target channel.
/v1/categories
Categories
List browseable stream categories with hierarchy, image, slug, and display name metadata.
/v1/moderation
Moderation
Ban users, remove bans, and temporarily mute users in channels where the actor has moderation permission.
Socket.IO
Events after REST
Use REST for a snapshot, then subscribe to EventSub when the product needs live changes.
Request shape
Most API calls share the same skeleton: method, versioned path, Bearer token, Client ID header, JSON accept header, and a response your UI or backend can trust.
GET/v1/users/profile
Authorization: Bearer YOUR_ACCESS_TOKEN
client-id: YOUR_CLIENT_ID
Accept: application/json
200 OK -> application/json