AhaSend
AhaSend is a developer-focused transactional email platform providing fast, reliable email delivery via REST API and SMTP relay. It offers features including email tracking, webhooks, email routing, suppression management, domain management, SMTP credentials, and detailed delivery statistics.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles AhaSend the way a machine reads it — 233 machine-readable artifacts across 11 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 — AhaSend scores 64.9/100 (strong), 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile AhaSend
Each block below is one kind of artifact we hold for AhaSend. 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 11
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.
AhaSend Accounts API
Manage account settings and members
AhaSend API Keys API
Manage API keys for authentication and access control
AhaSend Domains API
Manage sending domains
AhaSend Email API
APIs for sending emails
AhaSend Messages API
Send and manage transactional messages
AhaSend Routes API
Manage inbound email routing
AhaSend SMTP Credentials API
Manage SMTP authentication credentials
AhaSend Statistics API
Access transactional email statistics
AhaSend Suppressions API
Manage email suppressions
AhaSend Utility API
Utility endpoints for health checks and diagnostics
AhaSend Webhooks API
Manage webhook notifications
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
AhaSend Email API
OPEN COLLECTIONPricing 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.
Ahasend 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.
Ahasend Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Transactional Email Delivery
Fast delivery of transactional emails including OTPs and confirmations, targeting sub-2-second delivery to Gmail at 99th percentile.
Email Tracking
Track email opens and link clicks with real-time analytics.
Webhook Notifications
Real-time webhook events for delivery, bounces, opens, clicks, and account alerts.
Email Routing
Route incoming emails to HTTP endpoints with automatic parsing of signatures and quoted replies.
Suppression Management
Automated handling of bounces, complaints, and unsubscribes with suppression lists.
Domain Management
Manage sending domains including DNS validation, DKIM rotation, and whitelabeling.
SMTP Relay
Compatible SMTP relay supporting any programming language or software.
Dedicated IPs
Free dedicated IPs for high-volume senders exceeding 300k emails per month.
S3-Compatible Archiving
Archive emails to S3-compatible storage with configurable retention policies.
SSO with OIDC
Enterprise single sign-on via OpenID Connect with granular API credential scoping.
Scroll within the panel for all 10 ·
Semantic Vocabularies 2
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.
Ahasend Api Context
JSON-LDAhasend Openapi V2 Context
JSON-LDSpectral Rules 2
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.
AhaSend API Rules
SPECTRALAhaSend API Rules
SPECTRALJSON Schema 63
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.
AccessDeniedResponse
JSON SCHEMAAttachment
JSON SCHEMABadRequestResponse
JSON SCHEMAContact
JSON SCHEMAContent
JSON SCHEMASuccessfulResponse
JSON SCHEMAAccountMembersResponse
JSON SCHEMAAccount
JSON SCHEMAAddMemberRequest
JSON SCHEMAAddress
JSON SCHEMAAPIKey
JSON SCHEMAAPIKeyScope
JSON SCHEMAAttachment
JSON SCHEMABounce
JSON SCHEMABounceStatisticsResponse
JSON SCHEMABounceStatistics
JSON SCHEMACreateAPIKeyRequest
JSON SCHEMACreateConversationMessageRequest
JSON SCHEMACreateDomainRequest
JSON SCHEMACreateMessageRequest
JSON SCHEMACreateMessageResponse
JSON SCHEMACreateRouteRequest
JSON SCHEMACreateSingleMessageResponse
JSON SCHEMACreateSMTPCredentialRequest
JSON SCHEMACreateSuppressionRequest
JSON SCHEMACreateSuppressionResponse
JSON SCHEMACreateWebhookRequest
JSON SCHEMADeliverabilityStatisticsResponse
JSON SCHEMADeliverabilityStatistics
JSON SCHEMADeliveryEvent
JSON SCHEMADeliveryTime
JSON SCHEMADeliveryTimeStatisticsResponse
JSON SCHEMADeliveryTimeStatistics
JSON SCHEMADNSRecord
JSON SCHEMADomain
JSON SCHEMAMessageAttachment
JSON SCHEMAMessageContentParsed
JSON SCHEMAMessageContentPart
JSON SCHEMAMessageSchedule
JSON SCHEMAMessage
JSON SCHEMAMessageSummary
JSON SCHEMAPaginatedAPIKeysResponse
JSON SCHEMAPaginatedDomainsResponse
JSON SCHEMAPaginatedMessagesResponse
JSON SCHEMAPaginatedRoutesResponse
JSON SCHEMAPaginatedSMTPCredentialsResponse
JSON SCHEMAPaginatedSuppressionsResponse
JSON SCHEMAPaginatedWebhooksResponse
JSON SCHEMAPaginationInfo
JSON SCHEMARecipient
JSON SCHEMARetention
JSON SCHEMARoute
JSON SCHEMASMTPCredential
JSON SCHEMASuppression
JSON SCHEMATracking
JSON SCHEMAUpdateAccountRequest
JSON SCHEMAUpdateAPIKeyRequest
JSON SCHEMAUpdateDomainRequest
JSON SCHEMAUpdateRouteRequest
JSON SCHEMAUpdateWebhookRequest
JSON SCHEMAUserAccount
JSON SCHEMAWebhook
JSON SCHEMAScroll within the panel for all 63 ·
JSON Structure 63
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Api Access Denied Response Structure
JSON STRUCTUREApi Attachment Structure
JSON STRUCTUREApi Bad Request Response Structure
JSON STRUCTUREApi Contact Structure
JSON STRUCTUREApi Content Structure
JSON STRUCTUREApi Email Structure
JSON STRUCTUREApi Successful Response Structure
JSON STRUCTUREOpenapi V2 Account Members Response Structure
JSON STRUCTUREOpenapi V2 Account Structure
JSON STRUCTUREOpenapi V2 Add Member Request Structure
JSON STRUCTUREOpenapi V2 Address Structure
JSON STRUCTUREOpenapi V2 Api Key Scope Structure
JSON STRUCTUREOpenapi V2 Api Key Structure
JSON STRUCTUREOpenapi V2 Attachment Structure
JSON STRUCTUREOpenapi V2 Bounce Statistics Response Structure
JSON STRUCTUREOpenapi V2 Bounce Statistics Structure
JSON STRUCTUREOpenapi V2 Bounce Structure
JSON STRUCTUREOpenapi V2 Create Api Key Request Structure
JSON STRUCTUREOpenapi V2 Create Conversation Message Request Structure
JSON STRUCTUREOpenapi V2 Create Domain Request Structure
JSON STRUCTUREOpenapi V2 Create Message Request Structure
JSON STRUCTUREOpenapi V2 Create Message Response Structure
JSON STRUCTUREOpenapi V2 Create Route Request Structure
JSON STRUCTUREOpenapi V2 Create Single Message Response Structure
JSON STRUCTUREOpenapi V2 Create Smtp Credential Request Structure
JSON STRUCTUREOpenapi V2 Create Suppression Request Structure
JSON STRUCTUREOpenapi V2 Create Suppression Response Structure
JSON STRUCTUREOpenapi V2 Create Webhook Request Structure
JSON STRUCTUREOpenapi V2 Deliverability Statistics Response Structure
JSON STRUCTUREOpenapi V2 Deliverability Statistics Structure
JSON STRUCTUREOpenapi V2 Delivery Event Structure
JSON STRUCTUREOpenapi V2 Delivery Time Statistics Response Structure
JSON STRUCTUREOpenapi V2 Delivery Time Statistics Structure
JSON STRUCTUREOpenapi V2 Delivery Time Structure
JSON STRUCTUREOpenapi V2 Dns Record Structure
JSON STRUCTUREOpenapi V2 Domain Structure
JSON STRUCTUREOpenapi V2 Message Attachment Structure
JSON STRUCTUREOpenapi V2 Message Content Parsed Structure
JSON STRUCTUREOpenapi V2 Message Content Part Structure
JSON STRUCTUREOpenapi V2 Message Schedule Structure
JSON STRUCTUREOpenapi V2 Message Structure
JSON STRUCTUREOpenapi V2 Message Summary Structure
JSON STRUCTUREOpenapi V2 Paginated Api Keys Response Structure
JSON STRUCTUREOpenapi V2 Paginated Domains Response Structure
JSON STRUCTUREOpenapi V2 Paginated Messages Response Structure
JSON STRUCTUREOpenapi V2 Paginated Routes Response Structure
JSON STRUCTUREOpenapi V2 Paginated Smtp Credentials Response Structure
JSON STRUCTUREOpenapi V2 Paginated Suppressions Response Structure
JSON STRUCTUREOpenapi V2 Paginated Webhooks Response Structure
JSON STRUCTUREOpenapi V2 Pagination Info Structure
JSON STRUCTUREOpenapi V2 Recipient Structure
JSON STRUCTUREOpenapi V2 Retention Structure
JSON STRUCTUREOpenapi V2 Route Structure
JSON STRUCTUREOpenapi V2 Smtp Credential Structure
JSON STRUCTUREOpenapi V2 Suppression Structure
JSON STRUCTUREOpenapi V2 Tracking Structure
JSON STRUCTUREOpenapi V2 Update Account Request Structure
JSON STRUCTUREOpenapi V2 Update Api Key Request Structure
JSON STRUCTUREOpenapi V2 Update Domain Request Structure
JSON STRUCTUREOpenapi V2 Update Route Request Structure
JSON STRUCTUREOpenapi V2 Update Webhook Request Structure
JSON STRUCTUREOpenapi V2 User Account Structure
JSON STRUCTUREOpenapi V2 Webhook Structure
JSON STRUCTUREScroll within the panel for all 63 ·
Examples 62
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.
Api Attachment Example
EXAMPLEApi Contact Example
EXAMPLEApi Content Example
EXAMPLEApi Email Example
EXAMPLEOpenapi V2 Account Example
EXAMPLEOpenapi V2 Address Example
EXAMPLEOpenapi V2 Api Key Example
EXAMPLEOpenapi V2 Bounce Example
EXAMPLEOpenapi V2 Domain Example
EXAMPLEOpenapi V2 Recipient Example
EXAMPLEOpenapi V2 Retention Example
EXAMPLEOpenapi V2 Route Example
EXAMPLEOpenapi V2 Tracking Example
EXAMPLEOpenapi V2 Webhook Example
EXAMPLEScroll within the panel for all 62 ·
Security Posture 3
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.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Password Reset Emails
Send secure one-time password and password reset links with guaranteed fast delivery.
Email Verification
Deliver account verification emails for new user signups.
Order Confirmation Emails
Transactional order and shipping confirmation emails for e-commerce.
System Alerts
Programmatic email alerts and notifications from applications and infrastructure.
Inbound Email Processing
Route and process incoming emails in applications using email routing.
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Node.js
Native Node.js integration with code examples and SDK support.
Python
Python integration examples for sending emails via API or SMTP.
PHP / Symfony
PHP integration including Symfony Mailer transport support.
Ruby on Rails
Ruby integration with Rails ActionMailer transport.
Go
Official Go SDK for the AhaSend API.
WordPress
WordPress plugin for routing site emails through AhaSend.
Java
Java client generated from OpenAPI spec.
Scroll within the panel for all 7 ·
Resources
Every other property we hold for AhaSend — 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.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
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/ahasend · machine-readable index on apis.io