Both Ads endpoints start from a finished ad: one flat PNG or JPEG with everything baked in. They answer the two questions a shipped ad raises after the design file is gone: how do I edit it, and how do I get it at another size.
| Endpoint | What it does | Reference |
|---|---|---|
POST /v2/ads/delayer | Takes the ad apart into editable layers: a background plate, image cutouts, live text with typography, and vector shapes, returned as one JSON layer document. | Ads API reference |
POST /v2/ads/resize | Produces the ad at up to ten other sizes with the layout redone for each shape: the Ad Delayer takes the ad apart, and Bria's layout engine composes the layers for each new shape. | Ads API reference |
Use the delayer when the ad itself has to change: a new headline, a translated line, a different price. Use resize when the ad is approved as it is and the campaign needs it in other placements. The two chain naturally: delayer first to edit, then resize the edited ad.
Both endpoints are asynchronous and share the platform's job model:
POSTthe ad and get back arequest_idand astatus_url.- Poll the status endpoint, or register a webhook and skip polling.
- On
COMPLETED, the status body carries the result: a pointer to the hosted layer document for the delayer, one hosted image per target size for resize.
A delayer run takes about two minutes. A resize lays every size out from the ad's layers and takes several minutes; the job finishes when its slowest size does.
Sources over 2048 px per side need an Enterprise plan. The delayer rejects a larger ad before any work is done; resize downscales it to fit first and says so in the response. Results stay hosted for the platform's standard asset retention period.
The API reference has both request schemas, the completion payloads and the error catalogs.