canonical: https://jentic.com/apis/phound.app/phound

# Phound App Phound API

Jentic publishes the only available OpenAPI specification for Phound API, keeping it validated and agent-ready. Phound provides a communication platform API for managing subscriptions, conference calls, file storage, and broadcast sessions. The API supports subscriber lifecycle management, multi-party conferencing, file uploads with batch processing, broadcast messaging to subscriber groups, and international calling with country and timezone reference data across 14 endpoints.

## For AI agents

Manage communication subscriptions, create and control conference calls, upload and organize files, and broadcast messages to subscriber groups via the Phound platform.

## Scope

Does not handle SMS messaging, email delivery, or video calls - use for voice conferencing, subscription management, and broadcast communications only.

## Capabilities

- Create and manage subscriber accounts with configurable communication preferences
- Initiate multi-party conference calls and manage participant connections
- Upload files with batch processing for bulk content distribution
- Broadcast voice or recorded messages to subscriber groups simultaneously
- Query available countries and time zones for international subscriber configuration
- Track conference session history and participant engagement metrics
- Manage storage allocations and file organization per subscription

## Use cases

### Conference Call Management

Create and manage multi-party conference calls for business communication. Phound handles participant dialing, connection management, and session recording. Conference sessions are linked to subscriptions, enabling organized call tracking and participant management across recurring meeting groups.

Example prompt: Create a new conference under subscription SUB123, add three participants by phone number, and retrieve the conference session details

### Broadcast Messaging

Send voice broadcasts or recorded messages to groups of subscribers simultaneously. Phound manages the subscriber roster, schedules delivery across time zones, and tracks which recipients were reached. Useful for emergency notifications, announcements, and recurring informational broadcasts to opted-in audiences.

Example prompt: Create a broadcast session targeting all active subscribers and upload an audio file for delivery

### Subscription Lifecycle Management

Manage the full lifecycle of communication subscribers from creation through active use to cancellation. Each subscription includes storage allocation, conference access, and broadcast eligibility. The API supports listing, creating, updating, and retrieving detailed subscription information including associated conferences and files.

Example prompt: List all subscriptions, create a new subscription with timezone America/New_York, and verify it appears in the subscription list

### AI Agent Communication Orchestration via Jentic

AI agents can manage communication workflows through Jentic by creating subscriptions, scheduling broadcasts, and initiating conferences without handling OAuth tokens directly. The agent searches for communication operations, loads endpoint schemas, and Jentic manages the OAuth2 authorization code flow for secure access to the Phound platform.

Example prompt: Search Jentic for 'start a conference call', load the Phound conference creation operation, and execute to create a new conference under an existing subscription

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/subscription` | Create a new subscriber account |
| GET | `/subscriptions` | List all subscriptions |
| GET | `/subscriptions/{subscriptionId}` | Retrieve subscription details |
| GET | `/subscriptions/{subscriptionId}/conferences` | List conferences for a subscription |
| POST | `/storage/upload` | Upload a file to subscriber storage |
| GET | `/storage/files` | List uploaded files |
| POST | `/broadcast_sessions` | Create a broadcast messaging session |
| GET | `/countries` | List supported countries for subscribers |

## Key resources

- **Subscriptions** — Create, list, and manage subscriber accounts and their settings
- **Conferences** — Create conference calls and track session history per subscription
- **Storage** — Upload, list, and manage files and batch content for broadcasts
- **Broadcast Sessions** — Create and manage voice or message broadcasts to subscriber groups
- **Reference Data** — Query supported countries and time zones for subscriber configuration

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/phound.app/phound/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Phound API by hand means running its OAuth2 authorization-code flow against app.phound.app to mint and refresh tokens, then formatting the subscription, storage, and broadcast requests yourself. Through Jentic you install once, import the Phound API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** Phound puts the subscription id in the URL path (`/subscriptions/{subscriptionId}`), so a rule can pin your agent to reading one subscription and its conferences; the create-subscription, upload, and broadcast operations carry their target in the request body, so there you limit the agent to the operations it needs. You choose the operations it may call, so creating a subscription or starting a broadcast is not included unless you add it.
- **Credential handling:** Your Phound OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list voice conferencing subscriptions', and Jentic returns the matching Phound operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio API** — Full communications platform with voice, SMS, conferencing, and video capabilities
- **Plivo API** — Voice and SMS API with conference call support and competitive pricing
- **Telnyx API** — Telephony infrastructure for SIP trunking and number provisioning

## FAQ

### Why is there no official OpenAPI spec for Phound API?

Phound does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Phound API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### 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.