Media2URL Documentation

Media2URL helps you host supported files and use the resulting direct media URLs or share pages in your applications and workflows.

For common product asset workflows, see the developer workflows and SaaS team workflows.

Choose a starting point

• External REST API — automate uploads, asset management, folders, and remote imports.
• Overview and authentication — create credentials and complete the first upload safely.
• Uploads, imports, and jobs — handle upload sessions, remote imports, and asynchronous jobs.
• Assets, versions, and folders — manage returned assets and workspace organization.
• Errors, retries, and limits — handle problem responses, rate limits, quotas, and idempotency.

If the upload belongs to a Make scenario or a Zapier workflow, start with the relevant integration guide for its connection method and availability. For n8n, the community-node setup covers package installation and the API key used by your workflow.

Public API at a glance

The external REST API is available at:

https://api.media2url.com/v1

Requests use bearer API keys created in the developer dashboard. The API supports direct uploads through short-lived upload sessions, asset organization, version-aware replacement, and asynchronous remote imports.

The OpenAPI 3.1 specification is the machine-readable contract. The human guides explain the same public operations with complete examples and safer integration advice.

Working with the public API

The reference covers the public endpoints and their request and response formats so you can connect an application to Media2URL. Never place an API key, signed URL, or private asset identifier in public source code or documentation.

Need help?

For account access, billing, or abuse questions, use the public contact page. For security concerns, see the security page.