Using the /api/v1 surface
Build a custom storefront on top of the platform's read API.
What it is
The /api/v1 endpoints are a JSON read API for your published inventory and content. Use them to power a custom frontend (Next.js, Astro, Nuxt), a native app, a showroom kiosk, or anything else that wants your data.
This page is aimed at whoever is building that consumer — usually a developer. If you just want to manage cars and content, the built-in admin already does that.
Authentication
Send Authorization: Bearer <your_key> on every request. Server keys work from anywhere. Publishable keys also need an Origin header matching the list you set when you created the key.
curl -H "Authorization: Bearer dlrb_sk_..." \
https://api.dealerbloom.com/api/v1/cars?make=BMW,Audi&pageSize=24
Endpoints
GET /api/v1/cars— paginated inventory with filters.GET /api/v1/cars/{slug}— full detail including images, specs and location.GET /api/v1/makes— makes and their models.GET /api/v1/specs— spec groups and their values.GET /api/v1/locations— showrooms with map coordinates.GET /api/v1/contact— phones, WhatsApps, email, social handles, hours.GET /api/v1/testimonials— published testimonials.GET /api/v1/team— published team members.GET /api/v1/content/{pageKey}— content for a specific page.GET /api/v1/settings— site name, logo, currency.
Filtering cars
Multi-value filters (make, model, color, spec_<slug>) accept either comma-separated values or repeated query keys. Values within one filter match if ANY apply; values across different filters must ALL apply.
?make=BMW,Audi&model=A4,A6&color=black,white
?spec_body-type=SUV,Coupe&spec_fuel=Hybrid
# (BMW OR Audi) AND (A4 OR A6) AND (black OR white)
# AND (SUV OR Coupe) AND (Hybrid)
Cross-origin requests
Browser preflight (OPTIONS) always passes. The real GET checks the bearer token; publishable keys also have to match one of the origins you listed when you created the key.