What authentication does the Phound API use?

Phound uses OAuth 2.0 with the authorization code flow. The authorization URL is https://app.phound.app/oauth/authorize and the token URL is https://app.phound.app/oauth/token. Through Jentic, OAuth tokens are managed in your Jentic One instance with automatic refresh handling.

Can I create a conference call for multiple participants with the Phound API?

Yes. Conference calls are created under a subscription using GET /subscriptions/{subscriptionId}/conferences to manage conferences. Participants are added to the conference session and Phound handles the dialing and connection for each participant.

How do I upload files for broadcast distribution?

Use POST /storage/upload to upload audio or content files. Files are stored per account and can be referenced when creating broadcast sessions via POST /broadcast_sessions. Batch uploads are supported through the /storage/batches/{id} endpoint for bulk content preparation.

How do I set up a broadcast session through Jentic?

Search Jentic for 'create a voice broadcast' to find the POST /broadcast_sessions operation. Load the schema to see required fields including target subscriber group and content reference, then execute. Jentic handles OAuth2 token acquisition and refresh automatically.

Can I limit what my agent is allowed to do with the Phound API?

Yes. Jentic One is self-hosted, so your own rules decide which Phound operations and credentials the agent may use. Because Phound puts the subscription id in the URL path (GET /subscriptions/{subscriptionId} and its conferences), you can pin the agent to reading one subscription while withholding the create-subscription, POST /storage/upload, and POST /broadcast_sessions calls whose targets sit in the request body. The agent can only invoke the operations you add, so starting a broadcast or creating a subscription stays off unless you grant it.