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
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Export returns ZIP archives containing one JSON event per line. Requests select UTC server_upload_time hours, with a 4GB response limit and at most 365 days per request.
Amplitude raw event Export API ↗
Upload-time range, ZIP JSON response and size limits · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Export returns ZIP archives containing one JSON event per line. Requests select UTC server_upload_time hours, with a 4GB response limit and at most 365 days per request.
Amplitude raw event Export API ↗
Upload-time range, ZIP JSON response and size limits · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Upload-hour start/end bounds select raw events; dashboard queries provide a separate aggregate route. The assessed raw export is fixed-range retrieval rather than relational SQL.
Amplitude raw event Export API ↗
Upload-time range, ZIP JSON response and size limits · Checked 2026-10-16
Access cost barrier -
-
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
The reviewed authentication/export sources do not establish complete minimum-plan and fixed-fee conditions for this project API portfolio.
Amplitude export quotas and retry ↗
Project-key default quotas and retry handling · Checked 2026-10-16
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
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Customers control project API key/secret credentials used by external API clients. Regional endpoints and project permissions are part of the boundary; cross-project views do not own exportable events.
Amplitude API authentication ↗
Project API key and secret authentication · Checked 2026-10-16
Downstream permission -
-
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Amplitude API authentication ↗
Project API key and secret authentication · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
HTTP V2 accepts event ingestion into the selected project. This documents event creation, without claiming arbitrary updates to previously stored event records.
Amplitude HTTP V2 event ingestion ↗
Event upload request and response · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Amplitude API authentication ↗
Project API key and secret authentication · 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
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Advance an upload-hour watermark only after the documented availability delay and complete archive validation. Late event_time values belong to the server upload hour; overlapping retries need destination deduplication.
Amplitude upload-time extraction ↗
Data availability and consistency; upload checkpoint · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Export defaults are four concurrent requests and 360 requests/hour per project API key, with possible overrides. 429 identifies rate or concurrency exhaustion; retry uses bounded backoff and honors Retry-After when present.
Amplitude export quotas and retry ↗
Project-key default quotas and retry handling · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Raw exports contain current retained event payloads for selected upload windows; a general update/deletion tombstone feed is not established.
Amplitude upload-time extraction ↗
Data availability and consistency; upload checkpoint · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Upload windows can be re-requested with overlap and deduplication. Archive bytes can differ between requests; 365 days is a per-request range limit, not guaranteed retention or a durable checkpoint.
Amplitude upload-time extraction ↗
Data availability and consistency; upload checkpoint · 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
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Raw event JSON can be retained in customer storage; dashboard CSV supplies a separate selected-report route. Saved analyses, definitions, identity behavior and full service configuration are not established as independently restorable.
Amplitude event export format ↗
JSON event schema and archive response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Amplitude event export format ↗
JSON event schema and archive response · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Raw event JSON can be retained in customer storage; dashboard CSV supplies a separate selected-report route. Saved analyses, definitions, identity behavior and full service configuration are not established as independently restorable.
Amplitude event export format ↗
JSON event schema and archive response · 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
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Amplitude API authentication ↗
Project API key and secret authentication · Checked 2026-10-16
Rights to custom logic -
-
Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Amplitude API authentication ↗
Project API key and secret authentication · 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
Customers control project API key/secret credentials used by external API clients. Regional endpoints and project permissions are part of the boundary; cross-project views do not own exportable events.
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
Export returns ZIP archives containing one JSON event per line. Requests select UTC server_upload_time hours, with a 4GB response limit and at most 365 days per request. Upload-hour start/end bounds select raw events; dashboard queries provide a separate aggregate route. The assessed raw export is fixed-range retrieval rather than relational SQL.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | HTTP Basic | Customer | No | customer authorization | 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
The reviewed authentication/export sources do not establish complete minimum-plan and fixed-fee conditions for this project API portfolio.
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
HTTP V2 accepts event ingestion into the selected project. This documents event creation, without claiming arbitrary updates to previously stored event records.
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
Advance an upload-hour watermark only after the documented availability delay and complete archive validation. Late event_time values belong to the server upload hour; overlapping retries need destination deduplication. Export defaults are four concurrent requests and 360 requests/hour per project API key, with possible overrides. 429 identifies rate or concurrency exhaustion; retry uses bounded backoff and honors Retry-After when present.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Raw exports contain current retained event payloads for selected upload windows; a general update/deletion tombstone feed is not established. | Amplitude upload-time extraction ↗Data availability and consistency; upload checkpointChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Upload windows can be re-requested with overlap and deduplication. Archive bytes can differ between requests; 365 days is a per-request range limit, not guaranteed retention or a durable checkpoint. | Amplitude upload-time extraction ↗Data availability and consistency; upload checkpointChecked 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
Raw event JSON can be retained in customer storage; dashboard CSV supplies a separate selected-report route. Saved analyses, definitions, identity behavior and full service configuration are not established as independently restorable.
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 implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
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 scopeAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Export returns ZIP archives containing one JSON event per line. Requests select UTC server_upload_time hours, with a 4GB response limit and at most 365 days per request. | Amplitude raw event Export API ↗Upload-time range, ZIP JSON response and size limitsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Export returns ZIP archives containing one JSON event per line. Requests select UTC server_upload_time hours, with a 4GB response limit and at most 365 days per request. | Amplitude raw event Export API ↗Upload-time range, ZIP JSON response and size limitsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Upload-hour start/end bounds select raw events; dashboard queries provide a separate aggregate route. The assessed raw export is fixed-range retrieval rather than relational SQL. | Amplitude raw event Export API ↗Upload-time range, ZIP JSON response and size limitsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Customers control project API key/secret credentials used by external API clients. Regional endpoints and project permissions are part of the boundary; cross-project views do not own exportable events. | Amplitude API authentication ↗Project API key and secret authenticationChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. The reviewed authentication/export sources do not establish complete minimum-plan and fixed-fee conditions for this project API portfolio. | Amplitude export quotas and retry ↗Project-key default quotas and retry handlingChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Amplitude API authentication ↗Project API key and secret authenticationChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. HTTP V2 accepts event ingestion into the selected project. This documents event creation, without claiming arbitrary updates to previously stored event records. | Amplitude HTTP V2 event ingestion ↗Event upload request and responseChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Customers can build or choose applications using the documented API and the disclosed authorization route. | Amplitude API authentication ↗Project API key and secret authenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Advance an upload-hour watermark only after the documented availability delay and complete archive validation. Late event_time values belong to the server upload hour; overlapping retries need destination deduplication. | Amplitude upload-time extraction ↗Data availability and consistency; upload checkpointChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Export defaults are four concurrent requests and 360 requests/hour per project API key, with possible overrides. 429 identifies rate or concurrency exhaustion; retry uses bounded backoff and honors Retry-After when present. | Amplitude export quotas and retry ↗Project-key default quotas and retry handlingChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Raw event JSON can be retained in customer storage; dashboard CSV supplies a separate selected-report route. Saved analyses, definitions, identity behavior and full service configuration are not established as independently restorable. | Amplitude event export format ↗JSON event schema and archive responseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Amplitude event export format ↗JSON event schema and archive responseChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Amplitude API authentication ↗Project API key and secret authenticationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Amplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Amplitude API authentication ↗Project API key and secret authenticationChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedAmplitude Analytics / customer project key/secret, raw Export API, HTTP V2 event ingestion and dashboard CSV downloads; Session Replay, cross-project views and separately entitled warehouse delivery are excluded. Raw event JSON can be retained in customer storage; dashboard CSV supplies a separate selected-report route. Saved analyses, definitions, identity behavior and full service configuration are not established as independently restorable. | Amplitude event export format ↗JSON event schema and archive responseChecked 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
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.