Docs/Guides

Guides

Task-oriented walkthroughs that string the API endpoints together into the jobs you actually want to do. Each one links to the full reference for field-level detail.

Generate your first piece of copy

From a brand-new client to a finished draft in four calls.

1
Create the client with POST /v1/clients, then add their brief with PATCH /v1/clients/{id} (what they sell, ideal customer, competitors). The brief is the context every bot reads.
2
List the bots available to you with GET /v1/bots to find the writing bot you want.
3
Run it with POST /v1/clients/{id}/bots/{botType}. The response includes the generated output.
4
Promote the output to an editable draft and finalize it with PATCH /v1/clients/{id}/drafts/{draftId} once you are happy with it.
Full quickstart in the API reference →

Close the attribution loop

Generation only gets smarter if Coppica learns what converted. This is the step most integrations skip, and the one that matters most.

1
Attach a tracking link to a deployed output with POST /v1/clients/{id}/tracking-links. It returns a UTM-tagged URL to use in the wild.
2
When a conversion happens, report it with POST /v1/outcomes, referencing the output that drove it.
3
The taxonomy reweights from that outcome, scaled by attribution confidence, so the next generation for this audience is informed by what actually worked.
Close the loop in the API reference →

Backfill existing copy

You do not have to start from zero. Import copy you already have so it can be tracked and learned from alongside net-new generations.

1
Send each existing piece to POST /v1/extract. Coppica parses it into a structured output it can track.
2
Attach tracking links and report outcomes exactly as you would for generated copy, so your historical winners feed the same loop.
Backfill in the API reference →

Wire up conversion tracking

Outcomes can arrive two ways. Pick the one that fits your stack.

1
For a website, drop in the pixel: one script tag that auto-reads UTM parameters. Good for simple setups.
2
For programmatic platforms, use webhook keys and post conversions server-side. Register webhook endpoints with POST /v1/webhooks.
Conversion tracking integration guide →

Install these as agent skills

Want your own agent to run these playbooks without you walking it through each step? Download drop-in skill files for Claude Code, Cursor, or any MCP agent.

Get the agent skills →
← Back to docs