Benchmark Email
Benchmark Email is an email marketing platform with a REST API for managing contacts, lists, email campaigns, automations, reports, and transactional email delivery. The API supports contact synchronization, campaign management, reporting analytics, domain verification, and webhook notifications for real-time event handling.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Benchmark Email the way a machine reads it — 47 machine-readable artifacts across 29 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Benchmark Email scores 53.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Benchmark Email
Each block below is one kind of artifact we hold for Benchmark Email. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 29
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Benchmark Email ABTest Creation API
Create and manage A/B split tests
Benchmark Email Account Settings API
Manage account settings and configurations
Benchmark Email Add Contacts API
Add and import contacts to lists
Benchmark Email Agency Account API
Manage linked agency accounts
Benchmark Email Archive API
Manage email archive and archive pages
Benchmark Email Automation Creation API
Create and manage automation workflows
Benchmark Email Contact Configurations & Searches API
Configure and search contacts
Benchmark Email Contact Reports & Metrics API
Contact reporting and metrics
Benchmark Email Email Editor API
Email template and layout management
Benchmark Email Email Email Rss Creation API
Email Email Rss Creation
Benchmark Email Engagement API
Engagement analytics and list building
Benchmark Email General API
General operations
Benchmark Email Help API
Help desk and support tickets
Benchmark Email Image Gallery API
Manage image gallery
Benchmark Email Inbox Checker API
Test emails in inbox preview
Benchmark Email List Configurations & Searches API
Configure and search contact lists
Benchmark Email List Reporting or Metrics API
List reporting and metrics
Benchmark Email Partner API
Partner commission and referral management
Benchmark Email Poll Creation API
Create and manage polls
Benchmark Email Reports API
Campaign reporting and analytics
Benchmark Email Security API
Authentication and security operations
Benchmark Email Segments API
Manage contact segments
Benchmark Email Signup Form API
Manage signup forms
Benchmark Email Sub-Account API
Manage sub-accounts and their settings
Benchmark Email Survey Creation API
Create and manage surveys
Benchmark Email Third Party Signup Forms API
Third-party signup form integrations
Benchmark Email Video Gallery API
Manage video gallery
Benchmark Email Webhooks API
Manage webhooks for event notifications
Scroll within the panel for all 29 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Benchmark Email Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Benchmark Email Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Benchmark Email Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Benchmark Email API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CampaignReport
JSON SCHEMAContactList
JSON SCHEMAContact
JSON SCHEMAEmailCampaign
JSON SCHEMAWebhook
JSON SCHEMAExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Add Contact
EXAMPLECreate Contact List
EXAMPLECreate Webhook
EXAMPLEGet Campaign Report
EXAMPLESend Campaign
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Benchmark Email — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/benchmark-email · machine-readable index on apis.io