LaunchDarkly REST API
LaunchDarkly DocsSign in
HomeAPI ReferenceSDKsContext Plugin
Audit log

Get audit log entry counts

POST
/api/v2/auditlog/counts

Returns aggregate counts of audit log entries per time bucket. Used for dashboard overlays that show flag targeting changes.

Authorization

ApiKey read, write
Authorization<token>

In: header

Scope: read, write

Query Parameters

before?integer

A timestamp filter, expressed as a Unix epoch time in milliseconds. Defaults to now.

Formatint64
after*integer

A timestamp filter, expressed as a Unix epoch time in milliseconds. Required.

Formatint64
buckets?integer

Number of time buckets to divide the range into. Default 50, max 500.

Formatint64
member?string

A member ID that lets you filter counts to changes made by that member. Repeat the parameter to filter by multiple members.

Formatstring
token?string

An access token ID that lets you filter counts to changes made by that token. Repeat the parameter to filter by multiple tokens.

Formatstring

Request Body

application/json

[index: integer]?

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v2/auditlog/counts?after=0" \  -H "Content-Type: application/json" \  -d '[    {      "effect": "allow"    }  ]'
{  "buckets": [    {      "timestamp": 0,      "count": 0    }  ],  "totalCount": 0,  "bucketIntervalMs": 0}

Search audit log entries POST

Search your audit log entries. The query parameters let you restrict the results that return by date ranges, or a full-text search query. The request body lets you restrict the results that return by resource specifiers. LaunchDarkly uses a resource specifier syntax to name resources or collections of resources. To learn more, read [About the resource specifier syntax](https://launchdarkly.com/docs/home/account/role-resources#about-the-resource-specifier-syntax).

Get audit log entry GET

Fetch a detailed audit log entry representation. The detailed representation includes several fields that are not present in the summary representation, including: - `previousVersion`: a JSON representation of the previous version of the entity. - `currentVersion`: a JSON representation of the current version of the entity. - `delta`: the JSON patch body that was used in the request to update the entity. This is only included if the update was made through a [JSON patch](https://launchdarkly.com/docs/api#updates-using-json-patch). It is null when the update was made using [semantic patch](https://launchdarkly.com/docs/api#updates-using-semantic-patch). Because most [flag updates](https://launchdarkly.com/docs/api/feature-flags/patch-feature-flag) are made using semantic patch, this field is rarely returned.