RudderStack Docs – APIs

Releases: Data Catalog API

Fri, 31 May 2024 00:00:00 +0000

We have released the Data Catalog API to help you programmatically manage tracking plans, events, and properties in your data catalog.

With the Data Catalog API, you can:

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.

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

Releases: Audit Logs API

Mon, 12 Feb 2024 00:00:00 +0000

RudderStack has launched the Audit Logs API which helps you programmatically access audit logs for running your security audits.

Using the Audit Logs API, you can:

Access all existing audit logs.
Access audit logs generated after the last access, that is, incremental load.
Filter audit logs based on workspaces, date, etc.

For more information on the Audit Logs API, how it works, and its associated endpoints, refer to our docs.

Releases: User Suppression API

Thu, 12 Oct 2023 00:00:00 +0000

We have announced the launch of our User Suppression API. This API makes it easy to honor user consent by suppressing data collection at the source and enabling you to delete user data across multiple cloud tools simultaneously.

Our customers use the User Suppression API to avoid navigating multiple data stores and integrations across multiple regulatory environments to track and manage user consent preferences.

With RudderStack’s User Suppression API, you can:

Suppress data collection across multiple sources for a user or list of users. RudderStack drops the events for these users at the source. After suppression, these events will not be visible in any debuggers or forwarded to any destinations.
Suppress and delete user data across multiple downstream destinations like Amplitude, Braze, Redis, and others. This is helpful in cases where the user requests that their data be deleted.
Maintain centralized, historical records of user opt-outs. This helps data teams keep a record of all user preference updates to ensure they can suppress data coming from new sources.

For more information on the User Suppression API and how it works, read our blog. You can also refer to our docs to learn more about the API and its associated endpoints.