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
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
V3 exposes structured billing accounts and subscriptions.
Recurly V3 OpenAPI specification v2021-02-25 ↗
paths./accounts.get; paths./subscriptions.get · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Follow next until has_more is false; list pages contain 1–200 records.
Recurly V3 OpenAPI specification v2021-02-25 ↗
info.description > Pagination; components.parameters.limit · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Account and subscription lists support updated_at/created_at, time windows and resource filters.
Recurly V3 OpenAPI specification v2021-02-25 ↗
components.parameters.sort_dates; filter_begin_time; filter_end_time · Checked 2026-10-16
Access cost barrier -
-
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
REST API keys ↗
REST API keys; Prerequisites; Limitations; Generate an API key · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
REST API keys ↗
REST API keys; Prerequisites; Limitations; Generate an API key · Checked 2026-10-16
Downstream permission -
-
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
REST API keys ↗
REST API keys; Prerequisites; Limitations; Generate an API key · Checked 2026-10-16
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
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Create and update billing accounts; deactivation/redaction are separately governed actions.
Recurly V3 OpenAPI specification v2021-02-25 ↗
paths./accounts.post; paths./accounts/{account_id}.put · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
External applications can use customer-managed REST keys; chosen-third-party contract approval remains unresolved.
REST API keys ↗
Definition; Generate an API key · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Ascending updated_at and time bounds support overlapping mutable-record polling.
Recurly V3 OpenAPI specification v2021-02-25 ↗
components.parameters.sort_dates; filter_begin_time; filter_end_time · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
The V3 specification publishes sandbox/production numeric limits, 429 behavior and runtime limit headers.
Recurly V3 OpenAPI specification v2021-02-25 ↗
info.description > Limits · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Updated-time discovery is supported; account deactivation is not proof of complete hard-delete capture.
Recurly V3 OpenAPI specification v2021-02-25 ↗
components.parameters.sort_dates; paths./accounts/{account_id}.delete · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Repeat unfiltered permitted account/subscription listings to rebuild current state. The 60-day export window is not a retained account-change log; deleted payloads and intermediate versions remain unestablished.
Recurly V3 OpenAPI specification v2021-02-25 ↗
info.description > Pagination; paths./accounts.get; paths./subscriptions.get · Checked 2026-10-16
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
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Customers can retrieve structured nightly export files and retain them externally.
Automated exports ↗
Accessing the data · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
A customer cancellation retrieval window and any exit charges have not been established.
REST API keys ↗
REST API keys; Prerequisites; Limitations; Generate an API key · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Portable records and export types are established, qualified by product/features and selected schemas.
Data imports and exports ↗
Available exports > Accounts & billing; Subscriptions · Checked 2026-10-16
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
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Customer-authored external integration code is supported; native workflow authoring portability is unestablished.
Recurly V3 OpenAPI specification v2021-02-25 ↗
Getting Started; Pagination · Checked 2026-10-16
Rights to custom logic -
-
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
REST API keys ↗
REST API keys; Prerequisites; Limitations; Generate an API key · Checked 2026-10-16
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
Users with Integration permission can generate, revoke and rotate REST API keys. Keys authenticate with HTTP Basic and grant full account access rather than per-object read-only scopes; external integration permissions do not establish a portable native workflow contract.
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
V3 list endpoints return next and has_more and accept up to 200 records per page. Account/subscription listing supports updated_at ascending order and begin_time/end_time filters; optional Automated Exports provides nightly selected datasets with a 60-day file window.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Recurly customer API | HTTP Basic | Customer | Not confirmed | self service | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
REST API key availability is documented on all Recurly plans, but the reviewed pages do not establish a fixed-fee-free baseline API entitlement. Automated Exports is explicitly unavailable on Starter and Pro and requires an upgrade; its price must not be applied to every API route.
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
V3 POST /accounts creates an account and PUT /accounts/{account_id} updates it. Deactivation and data redaction are separate operations; broad account credentials require exact target and field controls before any future write.
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
Ascending updated_at traversal with overlapping begin/end windows supports mutable-account refresh. Automated export files are retained for 60 days and download URLs for 60 minutes; these are file windows, not retained change-event replay guarantees.
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 establishedRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Updated-time discovery is supported; account deactivation is not proof of complete hard-delete capture. | Recurly V3 OpenAPI specification v2021-02-25 ↗components.parameters.sort_dates; paths./accounts/{account_id}.deleteChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Repeat unfiltered permitted account/subscription listings to rebuild current state. The 60-day export window is not a retained account-change log; deleted payloads and intermediate versions remain unestablished. | Recurly V3 OpenAPI specification v2021-02-25 ↗info.description > Pagination; paths./accounts.get; paths./subscriptions.getChecked 2026-10-16 |
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
Structured API records and selected export files can be held outside Recurly. Export versions need explicit configuration updates, and available types depend on features; complete native workflow/configuration recovery is not established.
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 maintain external account and billing integration code (without making native workflow artifacts portable). Ownership, reusable export and independent execution of those native definitions remain unresolved.
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 scopeRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. V3 exposes structured billing accounts and subscriptions. | Recurly V3 OpenAPI specification v2021-02-25 ↗paths./accounts.get; paths./subscriptions.getChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Follow next until has_more is false; list pages contain 1–200 records. | Recurly V3 OpenAPI specification v2021-02-25 ↗info.description > Pagination; components.parameters.limitChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Account and subscription lists support updated_at/created_at, time windows and resource filters. | Recurly V3 OpenAPI specification v2021-02-25 ↗components.parameters.sort_dates; filter_begin_time; filter_end_timeChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | REST API keys ↗REST API keys; Prerequisites; Limitations; Generate an API keyChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. The lowest eligible paid plan and route-specific fixed API charges have not been established. | REST API keys ↗REST API keys; Prerequisites; Limitations; Generate an API keyChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | REST API keys ↗REST API keys; Prerequisites; Limitations; Generate an API keyChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Create and update billing accounts; deactivation/redaction are separately governed actions. | Recurly V3 OpenAPI specification v2021-02-25 ↗paths./accounts.post; paths./accounts/{account_id}.putChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. External applications can use customer-managed REST keys; chosen-third-party contract approval remains unresolved. | REST API keys ↗Definition; Generate an API keyChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Ascending updated_at and time bounds support overlapping mutable-record polling. | Recurly V3 OpenAPI specification v2021-02-25 ↗components.parameters.sort_dates; filter_begin_time; filter_end_timeChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. The V3 specification publishes sandbox/production numeric limits, 429 behavior and runtime limit headers. | Recurly V3 OpenAPI specification v2021-02-25 ↗info.description > LimitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Customers can retrieve structured nightly export files and retain them externally. | Automated exports ↗Accessing the dataChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. A customer cancellation retrieval window and any exit charges have not been established. | REST API keys ↗REST API keys; Prerequisites; Limitations; Generate an API keyChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Customer-authored external integration code is supported; native workflow authoring portability is unestablished. | Recurly V3 OpenAPI specification v2021-02-25 ↗Getting Started; PaginationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | REST API keys ↗REST API keys; Prerequisites; Limitations; Generate an API keyChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRecurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. Portable records and export types are established, qualified by product/features and selected schemas. | Data imports and exports ↗Available exports > Accounts & billing; SubscriptionsChecked 2026-10-16 |
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
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.