Listing status
A listing’s status carries down to its photos, while each image also has its own. Needs review remains visible, ready and published read as completed states, and the approval permission determines who can move status.
Workflow guide
VehiclePhoto for internet managers
Online listings stall when imagery, copy, approval, and delivery live in separate queues. VehiclePhoto keeps a vehicle’s photos and VIN-backed text together, shows whether work is new, editing, waiting for review, ready, or published, and prepares destination-sized files after approval. The workflow reduces handoff ambiguity without pretending to push directly into a DMS.
Real product surfacesToday's pressure
- Every listing needs complete, consistent imagery and accurate text.
- A missing angle or failed photo must be visible before publication.
- Approvals should prevent unfinished output from entering delivery.
- Destination sizes and formats need repeatable export profiles.
- Programmatic intake or retrieval needs scoped authentication and status events.
What changes
Automatic listing copy
The copy workspace builds text from decoded VIN specifications and flags uncertainty for review. It keeps generated wording tied to the same vehicle and avoids treating an unsupported feature as fact simply because it sounds plausible.
Export & deliver
Select a channel profile, preview output, and export only after the publish gate is satisfied. Bulk ZIP creates multiple requested profiles and embeds a manifest with included and dropped items for a transparent handoff.
API keys
Issue scoped keys for REST API v1 so a partner can ingest a URL, start a supported process, retrieve an asset or job, and register webhooks. Keys expose named permissions rather than a broad account credential.
First hour
- 01
Choose a listing
Use a vehicle whose current page contains a normal mix of exterior, interior, and detail photos. Upload that listing and confirm the images group correctly before applying any processing or copy workflow.
- 02
Build the package
Create consistent photo output, review privacy treatment, and open Automatic listing copy. Compare decoded specifications with source information, edit uncertain wording, and keep unsupported equipment out of the final description.
- 03
Exercise approval
Leave one photo in needs review and move the complete work to ready only after correcting it. Confirm a user without approval permission can edit but cannot release the listing or individual image.
- 04
Test delivery
Export the profiles used by the real destination, inspect the ZIP manifest, and retrieve a result through a scoped API key if automation is planned. Record the remaining manual upload because direct DMS push is not live.
Connected responsibilities
The same listing crosses capture, review, brand, delivery, and account controls. Continue with the adjacent workflows that share those handoffs.
Pricing
Use the five-credit watermarked trial on a real listing, then choose a $39 one-off Listing Pass or a recurring plan from $49 per month. Standard listing-ready photos use one credit each; plan for full listing size and premium media before selecting capacity.
FAQ
Questions answered
Can copy use the VIN?
Yes. Automatic listing copy uses decoded VIN data and a review state designed to avoid unsupported assertions. It should still be checked against the specific vehicle because installed options, condition, and provided details cannot be inferred safely from a generic description.
What does the API expose?
REST API v1 supports authenticated ping, asset and job retrieval, HTTPS URL ingest, one supported processing step, and webhook endpoint registration. It does not provide a live DMS connector or a broad list operation, so integration design should match the documented surface.
Can incomplete work export?
Export is gated on approval. Workflow status provides a visible control at listing and image level, and the bulk manifest reports any dropped item. That makes missing output discoverable before the archive is handed to the destination workflow.