← All Skills
Sending (EmailBison)

EmailBison API

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.

When to use this

  • Any script or skill talking to EmailBison directly
  • Creating or editing a campaign, sequence step, or schedule
  • Uploading leads or attaching senders
  • Reading stats, bounces, or sender counts
  • A result count comes back as exactly 15

What it covers

  • Landmine 1: auth failures return 200-shaped JSON with success:false, not 401
  • Landmine 2: the pagination law, 15 per page always, loop to meta.last_page
  • Landmine 3: PATCH resets every unspecified boolean, always resend the full set
  • Campaign activation: no launch endpoint exists, resume is the only way
  • Sequence step traps: variant_from_step vs variant_from_step_id, PUT orphans variants
  • Lead upsert and attach: batch sizes, custom_variables shape, bounced-lead 422s
  • Sender attach and the zero-senders-sends-nothing failure mode
  • Stats, schedule shape, and the unreliable schedule status label

Install just this skill

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?