Stream events to Datadog

Introduction

Stream events to Datadog is part of the Paycux platform. This page explains what it does, when to reach for it, and the smallest working setup you can ship.

Everything below applies to both environments. Build and test in staging, then promote the same configuration to production without changing your code — only the API key and client ID differ.

Create a Datadog API key

Every API request is authenticated with a bearer token in the Authorization header. Keys are scoped to a single environment and are shown once at creation — store them in a secret manager, not in source control.

1curl -X GET 'https://api.paycux.com/v1/organizations' \
2  -H 'Authorization: Bearer $PAYCUX_API_KEY'

Configure event streaming in Paycux

Audit log events are append-only and retained for the window configured on the organization. Each event carries an actor, a target, a timestamp and the context the action happened in.

Stream events to a customer's SIEM, or export a date range as JSON or CSV. Exports are generated asynchronously and delivered as a signed URL.

Add the Paycux Datadog dashboard

Add the Paycux Datadog dashboard is handled by Stream events to Datadog rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.

Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.