Squadcast Fm SquadCast API
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer19 EndpointsREST
For Agents
Programmatically retrieve organization, get account balance. Covers 19 operations with bearer authentication.
Use for: I need to organization, I want to account balance, Search for team members, Find all session
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API for managing SquadCast recording sessions, shows, organizations, and webhooks. The API exposes 19 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the SquadCast API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SquadCast API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquadcast.fm%2Fsquadcast-fm" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquadcast.fm%2Fsquadcast-fm" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SquadCast API.
Retrieve organization
Get account balance
List team members
Create session
Update session
Use Cases
Patterns agents use SquadCast API for, with concrete tasks.
★ Developer Tools Operations
Use the SquadCast API to perform developer tools operations programmatically. The API provides 19 endpoints covering core functionality including retrieve organization, get account balance, list team members.
Call GET /organizations to retrieve organization
Automated Organizations Management
Automate organizations operations by combining multiple SquadCast API endpoints. Agents can get account balance and then list team members in a single workflow.
Call GET /organizations/balance to get account balance, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SquadCast API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'retrieve organization', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
19 endpoints — api for managing squadcast recording sessions, shows, organizations, and webhooks.
METHOD
PATH
DESCRIPTION
GET
/organizations
Retrieve organization
GET
/organizations/balance
Get account balance
GET
/organizations/team
List team members
POST
/sessions
Create session
GET
/sessions
List sessions
GET
/sessions/{id}
Get session
PUT
/sessions/{id}
Update session
DELETE
/sessions/{id}
Delete session
GET
/organizations
Retrieve organization
GET
/organizations/balance
Get account balance
GET
/organizations/team
List team members
POST
/sessions
Create session
GET
/sessions
List sessions
GET
/sessions/{id}
Get session
PUT
/sessions/{id}
Update session
DELETE
/sessions/{id}
Delete session
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SquadCast by hand means learning its bearer auth against api.squadcast.fm/v2 and managing session lifecycle calls yourself. Through Jentic you install once, import the SquadCast API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
SquadCast puts the session id in the URL path (/sessions/{id}), so a rule can pin your agent to reading and creating sessions. You choose the operations it may call, so destructive ones like session deletion are not included unless you add them.
Credential isolation
Your SquadCast bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a recording session' or 'list my organizations', and Jentic returns the matching SquadCast operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SquadCast API through Jentic.
What authentication does the SquadCast API use?
The SquadCast API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I retrieve organization with the SquadCast API?
Yes. Use the GET /organizations endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SquadCast API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I retrieve organization through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve organization'. Jentic returns the matching SquadCast API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SquadCast API have?
The SquadCast API exposes 19 endpoints covering organizations, sessions, shows operations.
Can I limit what my agent is allowed to do with the SquadCast API?
Yes. Because you self-host Jentic One, your own rules decide which SquadCast operations and credentials the agent may use. You can pin it to reading and creating sessions with GET /sessions and POST /sessions while withholding destructive calls like DELETE /sessions/{id}, since each session id lives in the URL path. Operations such as GET /organizations or listing team members are only available to the agent if you choose to include them.
GET STARTED