GetResponse
GetResponse is an online marketing platform offering email marketing, marketing automation, landing pages, webinars, and conversion funnels for small businesses, marketers, and enterprises. The platform provides tools to grow email lists, automate campaigns, segment audiences, and engage customers across multiple channels. The GetResponse API v3 is a JSON REST API that uses X-Auth-Token header authentication to manage contacts, campaigns, newsletters, autoresponders, landing pages, webinars, and more.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles GetResponse the way a machine reads it — 14 machine-readable artifacts across 9 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 — GetResponse scores 36.4/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). 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 GetResponse
Each block below is one kind of artifact we hold for GetResponse. 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 9
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.
GetResponse API v3
JSON REST API for managing contacts, campaigns, newsletters, autoresponders, landing pages, webinars, custom fields, tags, segments, and workflows in the GetResponse platform. A...
GetResponse Accounts API
The Accounts API from GetResponse — 1 operation(s) for accounts.
GetResponse Autoresponders API
The Autoresponders API from GetResponse — 2 operation(s) for autoresponders.
GetResponse Campaigns API
The Campaigns API from GetResponse — 2 operation(s) for campaigns.
GetResponse Contacts API
The Contacts API from GetResponse — 2 operation(s) for contacts.
GetResponse Custom Fields API
The Custom Fields API from GetResponse — 1 operation(s) for custom fields.
GetResponse Newsletters API
The Newsletters API from GetResponse — 2 operation(s) for newsletters.
GetResponse Tags API
The Tags API from GetResponse — 1 operation(s) for tags.
GetResponse Webhooks API
The Webhooks API from GetResponse — 1 operation(s) for webhooks.
Scroll within the panel for all 9 ·
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).
GetResponse API v3
OPEN COLLECTIONSecurity 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.
Resources
Every other property we hold for GetResponse — 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
Documentation 2
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 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/getresponse · machine-readable index on apis.io