Server API
The server API under /v1 on port 32500, described by a published OpenAPI contract: libraries, search, playback, Live TV, DVR and metadata.
Developers
Build with Portico.
Portico's own apps use the same server API you can. Create a scoped API key, script your library, receive signed webhooks, or connect an assistant over MCP. All of it runs on your own server, with no Portico Account required.
API keys and tokens
Create scoped keys under Settings → Server → Integrations. Send one as a bearer header from your tool or script.
Signed webhooks
The server posts events straight to your endpoint, signed with HMAC-SHA256, with retries and a delivery log.
Assistants
A Model Context Protocol endpoint at /v1/mcp. Tools follow the key's scopes and the member's permissions.
Portico Server
- Media and libraries
- Playback decisions and streams
- Server accounts and permissions
- Server administration
Portico Services
- Portico Accounts and sign-in security
- Server membership and invitations
- Signed route discovery for direct connections
Building a Portico appThe full generated reference for client applications.IntegrationsSmall task guides, tool setup and the native Integrations reference.API architecture overviewChoose the Server API or the Portico Services API and see where each one's authentication applies.AuthenticationSign people in, keep sessions safe and use API keys.Client architectureFollow the shared client behaviour and use each platform's native playback.Security requirementsVerify direct routes, respect server permissions and keep credentials out of logs and URLs you share.Report an issueSend useful evidence without exposing media, credentials or private addresses.Report a security issueTell us privately about a vulnerability.