POST /v1/content/posts/generate

Autentifikacija

Pošaljite API ključ kao bearer token. Ova krajnja tačka ne navodi specifičnu dozvolu u specifikaciji, zato dodelite svom ključu minimum potrebnih ovlašćenja i proverite odgovor umesto da pretpostavljate.

Ovaj krajnji tačka ne prihvata ID organizacije. Vaš ključ već identifikuje organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamenite bilo šta u uglastim zagradama sopstvenim vrednostima, a ključni placeholder sa ključem sa vaše kontrolne table.

curl -X POST https://api.zinndigital.com/v1/content/posts/generate \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "brief": <string> }'

Prijavljeni ste? API konzola na vašoj kontrolnoj tabli automatski popunjava ID vaše stvarne organizacije i vaš sopstveni ključ, i izvršava zahtev nad API-jem uživo tako da možete videti stvarni odgovor. Otvorite ovu krajnju tačku u API konzoli

Detalji

Turns a brief into DRAFT posts in the organisation's own content library, with the customer's anchors placed inside them. ⛔ It never schedules and never publishes — the drafts sit in the library until somebody reads them and creates a placement, which is the same line the hand-written path already draws. Gated on `links.edit`, the same key as writing a post by hand, because that is what this is. Every call is metered on the caller's own organisation — BYO key, then credits, then the included allowance — and is refused with a sentence naming what would clear it if none of the three can pay. ⛔ Anchors are placed VERBATIM and verified after generation. Any the model altered or dropped are named in the draft's `notes`, which the customer reads before scheduling — the platform never silently re-prompts (it would spend their money again) and never silently accepts (it would place a campaign they did not ask for).

Telo zahteva

Odgovor

Greške koje ovaj krajnji tačka može da vrati

401 · 403 · 422