All integrations

Amplitude

DATA · DATA & ANALYTICS

Funnels, retention, cohorts, and event segmentation from their own project.

Acts as the person, not as itself

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.

Credentials never touch the agent

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.

Every call on the record

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.

What an agent can do

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_idWRITE

Delete an event category by sending a DELETE request with the category ID.

api
amplitude_delete_api_2_taxonomy_event_by_event_typeWRITE

Delete an event type by sending a DELETE request with the event type name as a path parameter.

api
amplitude_delete_api_2_taxonomy_event_property_by_event_propertyWRITE

Delete an event property by sending a DELETE request with the event property as a path parameter.

api
amplitude_delete_api_2_taxonomy_user_property_by_user_propertyWRITE

Deletes a single user property by name.

api
amplitude_get_api_2_compositionREAD

Get the distribution of users across values of a user property in the specified date range.

api
amplitude_get_api_2_events_listREAD

Get the list of events with the current week totals, uniques, and % DAU (daily active users).

api
amplitude_get_api_2_events_segmentationREAD

Get metrics for an event with segmentation.

api
amplitude_get_api_2_exportREAD

Export 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.

api
amplitude_get_api_2_funnelsREAD

Get funnel drop-off and conversion rates.

api
amplitude_get_api_2_realtimeREAD

Get active user numbers with 5-minute granularity for the last two days.

api
amplitude_get_api_2_retentionREAD

Get user retention for specific starting and returning actions.

api
amplitude_get_api_2_revenue_ltvREAD

Get the lifetime value of new users.

api
amplitude_get_api_2_sessions_averageREAD

Get the average session length (in seconds) for each day in the specified date range.

api
amplitude_get_api_2_sessions_lengthREAD

Get the number of sessions for each predefined length (bucket) period during a specified date range.

api
amplitude_get_api_2_sessions_peruserREAD

Get the average number of sessions per user on each day in the specified date range.

api
amplitude_get_api_2_taxonomy_categoryREAD

Get all event categories in your project.

api
amplitude_get_api_2_taxonomy_category_by_category_nameREAD

Get the ID of an event category in your project by sending a GET request with the category name.

api
amplitude_get_api_2_taxonomy_eventREAD

Retrieves all event types in a project. This request has no required parameters.

api
amplitude_get_api_2_taxonomy_event_by_event_typeREAD

Get a single event type by name. Send a GET request with the event name.

api
amplitude_get_api_2_taxonomy_event_propertyREAD

Get shared or event-specific event properties.

api
amplitude_get_api_2_taxonomy_group_propertyREAD

Get shared or group-specific group properties.

api
amplitude_get_api_2_taxonomy_group_property_by_group_propertyREAD

Get a single group property by sending a GET request with the group property name as a path parameter.

api
amplitude_get_api_2_taxonomy_user_propertyREAD

Retrieves all user properties in your account. The request has no required parameters.

api
amplitude_get_api_2_taxonomy_user_property_by_user_propertyREAD

Retrieves a single user property by name.

api
amplitude_get_api_2_useractivityREAD

Get 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.

api
amplitude_get_api_2_usersREAD

Get the number of active or new users.

api
amplitude_get_api_2_usersearchREAD

Search 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.

api
amplitude_get_api_3_chart_by_chart_id_csvREAD

Get 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.

api
amplitude_get_api_3_cohortsREAD

Get all discoverable cohorts for an app.

api
amplitude_get_api_3_cohorts_usageREAD

Check 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.

api
amplitude_get_api_5_cohorts_request_by_idREAD

Get 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.

api
amplitude_get_api_5_cohorts_request_by_requestid_fileREAD

After 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.

api
amplitude_get_api_5_cohorts_request_status_by_request_idREAD

Poll 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.

api
amplitude_post_api_2_taxonomy_categoryWRITE

Create an event category in your project.

api
amplitude_post_api_2_taxonomy_eventWRITE

Create an event type by sending a POST request to the taxonomy event endpoint with parameters in the body.

api
amplitude_post_api_2_taxonomy_event_by_event_type_restoreWRITE

Restore an event type by sending a POST request with the event type name as a path parameter.

api
amplitude_post_api_2_taxonomy_event_propertyWRITE

Create 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.

api
amplitude_post_api_2_taxonomy_event_property_by_event_property_restoreWRITE

Restore an event property by sending a POST request with the event property as a path parameter. Answers 201, not 200.

api
amplitude_post_api_2_taxonomy_group_propertyWRITE

Create 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.

api
amplitude_post_api_2_taxonomy_user_propertyWRITE

Create 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.

api
amplitude_post_api_2_taxonomy_user_property_by_user_property_restoreWRITE

Restore a single user property by name.

api
amplitude_post_api_3_cohorts_membershipWRITE

Add and remove IDs to update existing cohort membership incrementally. A single request is limited to 100,000 identifiers.

api
amplitude_post_api_3_cohorts_uploadWRITE

Generate 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.

api
amplitude_put_api_2_taxonomy_category_by_category_idWRITE

Update the name of an event category by sending a PUT request with the category ID and a new name in the body.

api
amplitude_put_api_2_taxonomy_event_by_event_typeWRITE

Update an event type by sending a PUT request with the event type name.

api
amplitude_put_api_2_taxonomy_event_property_by_event_propertyWRITE

Update 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.

api
amplitude_put_api_2_taxonomy_group_property_by_group_propertyWRITE

Update 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.

api
amplitude_put_api_2_taxonomy_user_property_by_user_propertyWRITE

Update 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.

api

Put Amplitude behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.