EmailBison's API is workable but lies in specific, repeatable ways. This reference documents every landmine as it was actually found against the live platform: a bad key returning 200-shaped JSON instead of a 401, the pagination law that caps results at 15 unless you loop to meta.last_page, and the PATCH endpoint that resets every boolean you don't explicitly include. It's the mechanics layer every other EmailBison skill builds on.
Pipeline Playbooks · Open Source, MIT Licensed
The EmailBison API reference built from getting it wrong first: auth failures that look like success, pagination that silently truncates at 15, and one PATCH that can flip live campaign settings.
Every skill folder is self-contained. Run this from your project root to pull just this one into .claude/skills/emailbison-api/:
npx degit joelwylie7/cold-email-playbooks/.claude/skills/emailbison-api .claude/skills/emailbison-api
Want the whole system, not just one skill?

Assembles a complete EmailBison campaign end to end, copy, leads, senders, schedule, then deliberately stops at draft so nothing can go live without the QA gate.

A numbered gate that checks copy, settings, leads, senders, schedule and sequence structure before any campaign launches or resumes, PASS or FAIL, one line of evidence each.

Diagnoses a bounce spike by ESP and SMTP code before touching anything, because re-verifying the list fixes exactly one of five possible causes.