DATA · DATA & ANALYTICS
Funnels, retention, cohorts, and event segmentation from their own project.
Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.
Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.
Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
amplitude_delete_api_2_taxonomy_category_by_category_idWRITEDelete an event category by sending a DELETE request with the category ID.
amplitude_delete_api_2_taxonomy_event_by_event_typeWRITEDelete an event type by sending a DELETE request with the event type name as a path parameter.
amplitude_delete_api_2_taxonomy_event_property_by_event_propertyWRITEDelete an event property by sending a DELETE request with the event property as a path parameter.
amplitude_delete_api_2_taxonomy_user_property_by_user_propertyWRITEDeletes a single user property by name.
amplitude_get_api_2_compositionREADGet the distribution of users across values of a user property in the specified date range.
amplitude_get_api_2_events_listREADGet the list of events with the current week totals, uniques, and % DAU (daily active users).
amplitude_get_api_2_events_segmentationREADGet metrics for an event with segmentation.
amplitude_get_api_2_exportREADExport your project's event data. The response is a ZIP archive of JSON files, not JSON; it is returned base64-wrapped. 404 means there is no data in the range. Max 365 days per query, 4GB per response.
amplitude_get_api_2_funnelsREADGet funnel drop-off and conversion rates.
amplitude_get_api_2_realtimeREADGet active user numbers with 5-minute granularity for the last two days.
amplitude_get_api_2_retentionREADGet user retention for specific starting and returning actions.
amplitude_get_api_2_revenue_ltvREADGet the lifetime value of new users.
amplitude_get_api_2_sessions_averageREADGet the average session length (in seconds) for each day in the specified date range.
amplitude_get_api_2_sessions_lengthREADGet the number of sessions for each predefined length (bucket) period during a specified date range.
amplitude_get_api_2_sessions_peruserREADGet the average number of sessions per user on each day in the specified date range.
amplitude_get_api_2_taxonomy_categoryREADGet all event categories in your project.
amplitude_get_api_2_taxonomy_category_by_category_nameREADGet the ID of an event category in your project by sending a GET request with the category name.
amplitude_get_api_2_taxonomy_eventREADRetrieves all event types in a project. This request has no required parameters.
amplitude_get_api_2_taxonomy_event_by_event_typeREADGet a single event type by name. Send a GET request with the event name.
amplitude_get_api_2_taxonomy_event_propertyREADGet shared or event-specific event properties.
amplitude_get_api_2_taxonomy_group_propertyREADGet shared or group-specific group properties.
amplitude_get_api_2_taxonomy_group_property_by_group_propertyREADGet a single group property by sending a GET request with the group property name as a path parameter.
amplitude_get_api_2_taxonomy_user_propertyREADRetrieves all user properties in your account. The request has no required parameters.
amplitude_get_api_2_taxonomy_user_property_by_user_propertyREADRetrieves a single user property by name.
amplitude_get_api_2_useractivityREADGet a user summary and the user most or least recent events. Rate limited to 10 concurrent requests and 360 queries per hour, separately from the other Dashboard REST endpoints.
amplitude_get_api_2_usersREADGet the number of active or new users.
amplitude_get_api_2_usersearchREADSearch for a user by Amplitude ID, device ID, user ID, or user ID prefix. Rate limited to 10 concurrent requests and 360 queries per hour, separately from the other Dashboard REST endpoints.
amplitude_get_api_3_chart_by_chart_id_csvREADGet JSON results from any saved chart by chart ID. The chart is addressed by the id in its web-app URL. Amplitude documents the response only as: responses vary based on the chart type -- and the path ends in /csv while the same sentence calls the result JSON, so the content type is not something this integration asserts; whatever comes back is returned as JSON when Amplitude labels it JSON and as labelled text or base64 otherwise.
amplitude_get_api_3_cohortsREADGet all discoverable cohorts for an app.
amplitude_get_api_3_cohorts_usageREADCheck your current monthly usage and limit for the Behavioral Cohorts Download API. Reports how much of the 500-per-month Cohort Download allowance this project has used. Usage resets on the first of each month UTC.
amplitude_get_api_5_cohorts_request_by_idREADGet a discoverable cohort using its cohort_id. This is step one of the cohort download operation. Behavioral Cohorts Download, a Growth and Enterprise plan feature capped at 500 requests per month. This starts an async job and answers 202 with a request_id; poll the request-status tool, then fetch the file tool.
amplitude_get_api_5_cohorts_request_by_requestid_fileREADAfter the job finishes running, download the cohort. Downloads the finished async cohort export. Large cohorts answer a 302 redirect to a pre-signed URL valid for one minute; the response is a file, not JSON.
amplitude_get_api_5_cohorts_request_status_by_request_idREADPoll the request status using the request_id retrieved for the cohort. This is step two of the cohort download operation. Polls the async cohort download started by the cohort request tool. 202 means JOB INPROGRESS; 200 means JOB COMPLETED.
amplitude_post_api_2_taxonomy_categoryWRITECreate an event category in your project.
amplitude_post_api_2_taxonomy_eventWRITECreate an event type by sending a POST request to the taxonomy event endpoint with parameters in the body.
amplitude_post_api_2_taxonomy_event_by_event_type_restoreWRITERestore an event type by sending a POST request with the event type name as a path parameter.
amplitude_post_api_2_taxonomy_event_propertyWRITECreate an event property by sending a POST request with the required information in the body. The classifications field is only accepted when Data Access Controls is enabled at the account level.
amplitude_post_api_2_taxonomy_event_property_by_event_property_restoreWRITERestore an event property by sending a POST request with the event property as a path parameter. Answers 201, not 200.
amplitude_post_api_2_taxonomy_group_propertyWRITECreate a group property by sending a POST request with the required information in the body. The classifications field is only accepted when Data Access Controls is enabled at the account level.
amplitude_post_api_2_taxonomy_user_propertyWRITECreate a user property by sending a POST request with the user property name in the body. The classifications field is only accepted when Data Access Controls is enabled at the account level.
amplitude_post_api_2_taxonomy_user_property_by_user_property_restoreWRITERestore a single user property by name.
amplitude_post_api_3_cohorts_membershipWRITEAdd and remove IDs to update existing cohort membership incrementally. A single request is limited to 100,000 identifiers.
amplitude_post_api_3_cohorts_uploadWRITEGenerate a new cohort or update an existing cohort by uploading a set of User IDs or Amplitude IDs. A single request is limited to 100,000 identifiers and a cohort to 2 million users.
amplitude_put_api_2_taxonomy_category_by_category_idWRITEUpdate the name of an event category by sending a PUT request with the category ID and a new name in the body.
amplitude_put_api_2_taxonomy_event_by_event_typeWRITEUpdate an event type by sending a PUT request with the event type name.
amplitude_put_api_2_taxonomy_event_property_by_event_propertyWRITEUpdate an event property by sending a PUT request with the event property name as a path parameter. The classifications field is only accepted when Data Access Controls is enabled at the account level.
amplitude_put_api_2_taxonomy_group_property_by_group_propertyWRITEUpdate a group property by sending a PUT request with the group property name as a path parameter. The classifications field is only accepted when Data Access Controls is enabled at the account level.
amplitude_put_api_2_taxonomy_user_property_by_user_propertyWRITEUpdate a user property by sending a PUT request with the user property name as a path parameter. The classifications field is only accepted when Data Access Controls is enabled at the account level.
Put Amplitude behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.