OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
GetResponse returns contact records through v3. Unconfirmed double-opt-in contacts are not returned by the ordinary contact collection.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Traverse /contacts with page/perPage and the documented collection headers; keep the same filters and sort.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
GetResponse collection pagination ↗
Collection pagination and response headers · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
query[changedOn] and query[createdOn] select date ranges; email, name and campaign filters refine the cohort.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Access cost barrier -
-
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Create an API key and send X-Auth-Token: api-key. Unused keys expire after 90 days; MAX accounts additionally send X-Domain.
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
Downstream permission -
-
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
POST /contacts queues creation and returns 202. Later rejection or unconfirmed opt-in can prevent a contact appearing in the list.
GetResponse current contact OpenAPI specification ↗
POST /contacts: 202, later rejection and double opt-in · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
changedOn filters support repeated current-contact extraction. Confirm queued writes and retain opt-in state; deletion delivery is unverified.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Budgets are 30,000 calls/10 minutes, 80/second and ten parallel requests. Wait for X-RateLimit-Reset or timeToReset after 429.
GetResponse throttling and recovery ↗
Time frame, Basic rate limits, Parallel requests and Reaching the limit · Checked 2026-10-22
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
changedOn identifies updates to current contacts. It does not establish delivery of hard-deletion identities.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
GetResponse current contact OpenAPI specification ↗
GET /contacts filters and contact-list response · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
Rights to custom logic -
-
GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
GetResponse API authentication ↗
API key, expiry and MAX X-Domain · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Create an API key and send X-Auth-Token: api-key. Unused keys expire after 90 days; MAX accounts additionally send X-Domain.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Traverse /contacts with page/perPage and the documented collection headers; keep the same filters and sort. query[changedOn] and query[createdOn] select date ranges; email, name and campaign filters refine the cohort.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| v3 contact listing and asynchronous contact creation | API key | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /contacts queues creation and returns 202. Later rejection or unconfirmed opt-in can prevent a contact appearing in the list.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
changedOn filters support repeated current-contact extraction. Confirm queued writes and retain opt-in state; deletion delivery is unverified.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. changedOn identifies updates to current contacts. It does not establish delivery of hard-deletion identities. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. GetResponse returns contact records through v3. Unconfirmed double-opt-in contacts are not returned by the ordinary contact collection. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Traverse /contacts with page/perPage and the documented collection headers; keep the same filters and sort. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 GetResponse collection pagination ↗Collection pagination and response headersChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. query[changedOn] and query[createdOn] select date ranges; email, name and campaign filters refine the cohort. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Create an API key and send X-Auth-Token: api-key. Unused keys expire after 90 days; MAX accounts additionally send X-Domain. | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. POST /contacts queues creation and returns 202. Later rejection or unconfirmed opt-in can prevent a contact appearing in the list. | GetResponse current contact OpenAPI specification ↗POST /contacts: 202, later rejection and double opt-inChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. changedOn filters support repeated current-contact extraction. Confirm queued writes and retain opt-in state; deletion delivery is unverified. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Budgets are 30,000 calls/10 minutes, 80/second and ten parallel requests. Wait for X-RateLimit-Reset or timeToReset after 429. | GetResponse throttling and recovery ↗Time frame, Basic rate limits, Parallel requests and Reaching the limitChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | GetResponse current contact OpenAPI specification ↗GET /contacts filters and contact-list responseChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -GetResponse / v3 contact listing and asynchronous contact creation; unconfirmed-contact search, campaigns and complete account migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | GetResponse API authentication ↗API key, expiry and MAX X-DomainChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.