Skip to documentation
Let’s build
PUBLIC TECHNICAL PREVIEW Production access and integration details are agreed during onboarding.
Amora Docs/Errors & usage

DEVELOPER DOCUMENTATION

Errors & usage

Handle failures and agree commercial usage before launch.

Handle failures according to the operation that failed. A playback error, an interrupted network request and an exhausted commercial allowance need different responses.

User-facing failures

SituationRecommended behavior
Preview playback failsKeep the page usable and offer explicit retry
Microphone permission deniedExplain how to allow access; do not create the live call first
Call still connectingPrevent duplicate starts and allow cancellation
Network interruptionShow connection state and apply the configured reconnect policy
Generation outcome unknownCheck the existing job before submitting again
Service unavailableKeep a clear fallback and provide a support path

Show concise Amora-branded messages. Keep raw service URLs, keys and internal errors out of the visible interface.

Status and retry behavior

Production endpoints return the status codes and error shape agreed in your integration contract. Treat authentication failures as configuration issues, validation failures as request issues, and temporary service failures as potentially retryable only when the operation's outcome is known.

Do not retry a paid call or generation blindly after a timeout. Retain its session or job identifier and reconcile status where supported.

Usage and commercial limits

The public API plans start at $100, $300 and $900 per month. Included usage, overage rates, supported concurrency, storage and service-specific allowances are confirmed during sales.

There is no published universal requests-per-second guarantee in this technical preview. Rate limits and production capacity are agreed for the enabled services.

Support details

When reporting an issue, include the time, application environment, request or session identifier, operation and observed result. Remove keys, signed-link query strings and private user content before sharing logs.

Contact [email protected].

Building something personal?

Talk to our team about your architecture, character and launch.

Discuss your integration ↗