Self-service API keys
Business and Growth dealerships can create and revoke up to two active, dealership-scoped keys from the dashboard. Keys expire and are shown only once.
Available on Business and Growth
Car photo editing API for dealership inventory
Add CarPixAI photo processing to an existing dealership tool or automotive application. Upload one real inventory photo or submit 1–10 HTTPS sources, then poll each asynchronous job and retrieve protected results using the same image credits and production workflow as the dashboard.
Single or 1–10-photo batch · Per-image credits · Revocable dealership-scoped keys
Direct answer
What does the CarPixAI automotive photo API do?
CarPixAI provides a secure REST API for dealership inventory-photo processing. An eligible dealership uploads one JPG, PNG, or WebP, or submits 1–10 HTTPS sources in a bulk request. Each accepted image gets its own asynchronous job and protected result. New jobs use one normal image credit each; matching retries do not charge twice.
Production photo workflow
API jobs use the same production-default photo pipeline as dashboard jobs, including the selected dealership background and source-shaped framing behavior.
Asynchronous processing
Upload one JPG, PNG, or WebP—or submit 1–10 HTTPS sources—and poll dealership-scoped jobs instead of holding a long request open.
Protected result delivery
Completed images are returned only through an authenticated result route. Raw storage and provider URLs are not exposed to the client.
Safe retries
Every submission requires an idempotency key. Replaying the same request returns the same job without spending another image credit.
Vehicle-first review
The API standardizes presentation, but the exact vehicle and visible condition still need review before a result is approved for a listing.
Integration flow
Create, queue, verify, export
01
Create a key
Business and Growth accounts create a production key from Dashboard → API access.
02
Submit one or up to ten
Upload one image, or send a bounded JSON batch of HTTPS sources with a unique Idempotency-Key.
03
Poll each job
Read the returned status URLs until each accepted image completes or reaches a clear terminal failure.
04
Retrieve and verify
Download each protected result, compare it with its source vehicle, then approve it for downstream use.
One-photo request
curl --request POST https://carpixai.com/api/v1/photos/process \
--header "Authorization: Bearer $CARPIXAI_API_KEY" \
--header "Idempotency-Key: stock-123-front-v1" \
--header "Content-Type: image/jpeg" \
--data-binary @vehicle.jpg Bounded bulk request
curl --request POST https://carpixai.com/api/v1/photos/process-batch \
--header "Authorization: Bearer $CARPIXAI_API_KEY" \
--header "Idempotency-Key: stock-123-batch-v1" \
--header "Content-Type: application/json" \
--data '{"confirmCreditUse":true,"items":[
{"itemId":"front","sourceImageUrl":"https://cdn.example/stock-123-front.jpg"},
{"itemId":"rear","sourceImageUrl":"https://cdn.example/stock-123-rear.jpg"}
]}'Plan fit
API access uses the plan you already have
Business includes 500 image credits for $99/month. Growth includes 1,000 for $179/month. API and dashboard jobs draw from the same balance, so a dealership can test the integration without adopting a separate public API price sheet.
Best fit
- Dealerships connecting an internal inventory workflow
- Automotive software adding reviewed vehicle-photo processing
- Teams that can poll asynchronous jobs and retain source images
- Workflows that require dealership-scoped credentials and predictable credit use
Deliberate v1 boundary
A narrow API that is clear about what it does
CarPixAI exposes the smallest dependable production workflow first. That keeps image ownership, credit handling, retries, and result delivery understandable while integrations are being proven on real dealership inventory.
Not claimed in v1
- Bulk REST calls accept 1–10 HTTPS image sources; they do not read local folders or accept more than ten photos per request.
- No arbitrary prompt control, OAuth, webhook, SDK, CLI, or synchronous wait endpoint.
- No direct DMS import, inventory-feed writeback, marketplace publishing, or claimed service-level agreement.
- MCP remains a separate transport with separate credentials; REST keys cannot authorize MCP processing or reads.
API FAQ
Questions from dealerships and developers
What is a car photo editing API?
A car photo editing API lets software submit vehicle photos for automated presentation cleanup. CarPixAI accepts one uploaded photo or a batch of 1–10 HTTPS sources, queues each accepted image asynchronously, and returns each completed image through a protected result endpoint.
Who can use the CarPixAI photo processing API?
Photo processing API access is included with active Business and Growth dealership plans. Eligible users create and revoke keys from the API access page in their CarPixAI dashboard. Pro and Free accounts can see the feature but must upgrade before creating a key.
How is API processing billed?
Each newly accepted API job uses one normal CarPixAI image credit. An identical replay with the same source bytes and idempotency identity returns the existing job without a second debit. A changed source with the same identity is rejected as a conflict.
Does the API support bulk vehicle-photo requests?
Yes. POST /api/v1/photos/process-batch accepts 1–10 HTTPS vehicle-photo sources, preserves input order in its receipt, and returns an accepted or failed outcome for each item. Accepted images still complete asynchronously and are polled individually. Webhook delivery and direct inventory-system publishing are not currently claimed.
Does CarPixAI preserve the real vehicle?
CarPixAI is built to improve background and presentation while preserving the exact vehicle, including proportions, paint, trim, wheels, lights, glass, plates, accessories, and visible condition. Every completed result should still be compared with its source before publishing.
Is the REST API the same as the CarPixAI MCP integration?
No. REST keys can submit one uploaded photo or a bounded HTTPS batch, read status, and retrieve results. MCP uses separate keys and tools for assistant-led dealership workflows, including its own 1–10-photo batch tool. Access to one transport never grants access to the other.
Connect your first inventory photo
Open API access from an eligible dealership account, create a server-side key, and validate the workflow with a real source photo before automating more inventory.