API documentation
VersionFixer exposes authenticated REST endpoints for account jobs, conversion requests, worker status, and API key rotation.
Use a VersionFixer API key in the Authorization: Bearer header or X-VersionFixer-Key header.
POST /wp-json/versionfixer/v1/jobs with multipart form fields: file, target, options, and optional service.
GET /wp-json/versionfixer/v1/jobs returns recent jobs for the authenticated account.
GET /wp-json/versionfixer/v1/formats returns supported formats, versions, operations, and service targets.
GET /wp-json/versionfixer/v1/engines returns available conversion engines and worker readiness.
POST /wp-json/versionfixer/v1/api-key rotates the current account API key.
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.
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.
curl -H "Authorization: Bearer vf_live_xxx" \
-F "file=@design.ai" \
-F "target=Illustrator CS6" \
https://example.com/wp-json/versionfixer/v1/jobs