API
API overview
Convert 3D files from your application
The Convert3D API converts 3D files from scripts, apps, and backend workflows.
Base URL:
https://api.convert3d.orgEndpoints
| Method | Endpoint | Use when |
|---|---|---|
GET | /health | You want to check that the API is reachable. |
POST | /convert | You want one request that returns the converted file bytes. |
POST | /convert/jobs | You want to start an async conversion job. |
GET | /convert/jobs/:id | You want to check job status. |
GET | /convert/jobs/:id/download | You want to download a completed job. |
GET | /upload-url | You want to upload a large file before creating a job. |
Which flow should I use?
Use POST /convert when:
- The file is small.
- You want the converted file in the same response.
- Your app can keep the request open until conversion finishes.
Use POST /convert/jobs when:
- The file is larger.
- You need status and progress.
- You want cleaner retries.
- The conversion runs inside a production workflow.
Use GET /upload-url plus POST /convert/jobs when:
- Your app should upload the file before starting conversion.
- The file may be too large for a normal multipart request.
- You want a more reliable large-file workflow.
Authentication
All cloud API requests require a bearer token.
Authorization: Bearer YOUR_API_TOKENGet an API token from convert3d.org/convert3dapi.
Common request fields
Most conversion requests use multipart/form-data.
Examples
Endpoint pages include curl, JavaScript, and Python examples where they are useful.
Start with Create a job for production integrations.