Build Morface server integrations with public media URLs, async jobs, webhooks, and result delivery.

Morface Developer Docs

Morface Public API V1 is built for backend integrations. You submit publicly reachable media URLs, start an async job, listen for terminal webhooks, and fetch the final result when the job is ready.

Server-side API

Morface public endpoints are designed for server-to-server use with Authorization: Bearer <api_key>. Do not embed long-lived API keys in browser clients.

Start here

API Quickstart

The shortest path from API key to submit, webhook, and result fetch.

API Reference

Routes, headers, response envelope, idempotency, and delivery behavior.

Create API Keys

Generate a server-side key from your Morface account.

Pricing

Review available plans before you roll the integration out to production.

Core workflow

1. Authenticate

Use a Bearer API key and send write requests with request identifiers.

2. Prepare media URLs

Provide public http/https media URLs inside the submit body's input.source, input.target, input.reference, or input.audio fields.

3. Submit jobs

Start async image or video jobs with job_type, model, and an input object that contains params and media.

4. Observe completion

Receive terminal webhook events and keep status polling as a fallback path.

What the API covers

Async job submit, status, cancel, and result routes under /api/v1.
Terminal webhook delivery for job.completed, job.failed, and job.cancelled.
Idempotent submit retries with a 24-hour retention window.

Integration notes

API keys are shown in full only once when they are created.
The public API does not use session cookies. Always authenticate with a Bearer key.
Submit bodies must include job_type, model, and an input object with public http/https media URLs where applicable.
Jobs are asynchronous by design. A successful submit response means the job was accepted, not completed.
Webhooks do not contain result download URLs. Fetch results through GET /api/v1/jobs/{uuid}/result.

Introduction