How to use a design API

Humans design one post. Software needs fifty on-brand PNGs when a catalog updates. A design REST API is the editor’s engine with a door: you send a prompt, template, or plan, and you get a rendered asset back.

It is not a replacement for taste. You still set brand kits, sizes (Instagram 4:5, stories 9:16, 16:9, A4/Letter), and guardrails. The API repeats the work without opening a laptop.

Amadezing keys look like amz_ and go in the `Authorization: Bearer` header. Treat them like passwords: per environment, rotatable, never in a public frontend repo.

The playground is available on all plans so you can see requests and responses before you wire production. Free, Starter, and Pro still spend credits when generation runs.

Start with one size and one template you already like in the editor. Automating a bad layout only makes bad layouts faster.

Log the job id. Renders are not always instant; poll or webhook according to the docs in the playground rather than blocking a user click for thirty seconds.

1. Create a key in the account settings and store it server-side.
2. Open the playground and run a sample design-engine request.
3. Copy the call into your backend with the Bearer amz_ header.
4. Pass brand context (colors, fonts, logos) the same way the editor’s kit would.
5. Save the returned PNG (or place it on a canvas later) and optionally publish/schedule through your usual flow.

The playground is where you learn payload shape, errors, and credit cost. It is the same API your app will call. Skipping it is how teams ship a key in a Next.js client bundle.

Keep a human editor in the loop for the first campaign. Remix in the mobile-first canvas, then lock the template the API should clone.

Image generation (FLUX), extra renders, and large batches cost credits. Budget like you would budget ads. The API will not invent unlimited free compute.

You still have the manual tools — text, images, shapes, emoji, motion, background removal — for anything the model should not decide. Hybrid is the point: API for volume, editor for the hero post.

• Never expose amz_ keys in the browser.
• Version your templates; the API should name the revision it used.
• Fail visibly when credits run out rather than serving a blank PNG.

Amadezing’s design REST API shares the engine behind the social editor: templates, remix, brand kits, multi-size, carousels, PNG export. Positioned as a Canva/Figma alternative for social, plus a door for software.

Design the first piece by hand, then let the playground show you the request that would make the next fifty.

• Open the API playground
• Design the template in the editor
• What is an AI design tool?
• How to export designs as PNG
• Amadezing vs Canva