Taxonomy API

The Taxonomy API grants Scholarship, Growth, and Enterprise users the ability to programmatically plan their event schema in the Taxonomy tab.

The Taxonomy API lets you create, get, update, and delete categories, event types, event properties, and user properties.

Authentication

API uses basic authentication, using the API key and secret key for your project. Pass base64-encoded credentials in the request header like {api-key}:{secret-key}. api-key replaces username, and secret-key replaces the password.

Your authorization header should look something like this:

--header 'Authorization: Basic YWhhbWwsdG9uQGFwaWdlZS5jb206bClwYXNzdzByZAo'`

For more information, see Find your API Credentials

Endpoints

Region	Endpoint
Standard server	`https://amplitude.com/api/2/`
EU residency server	`https://analytics.eu.amplitude.com/api/2/`

Considerations

You may have to URL encode special characters in the names of event types, event properties, and user properties. For example, encode Play Song as Play%20Song. Use the W3Schools encoding reference.
In responses, custom user properties have a gp: prefix. For example, gp:my_custom_property.
You must plan events or properties in the schema before you can delete them via this API.

Limits

For each endpoint, there is a concurrent and a rate limit. This limit restricts the number of requests you can run at the same time, while the rate limit restricts the total number of queries you can run per hour.

Limits are per project, and exceeding any of these limits returns a 429 error.

The endpoints use a cost per query model. Here are the max costs per API Key:

Concurrent Cost Limit: You can run queries that collectively add up to 4 cost at the same time.
Period Cost Limit: You can run up to 7200 cost per hour.

Cost structure of each endpoint:

GET: 1 cost
PUT: 2 cost
POST: 2 cost
DELETE: 2 cost

Event category

Event categories are a way to organize your event types into broad groups.

!!!example You want to track how users register for your app, checkout, and how they interact with the onboarding experience. You can bucket your events using these event categories:

1- Registration
2- Checkout
3- Onboarding

Create event category

Create an event category in your project.

POST /api/2/taxonomy/category

1curl --location --request POST 'https://amplitude.com/api/2/taxonomy/category' \
2--header 'Authorization: Basic {api-key}:{secret-key}' \ #credentials must be base64 encoded
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'category_name=CATEGORY_NAME'

1POST /api/2/taxonomy/category HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
4Content-Type: application/x-www-form-urlencoded
5category_name=CATEGORY_NAME

Example: Create an event category

1curl --location --request POST 'https://amplitude.com/api/2/taxonomy/category' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'category_name=Attribution'

1POST /api/2/taxonomy/category HTTP/1.1
2Host: amplitude.com
3Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 25
6category_name=Attribution

Body parameters

Name	Description
`category_name`	Required. Name of the category.

Response

A successful request returns a 200 OK response with a JSON body:

1{
2    "success" : true
3}

A failed request sends an error message with more information:

1{
2   "success" : false,
3   "errors" : [
4      {
5         "message" : "error info"
6      }
7   ]
8}

Get all event categories

Get all event categories in your project.

GET https://amplitude.com/api/2/taxonomy/category

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/category' \
2-u '{api_key}:{secret_key}'

1GET /api/2/taxonomy/category HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Response

A successful request returns a 200 OK status with a JSON body:

 1{
 2    "success": true,
 3    "data": [
 4        {
 5            "id": 412931,
 6            "name": "Attribution"
 7        },
 8        {
 9            "id": 412941,
10            "name": "Conversion"
11        }
12    ]
13}

A failed request returns a 400 Bad Request response with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Not found"
6        }
7    ]
8}

Get an event category

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

GET https://amplitude.com/api/2/taxonomy/category/:category_name

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/category/:category_name' \
2-u '{api_key}:{secret_key}'

1GET /api/2/taxonomy/category/:category_name HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Get a category's ID

This example get the ID for the event category named "Attribution".

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/category/Attribution' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

1GET /api/2/taxonomy/category/Attribution HTTP/1.1
2Host: amplitude.com
3Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=

Path parameters

Name	Description
`category_name`	Required. The name of the category

Response

A successful request returns a 200 OK status and a JSON body with the category's data:

1{
2    "success": true,
3    "data": {
4        "id": 412941,
5        "name": "Conversion"
6    }
7}

A failed request returns a 400 Bad Request status with more information about the error.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Not found"
6        }
7    ]
8}

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

PUT https://amplitude.com/api/2/taxonomy/category/:category_id

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/category/CATEGORY_ID' \
2-u '{api_key}:{secret_key}' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'category_name=NEW_NAME'

1PUT /api/2/taxonomy/category/CATEGORY_ID HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 23
6 
7category_name=NEW_NAME

Example: Rename a category

This example renames the category with the ID 412941 to "Converted".

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/category/412941' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'category_name=Converted'

1PUT /api/2/taxonomy/category/412941 HTTP/1.1
2Host: amplitude.com
3Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 23
6 
7category_name=Converted

Path parameters

Name	Description
`category_id`	Required. The ID of the category

Body parameters

Name	Description
`category_name`	Required. The new name of the category

200 ok response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

If there is a problem with your request, the request returns a 409 Conflict status, and a JSON body with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to operate on entity event_category, id \"4129\", that does not exist."
6        }
7    ]
8}

Delete an event category

Delete an event category. Send a DELETE request with the category ID.

DELETE https://amplitude.com/api/2/taxonomy/category/:category_id

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/category/:category_id' \
2-u '{api_key}:{secret_key}'

1DELETE /api/2/taxonomy/category/:category_id HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Delete a category

This example deletes the category with the ID 412941.

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/category/412941' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

1DELETE /api/2/taxonomy/category/412941 HTTP/1.1
2Host: amplitude.com
3Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=

Path parameters

Name	Description
`category_id`	Required. The ID of the category

200 ok response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

If there is a problem with your request, the request returns a 409 Conflict status, and a JSON body with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to operate on entity event_category, id \"412941\", that does not exist."
6        }
7    ]
8}

Event type

An event is any action a user can take, like start game or add to cart, or any activity associated with a user, like in-app notifications or push notifications.

You can use the API to manipulate event types.

Create an event type

Creates an event type. Send a POST request to https://amplitude.com/api/2/taxonomy/event and include a body with your parameters.

Note

Initialize the schema before you can add event types via the API.

1curl --location --request POST 'https://amplitude.com/api/2/taxonomy/event' \
2-u '{api_key}:{secret_key}' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'event_type=EVENT_TYPE' \
5--data-urlencode 'category=CATEGORY_NAME' \
6--data-urlencode 'description=DESCRIPTION'

1POST /api/2/taxonomy/event?=null HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} # credentials must be base64 encoded
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 80
6 
7event_type=EVENT_TYPE&category=CATEGORY_NAME&description=CATEGORY_DESCRIPTION

Example: Create an event type

This example creates the event type "Onboarding Start" with the category "Onboarding" and a description of "My new onboarding event".

1curl --location --request POST 'https://amplitude.com/api/2/taxonomy/event' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
3--data-urlencode 'event_type=Onboard Start' \
4--data-urlencode 'category=Onboarding' \
5--data-urlencode 'description=My new onboarding event. ' \

1 
2POST /api/2/taxonomy/event HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5 
6Content-Length: 92
7 
8event_type=Onboard%20Start&category=Onboarding&description=My%20new%20onboarding%20event.%20

Body parameters

Name	Description
`event_type`	Required. String. The event name.
`category`	Optional. String. The event type's category.
`description`	Optional. String. Details about the event type.

200 ok response

A successful request returns a 200 OK response with a JSON body:

1{
2    "success" : true
3}

409 conflict response

A failed request returns a 409 Conflict status with an error message.

1{
2   "success" : false,
3   "errors" : [
4      {
5         "message" : "error info"
6      }
7   ]
8}

Get all event types

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

GET https://amplitude.com/api/2/taxonomy/event

Note

Hidden events, those that have a visibility other than "Visible", don't appear in the response.

By default, deleted events will also not be included, but the showDeleted query parameter can be optionally added to the endpoint to include them:

GET https://amplitude.com/api/2/taxonomy/event?showDeleted=true

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event' \
2-u '{api_key}:{secret_key}'

1GET /api/2/taxonomy/event HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

200 OK response

A successful request returns a 200 OK status with a JSON body:

 1{
 2    "success": true,
 3    "data": [
 4        {
 5            "event_type": "Attribution",
 6            "category": {
 7                "name": "Attribution Events"
 8            },
 9            "description": null
10        },
11        {
12            "event_type": "Conversation",
13            "category": {
14                "name": "Conversion Events"
15            },
16            "description": "This event is fired when a user converts."
17        }
18    ]
19}

Get an event type

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

GET https://amplitude.com/api/2/taxonomy/event/:event_type

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event:event_type' \
2-u '{api_key}:{secret_key}'

1GET /api/2/taxonomy/event/:event_type HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Get an event type by name

This example gets the "Event 2" event type. This is a custom event, so it has a ce: prefix.

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event/ce:Event 2' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event/ce:Event 2' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

Path parameters

Name	Description
`event_type`	Required. String. The event name. Prefix custom event types with `ce:`.

200 OK response

A successful request returns a 200 OK status and a JSON body with the event type's data:

 1{
 2    "success": true,
 3    "data": {
 4        "event_type": "ce:Event 2",
 5        "category": {
 6            "name": "Conversion Events"
 7        },
 8        "description": null
 9    }
10}

400 Bad Request response

A failed request returns a 400 Bad Request status with more information about the error.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Not found"
6        }
7    ]
8}

Update an event type

Update an event type. Send a PUT request with the event type name.

PUT https://amplitude.com/api/2/taxonomy/event/:event_type

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/event/EVENT_TYPE_NAME' \
2-u '{api_key}:{secret_key}'
3--data-urlencode 'category=NEW_CATEGORY_NAME' \
4--data-urlencode 'display_name=NEW_EVENT_TYPE_DISPLAY_NAME'

1PUT /api/2/taxonomy/event/EVENT_TYPE_NAME HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} # credentials must be base64 encoded
4Content-Length: 41
5 
6category=NEW_CATEGORY_NAME&display_name=NEW_EVENT_TYPE_DISPLAY_NAME

Example: Update an event type

This example updates the event type "OnboardingBegin" with the category "Onboarding", event type name "OnboardStart", the display name "Onboarding Start", and a description of "User signed in and completed an onboarding task from modal". Because the event type is custom, it has the ce: prefix.

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/event/ce:OnboardBegin' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'new_event_type=OnboardStart' \
5--data-urlencode 'category=Onboarding' \
6--data-urlencode 'description=User signed in and completed an onboarding task from modal.' \
7--data-urlencode 'display_name=Onboarding Start'

1 
2PUT /api/2/taxonomy/event/ce:OnboardBegin HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 169
7 
8new_event_type=OnboardStart&category=Onboarding&description=User%20signed%20in%20and%20completed%20an%20onboarding%20task%20from%20modal.&display_name=Onboarding%20Start

Path parameters

Name	Description
`event_type`	Required. String. The event name. Prefix custom event types with `ce:`.

Body parameters

Name	Description
`new_event_type`	Optional. String. The event type's new name.
`category`	Optional. Current category name of the event type.
`description`	Optional. String. Details to add to the event type.
`display_name`	Optional. String. Display name of an event type. You can update the display name for an event type after it's ingested into Amplitude.

200 OK response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

If there is a problem with your request, the request returns a 409 Conflict status, and a JSON body with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to change the event display name for event \"ce:Event\", but the event is not in schema."
6        }
7    ]
8}

Delete an event type

Delete an event type.

DELETE https://amplitude.com/api/2/taxonomy/event/:event_type

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/event/EVENT_TYPE'
2-u '{api_key}:{secret_key}'

1DELETE /api/2/taxonomy/event/EVENT_TYPE HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Delete an event type

This example deletes the event type "Event1". Because the event type is custom, it has the ce: prefix.

1 
2curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/event/ce:Event1' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \

1 
2DELETE /api/2/taxonomy/event/ce:Event1 HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=

Path parameters

Name	Description
`event_type`	Required. The name of the event type. Prefix custom event types with `ce:`.

200 OK response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

If there is a problem with your request, the request returns a 409 Conflict status, and a JSON body with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to remove an event, \"ce:Event1\", that is not a planned event."
6        }
7    ]
8}

Event property

Event properties describe the attributes of an event. For example, if 'Swipe' is an event that you are tracking, then the event property ‘Direction’ could have the values ‘Left’ or ‘Right’.

Create an event property

Create an event property. Send a POST request to the endpoint with the required information in the body.

POST https://amplitude.com/api/2/taxonomy/event-property

1curl --location --request POST 'https://amplitude.com/api/2/taxonomy/event-property' \
2-u '{api_key}:{secret_key}' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'event_type=EVENT_TYPE' \
5--data-urlencode 'event_property=EVENT_PROPERTY' \

1POST /api/2/taxonomy/event-property HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 94
6 
7event_type=EVENT_TYPE&event_property=EVENT_PROPERTY

Example: Create an event property

This example creates the event property "Completed Task" with the description "User completed any onboarding task" for the event "Onboarding Start". The event property is a boolean type, is not required.

1 
2curl --location --request POST 'https://amplitude.com/api/2/taxonomy/event-property' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
4--data-urlencode 'event_type=Onboard Start' \
5--data-urlencode 'event_property=Completed Task' \
6--data-urlencode 'description=User completed any onboarding task' \
7--data-urlencode 'type=boolean' \
8--data-urlencode 'is_required=false'

1 
2POST /api/2/taxonomy/event-property HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5 
6Content-Length: 144
7 
8event_type=Onboard%20Start&event_property=Completed%20Task&type=boolean&is_required=false&description=User%20completed%20any%20onboarding%20task

Body parameters

Name	Description
`event_type`	Required. String. Name of the event type to which the event properties belong to.
`event_property`	Required. String. Name of the event property.
`description`	Optional. String. The event property's description.
`type`	Optional. String. Available with Govern Add-on. The event property's data type. Acceptable values are `string`, `number`, `boolean`, `enum`, and `any`
`regex`	Optional. String. Available with Govern Add-on. Regular expression, custom regex used for pattern matching or more complex values. For example, property zip code must have pattern `[0-9]{5}`
`enum_values`	Optional. String. Available with Govern Add-on. List of allowed values.
`is_array_type`	Optional. Boolean. Available with Govern Add-on.
`is_required`	Optional. Boolean. Available with Govern Add-on. Marks the property as required. When `true`, Amplitude flags events that are missing this property on the Taxonomy page in the web app.

200 OK response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

If there is a problem with your request, the request returns a 409 Conflict status, and a JSON body with more information.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to add an event property, \"Completed Task\" for event \"Onboard Start\", that already exists."
6        }
7    ]
8}

Get event properties

Get an event's properties.

GET https://amplitude.com/api/2/taxonomy/event-property

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event-property' \
3-u '{api_key}:{secret_key}' \
4--header 'Content-Type: application/x-www-form-urlencoded' \
5--data-urlencode 'event_type=EVENT_NAME'

1 
2GET /api/2/taxonomy/event-property HTTP/1.1
3Host: amplitude.com
4Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
5 
6event_type=EVENT_NAME

Example: get all of an event's properties

This example gets all event properties for the "Onboard Start" event.

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event-property' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA==' \
4--header 'Content-Type: application/x-www-form-urlencoded' \
5--data-urlencode 'event_type=Onboard Start'

1 
2GET /api/2/taxonomy/event-property HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA==
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 26
7 
8event_type=Onboard%20Start

Body parameters

Name	Description
`event_type`	Required. Name of the event type to which the event properties belong to.

200 OK response

A successful request returns a 200 OK status and a JSON body with a list of event properties and their data.

 1{
 2    "success": true,
 3    "data": [
 4        {
 5            "event_property": "Completed Task",
 6            "event_type": "Onboard Start",
 7            "description": "User completed a task during onboarding.",
 8            "type": "boolean",
 9            "regex": null,
10            "enum_values": null,
11            "is_array_type": false,
12            "is_required": false
13        },
14        {
15            "event_property": "Completed Tutorial",
16            "event_type": "Onboard Start",
17            "description": "",
18            "type": "any",
19            "regex": null,
20            "enum_values": null,
21            "is_array_type": false,
22            "is_required": false
23        }
24    ]
25}

Get a single event property

Get a single event property. Send a GET request with the event property name as a path parameter, and the event name in the body.

GET https://amplitude.com/api/2/taxonomy/event-property

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event-property?event_property=EVENT_PROPERTY' \
2-u '{api_key}:{secret_key}' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'event_type=EVENT_NAME'

1GET /api/2/taxonomy/event-property/EVENT_PROPERTY_NAME HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
4 
5event_type=EVENT_NAME

Example: Get a property from a specific event

This example gets a the "Completed Task" property for the "Onboard Start" event.

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/event-property?event_property=Completed Task' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
4--header 'Content-Type: application/x-www-form-urlencoded' \
5--data-urlencode 'event_type=Onboard Start'

1 
2GET /api/2/taxonomy/event-property?event_property=Completed Task HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA==
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 26
7 
8event_type=Onboard%20Start

Path parameters

Name	Description
`event_property`	Required. The event property name.

Body parameter

Name	Description
`event_type`	Required. Name of the event type to which the event properties belong to.

200 OK response

A successful request returns a 200 OK status and a JSON body containing information about the event property.

 1{
 2    "success": true,
 3    "data": {
 4        "event_property": "Shared",
 5        "event_type": "Onboard Finish",
 6        "description": "Whether user shared content.",
 7        "type": "boolean",
 8        "regex": null,
 9        "enum_values": null,
10        "is_array_type": false,
11        "is_required": false
12    }
13}

400 Bad Request response

If Amplitude can't find the event property, or you configure the request incorrectly, it returns a 400 Bad Request response and an error message.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Not found"
6        }
7    ]
8}

Update event property

Update an event property.

PUT https://amplitude.com/api/2/taxonomy/event-property/:event-property

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/event-property/EVENT_PROPERTY' \
2-u '{api_key}:{secret_key}' \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'event_type=EVENT_NAME' \

1 
2PUT /api/2/taxonomy/event-property/EVENT_PROPERTY HTTP/1.1
3Host: amplitude.com
4Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 24
7 
8event_type=EVENT_NAME

Example: Update an event property

This example updates a the "Completed Task" property for the "Onboard Start" event. It changes the name to "Task Completed", adds a description, and changes the type to "any".

1 
2curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/event-property/Completed Task' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA==' \
4--header 'Content-Type: application/x-www-form-urlencoded' \
5--data-urlencode 'event_type=Onboard Start' \
6--data-urlencode 'description=User completed an onboarding task' \
7--data-urlencode 'new_event_property_value=Task Completed' \
8--data-urlencode 'type=any'

1 
2PUT /api/2/taxonomy/event-property/Completed Task HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA==
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 130
7 
8event_type=Onboard%20Start&description=User%20completed%20an%20onboarding%20task&new_event_property_value=Task%20Completed&type=any

Path parameters

Name	Description
`event-property`	Required. Name of the event property.

Body parameters

Name	Description
`event_type`	Required. Name of the event type to which the event properties belong to.
`description`	Optional. String. The event property's description.
`new_event_property_value`	Optional. String. Available with Govern Add-on. The new name of the event property.
`type`	Optional. String. Available with Govern Add-on. The event property's data type. Acceptable values are `string`, `number`, `boolean`, `enum`, and `any`
`regex`	Optional. String. Available with Govern Add-on. Regular expression, custom regex used for pattern matching or more complex values. For example, property zip code must have pattern `[0-9]{5}`
`enum_values`	Optional. String. Available with Govern Add-on. List of allowed values.
`is_array_type`	Optional. Boolean. Available with Govern Add-on.
`is_required`	Optional. Boolean. Available with Govern Add-on. Marks the property as required.

200 OK response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

409 conflict response

Some failed requests return a 409 Conflict and an error message with more details.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to change the event property description for property \"Completed Task\" for event \"\", but the property is not in schema."
6        }
7    ]
8}

Delete an event property

Delete an event property. Send a DELETE request with the event property as a path parameter and the event type in the request body.

DELETE https://amplitude.com/api/2/taxonomy/event-property/:event-property

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/event-property/EVENT_PROPERTY' \
2--header 'Authorization: Basic {api-key}:{secret-key}' # credentials must be base64 encoded \
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'event_type=EVENT_NAME'

1DELETE /api/2/taxonomy/event-property/EVENT_PROPERTY HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} # credentials must be base64 encoded
4 
5event_type=EVENT_NAME

Example: Delete an event property

This example deletes the event property "Completed Task" from the "Onboarding Start" event.

1 
2curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/event-property/Completed Task' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
4--header 'Content-Type: application/x-www-form-urlencoded' \
5--data-urlencode 'event_type=Onboarding Start'

1 
2DELETE /api/2/taxonomy/event-property/Completed Task HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5Content-Type: application/x-www-form-urlencoded
6Content-Length: 29
7 
8event_type=Onboarding%20Start

Path parameters

Name	Description
`event_property`	Required. The event property name.

Body parameter

Name	Description
`event_type`	Required. Name of the event type to which the event properties belong to.

200 OK response

A successful request returns a 200 OK status and a JSON body.

1{
2    "success": true
3}

User property

User properties reflect traits about the individuals using your product.

Create a user property

Create a user property.

POST https://amplitude.com/api/2/taxonomy/user-property/

1 
2curl --location --request POST 'https://amplitude.com/api/2/taxonomy/user-property' \
3--header 'Authorization: Basic {api-key}:{secret-key}' # credentials must be base64 encoded \
4--data-urlencode 'user_property=USER_PROPERTY' \

1POST /api/2/taxonomy/user-property HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} # credentials must be base64 encoded
4 
5user_property=USER_PROPERTY

Example: Create a user property

This example creates a user property called "User Type", with a description of "Describes whether the user is a Free, Standard, or Premium user.", a type of string and allows the values "Free", "Standard", and "Premium".

1 
2curl --location --request POST 'https://amplitude.com/api/2/taxonomy/user-property' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
4--data-urlencode 'user_property=User Type' \
5--data-urlencode 'description=Describes whether the user is a Free, Standard, or Premium user. ' \
6--data-urlencode 'type=string' \
7--data-urlencode 'enum_values=Free, Standard, Premium'

1 
2POST /api/2/taxonomy/user-property HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5Content-Length: 185
6 
7user_property=User%20Type&description=Describes%20whether%20the%20user%20is%20a%20Free%2C%20Standard%2C%20or%20Premium%20user.%20&type=string&enum_values=Free%2C%20Standard%2C%20Premium

Body parameter

Name	Description
`user_property`	Required. String. Name of the user property type.
`description`	Optional. String. Details to add to the user property type.
`type`	Optional. String. The user property's data type. Acceptable values are `string`, `number`, `boolean`, `enum`, and `any`.
`regex`	Optional. String. Regular expression or custom regex used for pattern matching and more complex values. For example, 'zip code' property must have pattern `[0-9]{5}`.
`enum_values`	Optional. String. List of allowed values, separated by comma. For example: `red, yellow, blue`.
`is_array_type`	Optional. Boolean. Specifies whether the property value is an array.

Response

This request returns either a true or false response.

1{
2    "success" : true
3}

1{
2    "success" : false
3}

Get all user properties

Retrieves all user properties in your account. This call doesn't have any required parameters.

GET https://amplitude.com/api/2/taxonomy/user-property

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/user-property' \
2-u '{api_key}:{secret_key}''

1GET /api/2/taxonomy/user-property HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Response

A successful request returns a 200 OK response and a JSON body with user property details.

 1{
 2    "success": true,
 3    "data": [
 4        {
 5            "user_property": "device_id",
 6            "description": null,
 7            "type": null,
 8            "enum_values": null,
 9            "regex": null,
10            "is_array_type": false
11        }, ...
12        {
13            "user_property": "event_id",
14            "description": null,
15            "type": null,
16            "enum_values": null,
17            "regex": null,
18            "is_array_type": false
19        },
20        {
21            "user_property": "amplitude_id",
22            "description": null,
23            "type": null,
24            "enum_values": null,
25            "regex": null,
26            "is_array_type": false
27        },
28        {
29            "user_property": "location_lat",
30            "description": null,
31            "type": null,
32            "enum_values": null,
33            "regex": null,
34            "is_array_type": false
35        },
36        {
37            "user_property": "location_lng",
38            "description": null,
39            "type": null,
40            "enum_values": null,
41            "regex": null,
42            "is_array_type": false
43        },
44        {
45            "user_property": "server_upload_time",
46            "description": null,
47            "type": null,
48            "enum_values": null,
49            "regex": null,
50            "is_array_type": false
51        },
52        {
53            "user_property": "session_id",
54            "description": null,
55            "type": null,
56            "enum_values": null,
57            "regex": null,
58            "is_array_type": false
59        },
60        {
61            "user_property": "user_id",
62            "description": null,
63            "type": null,
64            "enum_values": null,
65            "regex": null,
66            "is_array_type": false
67        } 
68    ]
69}

Get a user property

Retrieves a single user property, by name.

GET https://amplitude.com/api/2/taxonomy/user-property/:user_property

1curl --location --request GET 'https://amplitude.com/api/2/taxonomy/user-property/USER_PROPERTY' \
2-u '{api_key}:{secret_key}'

1GET /api/2/taxonomy/user-property/USER_PROPERTY HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Get a user property

This example gets the device_id user property.

1 
2curl --location --request GET 'https://amplitude.com/api/2/taxonomy/user-property/device_id' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

1 
2GET /api/2/taxonomy/user-property/device_id HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=

Path parameters

Name	Description
`user_property`	Required. The user property name. Prefix custom user properties with `gp:`

200 OK response

A successful request returns a 200 OK response and a JSON body with user property details.

 1{
 2    "success": true,
 3    "data": {
 4        "user_property": "device_id",
 5        "description": null,
 6        "type": null,
 7        "enum_values": null,
 8        "regex": null,
 9        "is_array_type": false
10    }
11}

404 Bad Request response

A failed request returns a 404 Bad Request status and an error message.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Not found"
6        }
7    ]
8}

The Taxonomy API requires an Enterprise plan account or the Govern add-on enabled. If your subscription doesn't qualify, the call results in a 404 Bad Request response.

Update a user property

Update a user property.

PUT https://amplitude.com/api/2/taxonomy/user-property/:user_property

1curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/user-property/USER_PROPERTY' \
2-u '{api_key}:{secret_key}'
3--header 'Content-Type: application/x-www-form-urlencoded' \
4--data-urlencode 'new_user_property_value=VALUE' \
5--data-urlencode 'description=DESCRIPTION'

1PUT /api/2/taxonomy/user-property/USER_PROPERTY HTTP/1.1
2Host: amplitude.com
3Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded
4Content-Type: application/x-www-form-urlencoded
5Content-Length: 37
6 
7new_user_property_value=VALUE&description=DESCRIPTION

Example: Update a user property

This example updates a user property called "user_type" to be named "subscription_type", adds a description of "The user's subscription type", and changes the property's data type to string. The user property is prefixed with gp: in the path because it's a custom user property.

1 
2curl --location --request PUT 'https://amplitude.com/api/2/taxonomy/user-property/gp:user_type' \
3--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=' \
4--data-urlencode 'new_user_property_value=subscription_type' \
5--data-urlencode 'description=The user'\''s subscription type' \
6--data-urlencode 'type=string'

1 
2PUT /api/2/taxonomy/user-property/gp:user_type HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=
5Content-Length: 100
6 
7new_user_property_value=subscription_type&description=The%20user's%20subscription%20type&type=string

Path parameters

Name	Description
`user_property`	Required. The user property name. Prefix custom user properties with `gp:`

Body parameters

Name	Description
`new_user_property_value`	Optional. String. New name of the user property type.
`description`	Optional. String. Details to add to the user property type.
`type`	Optional. String. The user property's data type. Acceptable values are `string`, `number`, `boolean`, `enum`, and `any`.
`regex`	Optional. String. Regular expression or custom regex used for pattern matching and more complex values. For example, 'zip code' property must have pattern `[0-9]{5}`.
`enum_values`	Optional. String. List of allowed values, separated by comma. For example: `red, yellow, blue`.
`is_array_type`	Optional. Boolean. Specifies whether the property value is an array.

Response

This request returns either a true or false response.

1{
2    "success" : true
3}

1{
2    "success" : false
3}

Delete a user property

Deletes a single user property, by name.

DELETE https://amplitude.com/api/2/taxonomy/user-property/USER_PROPERTY

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/user-property/USER_PROPERTY' \
2-u '{api_key}:{secret_key}'

1 
2DELETE /api/2/taxonomy/user-property/USER_PROPERTY HTTP/1.1
3Host: amplitude.com
4Authorization: Basic {api-key}:{secret-key} #credentials must be base64 encoded

Example: Delete a user property

This example deletes a custom user property "interests". Notice that the user property is prefixed with gp:.

1curl --location --request DELETE 'https://amplitude.com/api/2/taxonomy/user-property/gp:interests' \
2--header 'Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA='

1 
2DELETE /api/2/taxonomy/user-property/gp:interests HTTP/1.1
3Host: amplitude.com
4Authorization: Basic MTIzNDU2NzgwMDoxMjM0NTY3MDA=

Path parameters

Name	Description
`user_property`	Required. The user property name. Prefix custom user properties with `gp:`

200 OK response

A successful request returns a 200 OK response and a JSON message.

1{
2    "success": true
3}

409 conflict response

A failed request returns a 409 Bad Request status and an error message.

1{
2    "success": false,
3    "errors": [
4        {
5            "message": "Attempted to remove a user property, \"sdf\", that is not a planned user property."
6        }
7    ]
8}