Amplitude Batch Event Upload API

The Amplitude Batch Event Upload API is optimized for high-volume server-side event ingestion. It accepts batches of events up to 20MB per request and is designed for use cases where data volume may exceed the limits of the standard HTTP V2 API. The API uses the same event structure as the HTTP V2 API and is recommended for data pipelines processing millions of events.

Documentation

Other Resources

🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/apis.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-annotation-lifecycle-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-cohort-export-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-cohort-upload-verify-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-dsar-request-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-event-property-lifecycle-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-experiment-lifecycle-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-flag-rollout-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-identity-merge-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-ingest-and-segment-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-scim-user-provisioning-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-taxonomy-event-governance-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-user-360-lookup-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/amplitude/refs/heads/main/arazzo/amplitude-variant-evaluation-workflow.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/batch-event-upload-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: amplitude:batch-event-upload-api
name: Amplitude Batch Event Upload API
tags:
- Analytics
- Batch
- Event
- Ingestion
tags_raw:
- Analytics
- Batch
- Events
- Ingestion
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
baseURL: https://api2.amplitude.com
humanURL: https://amplitude.com/docs/apis/analytics/batch-event-upload
properties:
- url: https://amplitude.com/docs/apis/analytics/batch-event-upload
  type: Documentation
description: The Amplitude Batch Event Upload API is optimized for high-volume server-side event ingestion.
  It accepts batches of events up to 20MB per request and is designed for use cases where data volume
  may exceed the limits of the standard HTTP V2 API. The API uses the same event structure as the HTTP
  V2 API and is recommended for data pipelines processing millions of events.