Vectorizer.AI Developers
Build automated image vectorization into applications, scripts, and production pipelines. Start with the official SDKs for normal application code, use the CLI for batch jobs and shell workflows, or call the HTTP API directly when you want complete control.
All developer tools use the same Vectorizer.AI API: authenticated raster-to-vector conversion for PNG, JPG, WebP, GIF, and BMP inputs with SVG, PDF, EPS, DXF, and PNG output.
- SDKs for application code in common languages
- CLI for terminals, scripts, and batch jobs
- HTTP API for custom integrations
- OpenAPI for generated clients and API tools
Choose Your Integration Path
Pick the tool that matches how you want to automate image vectorization.
1. SDKs
Best for applications and services. Use official packages with typed request objects, authentication helpers, and binary result handling.
2. Command Line
Best for local automation, batch conversion, CI jobs, and shell scripts. Install one standalone tool and call it from the terminal.
3. Direct API
Best when you want complete control over HTTP requests, custom transports, or a language without an official SDK.
Start With SDKs
Install
Add the Vectorizer.AI package through your normal language package manager. SDK packages are available for TypeScript and JavaScript, Java, C# and .NET, Go, PHP, and Ruby. The Python SDK is prepared and pending PyPI approval.
Call
Use the SDK to send an image file, image URL, base64 image, or retained image token along with your output settings.
Download
Receive SVG, PDF, EPS, DXF, or PNG output, or retain image tokens so you can download additional formats later.
The SDKs are the recommended starting point for most integrations because they keep your application code focused on your workflow instead of request wiring.
Use the Command Line
For Scripts and Batch Jobs
The Vectorizer.AI CLI is a standalone command line tool for Windows, macOS, and Linux. It is useful for shell scripts, local folders of artwork, CI jobs, QA checks, and one-off terminal workflows.
Use it when you want automation without adding an SDK dependency to an application project.
For Portable Automation
The CLI wraps the same API and output options as the SDKs. It can vectorize images, write output files, and fit naturally into existing terminal-based tooling.
Call the API Directly
HTTP Endpoints
Use the HTTP API directly when you need custom request handling, a custom client, or a language that does not yet have an official SDK. Authenticate with HTTP Basic auth using your API Id and API Secret.
-
POST /api/v1/vectorize -
POST /api/v1/download -
POST /api/v1/delete -
GET /api/v1/account
OpenAPI and Tools
Download the OpenAPI 3.0 specification for generated clients, API exploration tools, schema inspection, and internal integration documentation.
Use the code-generation variant when your generator prefers flatter schemas, or the Swagger variant when you want a Swagger UI-friendly document.
Developer References
Output Options
Configure SVG, DXF, PDF, EPS, and PNG behavior, including grouping, curves, shape stacking, compatibility, sizing, and gap filling.
Pricing and Test Mode
Test integrations for free, understand preview and production credit behavior, and choose an API plan when you are ready for production use.
Errors and Limits
Handle HTTP statuses, API error JSON, response headers, timeouts, and rate limiting behavior in production integrations.
Developer FAQ
Where should I start?
Start with an SDK if your language is supported. Use the CLI for terminal automation, or use the HTTP API and OpenAPI specification when you need custom control.
Can I test before subscribing?
Yes. Test mode is free and does not require an API subscription, so you can build your integration and inspect request behavior before paying for production output.
Which inputs and outputs are supported?
The API accepts PNG, JPG, WebP, GIF, and BMP input. Production results can be downloaded as SVG, PDF, EPS, DXF, or PNG.
Do SDKs, CLI, and direct API calls produce different results?
No. They are different ways to call the same Vectorizer.AI API and use the same vectorization engine, authentication model, pricing behavior, and output options.
