How the API works

Every LocalAds flow follows the same five steps. Do the first three once per product, then start as many creative jobs as you want.

Create a brand

One brand per website. Brands

Create a product

From a product page URL or images. LocalAds reads it, and the product becomes ready. Products

Pick an audience

Audiences are generated and saved automatically. Campaigns and UGC videos are made for the one you pick. Audiences

Start a creative job

An ad campaign, listing images, a photoshoot, ChatGPT ads, or a UGC video. It answers 202 Accepted with the job’s id.

Poll until completed

Read the finished creatives from the response. Polling

Step	Calls
1. Brand	`GET /brands`, `POST /brands`
2. Product	`POST /products`, `GET /products/{product_id}`
3. Audience	`GET /products/{product_id}/audiences`
4. Creative job	`POST /campaigns`, `POST /photoshoots`, `POST /amazon-listing-images`, `POST /chatgpt-ad-groups`, `POST /videos`
5. Results	the job’s `Location` URL, and `GET /creatives`

The rules every request shares

Base URL. https://makelocalads.com/api/v1. Every request is HTTPS.
Authentication. An organization API key in the Authorization bearer header. See Authentication.
JSON. Requests and responses are JSON. Errors use application/problem+json with a code and a request_id. See Errors and retries.
Asynchronous work. A generation request answers 202 Accepted with the job’s id and a Location header, then runs in the background. See Jobs and lifecycle.
Idempotent starts. Generation requests accept an Idempotency-Key header, so a retry after a network failure never starts and charges for a second job. See Idempotent requests.
Spending caps. Every request that spends credits accepts max_credits, and is refused with 422 instead of going over. See Credits and spending.