Data Catalog API

Manage your tracking plans, events, and properties in your data catalog programmatically.
Available Plans
  • growth
  • enterprise

  •   23 minute read  

success
The Data Catalog API is a part of RudderStack’s Data Governance toolkit that ensures the quality and integrity of your data in a secure and compliant manner.

You can use the Data Catalog API to:

  • Create and manage your tracking plans programmatically.
  • Add or update events and properties in your data catalog.
  • Create and manage categories for your data catalog events.

Prerequisites

Generate a workspace-level service access token in the RudderStack dashboard.

info
For production use cases, RudderStack recommends using a service access token instead of personal access token.

Authentication

The Data Catalog API uses Bearer authentication in the following format:

Authorization: Bearer <SERVICE_ACCESS_TOKEN>

Base URL

Use the base URL for your API requests depending on your region:

https://api.rudderstack.com/v2

https://api.eu.rudderstack.com/v2

Manage tracking plans

This section covers the API endpoints for creating and managing your tracking plans.

Create tracking plan

POST
/catalog/tracking-plans

Request body

name
Required
String
Tracking plan name.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
description
Optional
String
Tracking plan description.

Example request

POST /v2/catalog/tracking-plans HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 83

{
    "name": "Product Ordered Plan",
    "description": "Tracking plan for users placing an order for the product."
}

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
    "name": "Product Ordered Plan",
    "description": "Tracking plan for users placing an order for the product."
}'

Example response

{
  "id": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
  "name": "Product Ordered Plan",
  "description": "Tracking plan for users placing an order for the product.",
  "version": 1,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "creationType": "BackendAPI",
  "createdAt": "2024-05-22T10:34:03.016Z",
  "updatedAt": "2024-05-22T10:34:03.016Z"
}

Response codes

CodeDescription
200Tracking plan is successfully created. RudderStack also returns an ID for the newly created tracking plan.
400Bad or invalid request.

List all tracking plans

GET
/catalog/tracking-plans

Example request

GET /v2/catalog/tracking-plans HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "trackingPlans": [{
      "id": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
      "name": "Product Ordered Plan",
      "description": "Tracking plan for users placing an order for the product.",
      "version": 1,
      "createdAt": "2024-05-22T13:07:18.617Z",
      "updatedAt": "2024-05-22T13:07:18.617Z",
      "creationType": "BackendAPI",
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e"
    },
    {
      "id": "tp_2rKxjFu6R1qot19aWhTW7W7Ojew",
      "name": "Order Completed Plan",
      "description": "Tracking plan for users completing an order for the product.",
      "version": 4,
      "createdAt": "2024-01-30T15:41:14.446Z",
      "updatedAt": "2024-02-01T08:59:15.095Z",
      "creationType": "Event Audit API",
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e"
    }
  ]
}

Response codes

CodeDescription
200List of all tracking plans in the associated workspace.

Get tracking plan by ID

GET
/catalog/tracking-plans/{trackingPlanId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
version
Optional
String
Tracking plan version. Note that it must be a number.

Example request

GET /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "id": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
  "name": "Product Ordered Plan",
  "description": "Tracking plan for users placing an order for the product.",
  "version": 1,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "creationType": "BackendAPI",
  "createdAt": "2024-05-22T13:07:18.617Z",
  "updatedAt": "2024-05-22T13:07:18.617Z"
}

Response codes

CodeDescription
200Tracking plan is updated successfully.
404Tracking plan not found for the specified ID.

Update tracking plan

PUT
/catalog/tracking-plans/{trackingPlanId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.

Request body

To update the tracking plan, at least one of the following parameters is required:

name
String
Tracking plan name.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
description
String
Tracking plan description.

Example request

PUT /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T HTTP/1.1
Host: api.rudderstack.com
Content-Length: 87

{
    "name": "New Product Ordered Plan",
    "description": "Updated tracking plan for users placing an order for the product."
}

curl --location --request PUT 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T' \
--data '{
    "name": "New Product Ordered Plan",
    "description": "Updated tracking plan for users placing an order for the product."
}'

Example response

{
  "id": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
  "name": "New Product Ordered Plan",
  "description": "Updated tracking plan for users placing an order for the product.",
  "version": 2,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "creationType": "BackendAPI",
  "createdAt": "2024-05-22T10:34:03.016Z",
  "updatedAt": "2024-05-22T10:36:49.252Z"
}

Response codes

CodeDescription
200Tracking plan is updated successfully.
400Bad or invalid request.

Delete tracking plan

danger
Deleted tracking plans cannot be recovered or restored.
DELETE
/catalog/tracking-plans/{trackingPlanId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.

Example request

DELETE /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location --request DELETE 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "name": "New Product Ordered Plan",
  "version": 1,
  "description": "Updated tracking plan for users placing an order for the product.",
  "creationType": "BackendAPI",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "updatedBy": null,
  "createdAt": "2024-05-22T13:41:33.057Z",
  "updatedAt": "2024-05-22T13:41:33.057Z",
  "events": []
}

Response codes

CodeDescription
200Tracking plan is deleted successfully.
400Bad or invalid request.

Manage events in tracking plans

This section covers the API endpoints for upserting and managing events in your tracking plans.

info
The Data Catalog API creates the events and properties in the data catalog only if they do not exist already.

Upsert event to tracking plan

warning

While upserting an event to a tracking plan, make sure the schema of the properties adheres to the advanced rules set for those properties in the data catalog. Otherwise, RudderStack will drop the schema and give the below error:

“Property with name [${prop.name}] and type [${prop.type}] already exists with different advanced keywords.”

If you get this error, you can update the existing catalog property by adding required advanced rules and try again.

PATCH
/catalog/tracking-plans/{trackingPlanId}/events

Path parameters

trackingPlanId
Required
String
Tracking plan ID.

Request body

name
Required
String
Name of the event to be upserted.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
  • For non-track events, the name should be an empty string.
description
Optional
String
Event description.
eventType
Optional
String
Type of event to be upserted.

Note that:
  • Once set, the event type cannot be updated later.
  • Allowed event types are track, identify, group, page, and screen.
categoryId
Optional
String
Category ID of the event. It should be a valid, non-empty string.
rules
Required
Object
JSON schema against which RudderStack validates the event. The event rules cannot be empty.

Note: The keywords defined for a property in the rules parameter are the same as the advanced rules defined for a property in the dashboard.
identitySection
Optional
String
Section from which RudderStack extracts the event properties. See Event structure for tracking plans for more information.

Example request

PATCH /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: ••••••
Content-Length: 955

{
  "name": "Product Viewed",
  "eventType": "track",
  "description": "User viewed a product.",
  "categoryId": null,
  "rules": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "properties": {
        "type": "object",
        "required": [
          "amount"
        ],
        "additionalProperties": false,
        "properties": {
          "amount": {
            "type": [
              "number"
            ]
          },
        }
      }
    }
  }
}

curl --location --request PATCH 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
  "name": "Product Viewed",
  "eventType": "track",
  "description": "User viewed a product.",
  "categoryId": null,
  "rules": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "properties": {
        "type": "object",
        "required": [
          "amount"
        ],
        "additionalProperties": false,
        "properties": {
          "amount": {
            "type": [
              "number"
            ]
          },
        }
      }
    }
  }
}'

Example response

{
  "id": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
  "name": "Product Viewed Plan",
  "version": 3,
  "description": "User viewed a product.",
  "creationType": "BackendAPI",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdAt": "2024-05-22T10:34:03.016Z",
  "updatedAt": "2024-05-22T11:01:24.706Z"
}

Response codes

CodeDescription
200Event is upserted to the tracking plan successfully. The API gives the updated tracking plan information as a response.
400Bad or invalid request.

List all events in tracking plan

GET
/catalog/tracking-plans/{trackingPlanId}/events

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
page
Optional
Number
Events shown from given page. Default page size is 50.

Example request

GET /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "data": [{
    "id": "ev_2gotMKGuOtdDY4XbSdKjkwk4qc2",
    "name": "Product Viewed",
    "description": "User viewed a product.",
    "eventType": "track",
    "categoryId": null,
    "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
    "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
    "updatedBy": null,
    "createdAt": "2024-05-22T11:01:24.706Z",
    "updatedAt": "2024-05-22T11:01:24.706Z",
    "identitySection": "properties",
    "additionalProperties": true,
  }],
  "total": 1,
  "currentPage": 1,
  "pageSize": 50
}

Response codes

CodeDescription
200All the events in a tracking plan are fetched successfully.

Get tracking plan event by ID

GET
/catalog/tracking-plans/{trackingPlanId}/events/{eventId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
eventId
Required
String
Event ID.

Example request

GET /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events/ev_2gotMKGuOtdDY4XbSdKjkwk4qc2 HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events/ev_2gotMKGuOtdDY4XbSdKjkwk4qc2' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "id": "ev_2gotMKGuOtdDY4XbSdKjkwk4qc2",
  "name": "Product Viewed",
  "description": "User viewed a product.",
  "eventType": "track",
  "categoryId": null,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "updatedBy": null,
  "createdAt": "2024-05-22T11:01:24.706Z",
  "updatedAt": "2024-05-22T11:01:24.706Z",
  "identitySection": "properties",
  "rules": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "properties": {
        "type": "object",
        "required": [
          "amount"
        ],
        "additionalProperties": false,
        "properties": {
          "amount": {
            "type": [
              "number"
            ]
          },
        }
      }
    }
  }
}

Response codes

CodeDescription
200Event specified by the ID is fetched successfully.
404Tracking plan event not found for the specified ID.

Delete event from tracking plan

DELETE
/catalog/tracking-plans/{trackingPlanId}/events/{eventId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
eventId
Required
String
Event ID.

Example request

DELETE /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events/ev_2gotMKGuOtdDY4XbSdKjkwk4qc2 HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location --request DELETE 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/events/ev_2gotMKGuOtdDY4XbSdKjkwk4qc2' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Response codes

CodeDescription
204Event is deleted from tracking plan successfully.
400Bad or invalid request.

Manage events in data catalog

This section covers the API endpoints for creating and managing events in your data catalog.

Create new event

POST
/catalog/events

Request body

name
Required
String
Name of the event.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
  • For non-track events, the name should be an empty string.
description
Optional
String
Event description.
eventType
Optional
String
Type of event to be created in the data catalog.

Note that:
  • Once set, the event type cannot be updated later.
  • Allowed event types are track, identify, group, page, and screen.
categoryId
Optional
String
Category ID of the event. It should be a valid, non-empty string.

Example request

POST /v2/catalog/events HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 145

{
  "name": "Product Viewed",
  "description": "User viewed a product",
  "eventType": "track",
  "categoryId": null
}

curl --location 'https://api.rudderstack.com/v2/catalog/events' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
  "name": "Product Viewed",
  "description": "User viewed a product",
  "eventType": "track",
  "categoryId": null
}'

Example response

{
  "name": "Product Viewed",
  "description": "User viewed a product.",
  "eventType": "track",
  "categoryId": null,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "id": "ev_2gqmsfib1Zl6n6QL0mjCi9PJbDS",
  "createdAt": "2024-05-23T03:08:09.972Z",
  "updatedAt": "2024-05-23T03:08:09.972Z"
}

Response codes

CodeDescription
200Event is created successfully.
400Invalid request.

List all events

GET
/catalog/events

Query parameters

page
Optional
String
Page number. The API displays 50 events per page by default.
orderBy
Optional
String

Order the events list by a specific field.

Allowed fields are name, createdAt, updatedAt. For example, name:asc.

Example request

GET /v2/catalog/events?page=1&orderBy=name:desc HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/events?page=1&orderBy=name%3Adesc' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "data": [{
      "id": "ev_2g60ZQeit5D54rBHUUh0oK3IxzH",
      "name": "Order Placed",
      "description": "User placed an order.",
      "eventType": "track",
      "categoryId": null,
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "updatedBy": null,
      "createdAt": "2024-05-06T13:39:34.294Z",
      "updatedAt": "2024-05-06T13:39:34.294Z"
    },
    ....

    {
      "id": "ev_2dJfRK8t0hOmmAaCTc0VvMB36e1",
      "name": "Product Added to Cart",
      "description": "User added product to cart.",
      "eventType": "track",
      "categoryId": null,
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "updatedBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "createdAt": "2024-03-06T13:18:12.044Z",
      "updatedAt": "2024-05-13T11:39:40.115Z"
    },
  ],
  "total": 3563,
  "currentPage": 1,
  "pageSize": 50
}

Response codes

CodeDescription
200All events in the data catalog are retrieved successfully.

Get event by ID

GET
/catalog/events/{eventId}

Path parameters

eventId
Required
String
The event ID.

Example request

GET /v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "id": "ev_2dJfRQIZLrBhqdLoLoxywHpicLp",
  "name": "Product Viewed",
  "description": "User viewed a product.",
  "eventType": "track",
  "categoryId": null,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
  "updatedBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "createdAt": "2024-03-06T13:18:12.044Z",
  "updatedAt": "2024-05-22T14:57:50.265Z",
  "category": null
}

Response codes

CodeDescription
200All events in the data catalog are retrieved successfully.
404Event not found for the specified event ID.

Update event

PUT
/catalog/events/{eventId}

Path parameters

eventId
Required
String
The event ID.

Request body

To update an event in the data catalog, at least one of the following parameters is required:

name
String
Name of the event.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
  • For non-track events, the name should be an empty string.
description
String
Event description.
categoryId
String
Category ID of the event. It should be a valid, non-empty string.

Example request

PUT /v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 98

{
  "name": "Product Viewed Again",
  "description": "User viewed a product again.",
  "categoryId": null
}

curl --location --request PUT 'https://api.rudderstack.com/v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
  "name": "Product Viewed Again",
  "description": "User viewed a product again.",
  "categoryId": null
}'

Example response

{
  "name": "Product Viewed Again",
  "description": "User revisited a product on the website.",
  "categoryId": null
}

Response codes

CodeDescription
200Event is updated successfully.
404Event not found for the specified event ID.

Delete event

warning
You cannot delete an event that is connected to a tracking plan. Use the Delete event from tracking plan API to disconnect the event and then try deleting it.
DELETE
/catalog/events/{eventId}

Path parameters

eventId
Required
String
Event ID.

Example request

DELETE /v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location --request DELETE 'https://api.rudderstack.com/v2/catalog/events/ev_2dJfRQIZLrBhqdLoLoxywHpicLp' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "name": "Product Purchased",
  "description": "User purchased a product on the website.",
  "eventType": "track",
  "categoryId": null,
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "updatedBy": null,
  "createdAt": "2024-05-22T14:59:14.287Z",
  "updatedAt": "2024-05-22T14:59:14.287Z"
}

Response codes

CodeDescription
200Event is deleted from the catalog successfully.
404Event not found for the specified event ID.

Manage properties in data catalog

This section covers the API endpoints for creating and managing properties in your data catalog.

Create new property

POST
/catalog/properties

Request body

name
Required
String
Property name.

Note that:
  • The name must be of at least one character and should start with a letter.
  • It must contain only letters, numbers, underscores, and spaces.
description
Optional
String
Property description.
type
Required
String
Data type of the property.

Note that:
  • The data type must be either string, integer, number, object, array, boolean, null, or multi data type.
  • If not explicitly set, RudderStack allows all the above data types for the property, by default.
propConfig
Optional
Object
Advanced rules for the property. See JSON Schema for the complete list of supported keywords.
info

RudderStack supports multi data type for the type parameter. An example is shown:

{
  "type": ["string", "integer", "boolean", "null"]
}

Example request

POST /v2/catalog/properties HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 117

{
  "name": "amount",
  "description": "Amount for the product",
  "type": "number",
  "propConfig": {
      "multipleOf": 2
  },
}

curl --location 'https://api.rudderstack.com/v2/catalog/properties' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
  "name": "amount",
  "description": "Amount for the product",
  "type": "number",
  "propConfig": {
      "multipleOf": 2
  },
}'

Example response

{
  "name": "amount",
  "description": "Amount for the product",
  "type": "number",
  "propConfig": {
      "multipleOf": 2
  },
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "id": "prop_2gqpkKg1GtHWKR8JtNChoKsqhIK",
  "createdAt": "2024-05-23T03:31:43.297Z",
  "updatedAt": "2024-05-23T03:31:43.297Z"
}

Response codes

CodeDescription
200Property is created successfully.
400Invalid request.

List all properties

GET
/catalog/properties

Path parameters

page
Optional
Number
Page number.
orderBy
Optional
String

Order the properties list by a specific field.

Allowed fields are name, createdAt, updatedAt. For example, name:asc.

Example request

GET /v2/catalog/properties?page=1&orderBy=name:asc HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/properties?page=1&orderBy=name%3Aasc' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "data": [{
      "id": "prop_2dJfRQ233WrPRpWBPqbF4PuiMc0",
      "name": "affiliation",
      "description": "Product affiliation",
      "type": "string",
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "updatedBy": null,
      "createdAt": "2024-03-06T13:18:12.044Z",
      "updatedAt": "2024-03-06T13:18:12.044Z"
    },

    ...

    {
      "id": "prop_2bfXbQuinn4298XzqlyxmktRAX9d",
      "name": "Email",
      "description": "User's email",
      "type": "string",
      "propConfig": {},
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "updatedBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "createdAt": "2024-01-30T09:32:57.983Z",
      "updatedAt": "2024-01-30T09:33:18.885Z"
    }
  ],
  "total": 450,
  "currentPage": 1,
  "pageSize": 50
}

Response codes

CodeDescription
200All properties in the data catalog are retrieved successfully.

Get property by ID

GET
/catalog/properties/{propertyId}

Path parameters

propertyId
Required
String
Property ID.

Example request

GET /v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "id": "prop_2bfXbQuinn4298XzqlyxmktRAX9d",
  "name": "Email",
  "description": "User's email",
  "type": "string",
  "propConfig": {},
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
  "updatedBy": "1zirfVbEQN0zIImR235a1JivVYU",
  "createdAt": "2024-01-30T09:32:57.983Z",
  "updatedAt": "2024-01-30T09:33:18.885Z"
}

Response codes

CodeDescription
200All properties in the data catalog are retrieved successfully.
404Property not found for the specified event ID.

Update property

PUT
/catalog/properties/{propertyId}

Path parameters

propertyId
Required
String
Property ID.

Request body

To update the event property in the data catalog, at least one of the following parameters is required:

name
String
Property name.

Note that:
  • The name must be of at least one character and should start with a letter.
  • It must contain only letters, numbers, underscores, and spaces.
description
String
Property description.
type
String
Data type of the property.

Note that:
  • The data type must be either string, integer, number, object, array, boolean, null, or multi data type.
  • If not explicitly set, RudderStack allows all the above data types for the property, by default.
propConfig
Optional
Object
Advanced rules for the property. See JSON Schema for the complete list of supported keywords.
info

RudderStack supports multi data type for the type parameter. An example is shown:

{
  "type": ["string", "integer", "boolean", "null"]
}

Example request

PUT /v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 45

{
  "description": "User's email address",
  "propConfig": {
      "format": "email"
  }
}

curl --location --request PUT 'https://api.rudderstack.com/v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
  "description": "User's email address",
  "propConfig": {
      "format": "email"
  }
}'

Example response

{
  "id": "prop_2bfXbQuinn4298XzqlyxmktRAX9d",
  "name": "Email",
  "description": "User's email address",
  "propConfig": {
      "format": "email"
  },
  "type": "number",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
  "updatedBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "createdAt": "2024-01-30T09:32:57.983Z",
  "updatedAt": "2024-05-23T03:41:10.715Z"
}

Response codes

CodeDescription
200Property is updated successfully.
400Property not found for the specified event ID.

Delete property

DELETE
/catalog/properties/{propertyId}

Path parameters

propertyId
Required
String
Property ID.

Example request

DELETE /v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location --request DELETE 'https://api.rudderstack.com/v2/catalog/properties/prop_2bfXbQuinn4298XzqlyxmktRAX9d' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "name": "Email",
  "description": "User's email address",
  "type": "number",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
  "updatedBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "createdAt": "2024-01-30T09:32:57.983Z",
  "updatedAt": "2024-05-23T03:41:10.715Z"
}

Response codes

CodeDescription
200Property is deleted from the catalog successfully.
400Property not found for the specified event ID.

Manage categories in data catalog

This section covers the API endpoints for creating and managing categories in your data catalog. Go to Govern > Data Catalog > Events tab in your RudderStack dashboard to view the categories and associate them to your events.

Data catalog categories

Create new category

POST
/catalog/categories

Request body

name
Required
String
Category name.

Note that:
  • The name must be between 3 and 65 characters and should start with a letter.
  • It must contain only letters, numbers, underscores, commas, spaces, dashes, and dots.
description
Optional
String
Category description.

Example request

POST /v2/catalog/categories HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY
Content-Length: 70

{
  "name": "Onboarding",
  "description": "Customer onboarding"
}

curl --location 'https://api.rudderstack.com/v2/catalog/categories' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY' \
--data '{
  "name": "Onboarding",
  "description": "Customer onboarding"
}'

Example response

{
  "name": "Onboarding",
  "description": "Customer onboarding",
  "icon": "star",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "id": "cat_2gqs1Yzy1Vpeeewm69meqc6d8zH",
  "createdAt": "2024-05-23T03:50:27.416Z",
  "updatedAt": "2024-05-23T03:50:27.416Z"
}

Response codes

CodeDescription
200Category is created successfully.
400Invalid Request.

List all categories

GET
/catalog/categories

Path parameters

page
Optional
String
Page number.
orderBy
Optional
String

Order the categories list by a specific field.

Allowed fields are name, createdAt, updatedAt. For example, name:asc.

Example request

GET /v2/catalog/categories HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/categories' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "data": [{
      "id": "cat_2gqs1Yzy1Vpeeewm69meqc6d8zH",
      "name": "Onboarding",
      "description": "Customer onboarding",
      "icon": "star",
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
      "updatedBy": null,
      "createdAt": "2024-05-23T03:50:27.416Z",
      "updatedAt": "2024-05-23T03:50:27.416Z"
    },

    ...

    {
      "id": "cat_4gs21Yzy1Vpw1m69meqc6d8zH",
      "name": "Product Experience",
      "description": "Enhance overall product and customer experience",
      "icon": "star",
      "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
      "createdBy": "1zirfVbEQN0zIImR235a1JivVYU",
      "updatedBy": null,
      "createdAt": "2024-04-30T14:30:30.254Z",
      "updatedAt": "2024-04-30T14:30:30.254Z"
    }
  ],
  "total": 10,
  "currentPage": 1,
  "pageSize": 1000
}

Response codes

CodeDescription
200All the categories in a tracking plan are fetched successfully.

Get category by ID

GET
/catalog/categories/{categoryId}

Path parameters

categoryId
Required
String
Category ID.

Example request

GET /v2/catalog/categories/cat_2gqs1Yzy1Vpeeewm69meqc6d8zH HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location 'https://api.rudderstack.com/v2/catalog/categories/cat_2gqs1Yzy1Vpeeewm69meqc6d8zH' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "id": "cat_2gqs1Yzy1Vpeeewm69meqc6d8zH",
  "name": "Onboarding",
  "description": "Customer onboarding",
  "icon": "star",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "updatedBy": null,
  "createdAt": "2024-05-23T03:50:27.416Z",
  "updatedAt": "2024-05-23T03:50:27.416Z"
}

Response codes

CodeDescription
200All categories in the data catalog are retrieved successfully.
404Category not found for the specified ID.

Delete category

DELETE
/catalog/categories/{categoryId}

Path parameters

categoryId
Required
String
Category ID.

Example request

DELETE /v2/catalog/categories/cat_2gqs1Yzy1Vpeeewm69meqc6d8zH HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY

curl --location --request DELETE 'https://api.rudderstack.com/v2/catalog/categories/cat_2gqs1Yzy1Vpeeewm69meqc6d8zH' \
--header 'Authorization: Bearer 2glZLfSinoRWdkMqsZYPj48X8dY'

Example response

{
  "name": "Onboarding",
  "description": "Customer onboarding",
  "icon": "star",
  "workspaceId": "1hitizAoFT91DD6rfFhBjiTex3e",
  "createdBy": "2KDKycoVHAOLttVvzBiqw12O3Hr",
  "updatedBy": null,
  "createdAt": "2024-05-23T03:50:27.416Z",
  "updatedAt": "2024-05-23T03:50:27.416Z"
}

Response codes

CodeDescription
200Category is deleted from the catalog successfully.
400Category not found for the specified event ID.

Manage tracking plan-source connections

This section covers the API endpoints for managing the connections between your tracking plans and sources.

Add new connection

POST
/catalog/tracking-plans/{trackingPlanId}/sources/{sourceId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
sourceId
Required
String
Source ID.

Request body

warning
The request body must not be empty. Otherwise, you will encounter an error.
config
Required
Object
Tracking plan configuration for the source. See Config object structure below for more information.

Config object structure

The config object provided in the request body contains the source-specific tracking plan settings for validating the individual events. A sample object is shown below:

{
  "config": {
    "page": {
      "unplannedProperties": "forward",  // or "drop"
      "anyOtherViolation": "forward",  // or "drop"
      "propagateValidationErrors": "true",  // or "false"
    },
    "group": {
      "unplannedProperties": "forward",
      "anyOtherViolation": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "allowUnplannedEvents": "true",
      "unplannedProperties": "forward",
      "anyOtherViolation": "forward",
      "propagateValidationErrors": "true",  // or "false"
    },
    "global": {
      "allowUnplannedEvents": "true",
      "unplannedProperties": "forward",
      "anyOtherViolation": "forward",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "unplannedProperties": "forward",
      "anyOtherViolation": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "unplannedProperties": "forward",
      "anyOtherViolation": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

The event-level settings that you can define within the config object are described below. See Source-specific tracking plan settings for more information:

Field
Description
allowUnplannedEventsApplicable for track object only.

Boolean that determines if RudderStack should drop all events that do not match the predefined event names in the tracking plan.
unplannedPropertiesAcceptable values are forward and drop.

Determines if RudderStack should forward or drop events that contain properties not matching the list of predefined properties for the specific event.
anyOtherViolationAcceptable values are forward and drop.

Determines if RudderStack should forward or drop events with any other violations that include Type Mismatch, Required Fields Missing, and others outlined in the Violation types section.
propagateValidationErrorsBoolean that determines if RudderStack should capture the validation errors in the event’s context object and send them downstream (user transformations and destinations).
info

Note that:

  • You need not provide the tracking plan settings for all events. For example, you can include only the track and global objects within config. However, note that you must not provide a blank event object. If included, you must define at least one setting for that event.
  • RudderStack uses the default settings for the events that you do not specify explicitly and validates them accordingly.

Example request

POST /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/sources/2nk0qVvmxE79uIwsKebgVH4iNTR HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2rFATUz94Gt2GCgTtnWwNY1EHTO
Content-Length: 1125

{
  "config": {
    "page": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "group": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "true",
      "propagateValidationErrors": "true"
    },
    "global": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "false",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

curl --location 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/sources/2nk0qVvmxE79uIwsKebgVH4iNTR' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2rFATUz94Gt2GCgTtnWwNY1EHTO' \
--data '{
    "config": {
        "page": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "group": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "track": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "allowUnplannedEvents": "true",
            "propagateValidationErrors": "true"
        },
        "global": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "allowUnplannedEvents": "false",
            "propagateValidationErrors": "true"
        },
        "screen": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "identify": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        }
    }
}'

Example response

{
  "sourceId": "2nk0qVvmxE79uIwsKebgVH4iNTR",
  "trackingPlanId": "tp_5gopz6tfKxAjpS4TjuqVIeTdm7T",
  "config": {
    "page": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "group": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "true",
      "propagateValidationErrors": "true"
    },
    "global": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "false",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

Response codes

CodeDescription
200Connection created successfully.
400
  • Invalid Request
  • Empty or incorrect config object.
  • Source already connected to tracking plan.

Update tracking plan configuration

PUT
/catalog/tracking-plans/{trackingPlanId}/sources/{sourceId}

Path parameters

trackingPlanId
Required
String
Tracking plan ID.
sourceId
Required
String
Source ID.

Request body

warning
The request body must not be empty. Otherwise, you will encounter an error.
config
Required
Object
Tracking plan configuration for the source. See Config object structure below for more information.

Config object structure

The config object provided in the request body contains the source-specific tracking plan settings for validating the individual events. A sample object is shown below:

{
  "config": {
    "page": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "group": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "true",
      "propagateValidationErrors": "true"
    },
    "global": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "false",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

The event-level settings that you can define within the config object are described below. See Source-specific tracking plan settings for more information:

Field
Description
allowUnplannedEventsApplicable for track object only.

Boolean that determines if RudderStack should drop all events that do not match the predefined event names in the tracking plan.
unplannedPropertiesAcceptable values are forward and drop.

Determines if RudderStack should forward or drop events that contain properties not matching the list of predefined properties for the specific event.
anyOtherViolationAcceptable values are forward and drop.

Determines if RudderStack should forward or drop events with any other violations that include Type Mismatch, Required Fields Missing, and others outlined in the Violation types section.
propagateValidationErrorsBoolean that determines if RudderStack should capture the validation errors in the event’s context object and send them downstream (user transformations and destinations).
info

Note that:

  • You need not provide the tracking plan settings for all events. For example, you can include only the track and global objects within config. However, note that you must not provide a blank event object. If included, you must define at least one setting for that event.
  • RudderStack uses the default settings for the events that you do not specify explicitly and validates them accordingly.

Example request

PUT /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/sources/2nk0qVvmxE79uIwsKebgVH4iNTR HTTP/1.1
Host: api.rudderstack.com
Content-Type: application/json
Authorization: Bearer 2rFATUz94Gt2GCgTtnWwNY1EHTO
Content-Length: 1125

{
  "config": {
    "page": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "group": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "true",
      "propagateValidationErrors": "true"
    },
    "global": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "false",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

curl --location --request PUT 'https://api.rudderstack.com/v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/sources/2nk0qVvmxE79uIwsKebgVH4iNTR' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer 2rFATUz94Gt2GCgTtnWwNY1EHTO' \
--data '{
    "config": {
        "page": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "group": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "track": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "allowUnplannedEvents": "true",
            "propagateValidationErrors": "true"
        },
        "global": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "allowUnplannedEvents": "false",
            "propagateValidationErrors": "true"
        },
        "screen": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        },
        "identify": {
            "anyOtherViolation": "forward",
            "unplannedProperties": "forward",
            "propagateValidationErrors": "true"
        }
    }
}'

Example response

{
  "config": {
    "page": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "group": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "track": {
      "anyOtherViolation": "drop",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "true",
      "propagateValidationErrors": "true"
    },
    "global": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "allowUnplannedEvents": "false",
      "propagateValidationErrors": "true"
    },
    "screen": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    },
    "identify": {
      "anyOtherViolation": "forward",
      "unplannedProperties": "forward",
      "propagateValidationErrors": "true"
    }
  }
}

Response codes

CodeDescription
200Configuration updated successfully.
400
  • Invalid Request
  • Empty or incorrect config object.
  • Source is not connected to tracking plan.

List all sources connected to tracking plan

GET
/catalog/tracking-plans/{trackingPlanId}/sources

Path parameters

trackingPlanId
Required
String
Tracking plan ID.

Example request

GET /v2/catalog/tracking-plans/tp_5gopz6tfKxAjpS4TjuqVIeTdm7T/sources HTTP/1.1
Host: api.rudderstack.com
Authorization: Bearer 2rKxyWcnm9n4zh2h7VjxLGSNzm7

<