Developer API

API documentation

VersionFixer exposes authenticated REST endpoints for account jobs, conversion requests, worker status, and API key rotation.

The API is built for agencies, print shops and partner tools that need automated compatibility jobs.

Authentication

Use a VersionFixer API key in the Authorization: Bearer header or X-VersionFixer-Key header.

Create job

POST /wp-json/versionfixer/v1/jobs with multipart form fields: file, target, options, and optional service.

List jobs

GET /wp-json/versionfixer/v1/jobs returns recent jobs for the authenticated account.

Formats

GET /wp-json/versionfixer/v1/formats returns supported formats, versions, operations, and service targets.

Engines

GET /wp-json/versionfixer/v1/engines returns available conversion engines and worker readiness.

API keys

POST /wp-json/versionfixer/v1/api-key rotates the current account API key.

Workers

GET /wp-json/versionfixer/v1/workers summarizes which conversion families are ready, pending, or require a controlled worker.

Checkout

POST /wp-json/versionfixer/v1/checkout creates a checkout session for paid plans when the account is authenticated.

Authentication

Use Authorization: Bearer vf_live_xxx or X-VersionFixer-Key. API keys are hashed in user meta and can be rotated from the account/API endpoint.

Job creation

POST multipart/form-data to /wp-json/versionfixer/v1/jobs with file, format, target, options and optional service.

Job history

GET /wp-json/versionfixer/v1/jobs returns recent authenticated account jobs with status, credits, worker note and download URL when ready.

Operational model

Workers can be separated by format family so Adobe, CAD, 3D and PDF queues do not block each other.

Response model

Successful job responses include job ID, status, detected format, target version, credit cost and the next polling/download URL when available.

Error model

Errors are returned as readable JSON messages with HTTP status codes such as 400 for invalid files, 402 for credits, 429 for rate limits and 500 for worker failures.

Launch FAQ

Can a partner rotate API keys?

Yes. Authenticated users can rotate their key through the API key endpoint.

Does the API expose supported formats?

Yes. /wp-json/versionfixer/v1/formats returns formats, versions, operations, services and engine status.

Can API jobs be billed?

Yes. Jobs use the same plan and credit logic as the web converter.

Can developers check worker availability before upload?

Yes. Use /wp-json/versionfixer/v1/workers or /engines to decide whether to show instant conversion, queue or manual-review messaging.

curl -H "Authorization: Bearer vf_live_xxx" \
  -F "file=@design.ai" \
  -F "target=Illustrator CS6" \
  https://versionfixer.com/wp-json/versionfixer/v1/jobs

curl https://versionfixer.com/wp-json/versionfixer/v1/formats
curl https://versionfixer.com/wp-json/versionfixer/v1/engines
curl https://versionfixer.com/wp-json/versionfixer/v1/workers

{
  "success": false,
  "data": {
    "message": "File is required."
  }
}