Amplitude
Product analytics events and cohorts.
AnalyticsAPI key54 endpoints
Endpoints
| Operation | Method & path | Effect | Latency | Rate | Cost |
|---|---|---|---|---|---|
AMPLITUDE_ASSIGN_ANNOTATIONS_TO_CATEGORY Tool to bulk assign multiple annotations to a category in Amplitude. Use when you need to organize annotations by assigning them to a specific category. | POST /composio/amplitude/amplitude_assign_annotations_to_category | external_send | — | — | managed |
AMPLITUDE_CANCEL_DELETION Cancel a pending user deletion request in Amplitude. Use this to remove a user from a scheduled deletion job before it completes. Only works on deletion jobs in 'Staging' status (not yet submitted). | POST /composio/amplitude/amplitude_cancel_deletion | external_send | — | — | managed |
AMPLITUDE_CHECK_COHORT_STATUS Check the status of a cohort export request. This action allows you to: - Poll the status of an in-progress cohort download request - Determine if a cohort is ready for download | POST /composio/amplitude/amplitude_check_cohort_status | external_send | — | — | managed |
AMPLITUDE_CREATE_ANNOTATION Create a chart annotation in Amplitude to mark important dates. Use to highlight key events like feature releases, marketing campaigns, or product updates on analytics charts. | POST /composio/amplitude/amplitude_create_annotation | external_send | — | — | managed |
AMPLITUDE_CREATE_ANNOTATION_CATEGORY Tool to create an annotation category in Amplitude to organize annotations. Use when you need to create a new category for grouping related annotations. | POST /composio/amplitude/amplitude_create_annotation_category | external_send | — | — | managed |
AMPLITUDE_CREATE_EVENT_CATEGORY Create a new event category in Amplitude. This action allows you to: - Create a new event category to organize event types - Validate category name before creation Key features: - Creates event categories for organizing events - Returns success/failure status | POST /composio/amplitude/amplitude_create_event_category | external_send | — | — | managed |
AMPLITUDE_CREATE_EVENT_TYPE Create a new event type in Amplitude. This action allows you to: - Define a new event type with various properties - Associate the event with a category - Add metadata like description, tags, and owner Key features: - Creates trackable events in your Amplitude project - Supports full event type configuration | POST /composio/amplitude/amplitude_create_event_type | external_send | — | — | managed |
AMPLITUDE_CREATE_RELEASE Create a release to document product changes. Use when you want to track app version releases and their impact on metrics. Can be integrated into deployment workflows to automatically log releases in Amplitude. | POST /composio/amplitude/amplitude_create_release | external_send | — | — | managed |
AMPLITUDE_DELETE_ANNOTATION Delete a chart annotation from Amplitude. Use to remove existing annotations from charts. | POST /composio/amplitude/amplitude_delete_annotation | external_send | — | — | managed |
AMPLITUDE_DELETE_ANNOTATION_CATEGORY Delete an annotation category from Amplitude. Use when you need to remove an annotation category that is no longer needed. | POST /composio/amplitude/amplitude_delete_annotation_category | external_send | — | — | managed |
AMPLITUDE_DELETE_EVENT_CATEGORY Delete an event category from Amplitude. This action allows you to: - Delete an existing event category - Remove category organization from events Key features: - Permanently removes event categories - Returns success/failure status | POST /composio/amplitude/amplitude_delete_event_category | external_send | — | — | managed |
AMPLITUDE_DELETE_EVENT_TYPE Delete an event type from Amplitude. This action allows you to: - Remove an event type from your project - Mark live events as deleted - Remove planned events from the tracking plan Key features: - Different behavior based on event status (live, planned, etc.) - Returns success/failure status | POST /composio/amplitude/amplitude_delete_event_type | external_send | — | — | managed |
Showing 12 of 54 Amplitude actions. Every action is in the provider catalog, and the CLI and MCP list them with their inputs.