Delete annotation with the Mixpanel API
Deletes an annotation. The service account needs the Analyst role or higher on the project.
- Identifier
- mixpanel_delete_annotation
The request
POST https://connect.reportei.com/api/tools/mixpanel_delete_annotation/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"project_id": 1,
"annotation_id": 1
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| project_id | integer | Yes | Id of the project, sent as a number: a key of results.projects in List projects, or the number after /project/ in the URL of Mixpanel. |
| annotation_id | integer | Yes | Id of the annotation, from List annotations. |
Supported connections
Your customer connects their Mixpanel account once, with one of the modes below. The same connection serves every tool of the toolkit.
Username and password
Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/mixpanel_delete_annotation. It becomes your agent's tool definition with no conversion.
Other Mixpanel tools
- List projectsGETReturns, under results, the service account itself and the organizations, projects and workspaces it can access, each keyed by id. The keys of results.projects are the project_id the other tools ask for, and results.workspaces has the workspace_id of projects that use data views.
- Get saved reportGETReturns the data of a saved Insights or Funnels report, computed with the date range and filters saved in the report. Counts toward the Query API limit of 60 queries per hour.
- List event namesGETLists the names of the most common events of the project in the last 31 days, to use as the event arguments of the other tools. Counts toward the Query API limit of 60 queries per hour.
- List event propertiesGETLists the most common property names of one event, to build the on and where expressions of Get retention report. Counts toward the Query API limit of 60 queries per hour.
- Get event countsGETReturns, period by period, the total, unique or average count of one or more events between two dates. Counts toward the Query API limit of 60 queries per hour.
- Get retention reportGETReturns, for each cohort date, how many users entered the cohort (first) and how many came back in each interval after it (counts). Counts toward the Query API limit of 60 queries per hour.
- List cohortsPOSTLists the saved cohorts of the project with id, name, number of users, description, creation date and visibility. Counts toward the Query API limit of 60 queries per hour.
- Search profilesPOSTReturns the user profiles that match a where expression, a cohort or a list of distinct_ids, with their properties. A page holds up to page_size profiles: for the next one, repeat the call with the same filters, the session_id of the response and page plus one. Counts toward the Query API limit of 60 queries per hour.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
