Skip to main content
Polymorfa has three public API families. The Messaging API uses separate native and Meta-compatible OpenAPI documents so clients do not mix request shapes. The production base URL is:

​
Authentication

Service calls send a credential in the bearer header:
The three service credential kinds retain their compatibility prefixes:
  • titan_… — organization/server key.
  • titan_pt_… — project credential, restricted to its owning project.
  • titan_ct_… — short-lived client token, restricted by session and client rules.
Dashboard routes use a short-lived bearer and recheck live session, organization, membership, ban, and role state. See Authentication.

​
Messaging API versioning

The Messaging API defaults to 2026-03-20 and echoes the resolved version. Older versions follow the Deprecation, Sunset, and Link behavior described in Versioning. Meta-compatible paths use their own vNN.0 version.

​
Success and error shapes

Most typed Messaging API responses use one of these envelopes:
Messaging API errors contain a safe human-readable error string and may include a docs URL:
Meta-compatible errors use Meta’s error envelope and fbtrace_id. See Errors. Every response carries X-Request-Id. Send your own value to correlate a call, or log the generated one when contacting support.

​
API references

Use the generated endpoint page for the exact parameters, request bodies, responses, security requirements, and component types. The live OpenAPI document for the Messaging API is also available at https://api.polymorfa.com/docs/openapi.json.

Authentication

Credential kinds, scopes, and audiences.

Meta-compatible requests

Use Messaging API paths and shapes compatible with Meta Cloud API.

Platform API

Public /v1 paths, credentials, and schemas.

Enterprise API

Instance administration and messaging operations.