For the complete documentation index, see llms.txt. For the full documentation snapshot, see llms-full.txt.
Create deployment event
curl --request POST \
--url https://app.launchdarkly.com/api/v2/engineering-insights/deployment-events \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"projectKey": "default",
"environmentKey": "production",
"applicationKey": "billing-service",
"version": "a90a8a2",
"eventType": "started",
"applicationName": "Billing Service",
"applicationKind": "server",
"versionName": "v1.0.0",
"eventTime": "1706701522000",
"eventMetadata": {
"buildSystemVersion": "v1.2.3"
},
"deploymentMetadata": {
"buildNumber": "1234"
}
}
'{
"code": "invalid_request",
"message": "validation failed",
"errors": [
{
"attribute": "projectKey",
"reason": "must be present"
}
]
}Documentation Index
Fetch the complete documentation index at: https://launchdarkly-preview.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The project key
"default"
The environment key
"production"
The application key. This defines the granularity at which you want to view your insights metrics. Typically it is the name of one of the GitHub repositories that you use in this project.
LaunchDarkly automatically creates a new application each time you send a unique application key.
"billing-service"
The application version. You can set the application version to any string that includes only letters, numbers, periods (.), hyphens (-), or underscores (_).
We recommend setting the application version to at least the first seven characters of the SHA or to the tag of the GitHub commit for this deployment.
"a90a8a2"
The event type
started, failed, finished, custom "started"
The application name. This defines how the application is displayed
"Billing Service"
The kind of application. Default: server
server, browser, mobile "server"
The version name. This defines how the version is displayed
"v1.0.0"
The time, in Unix milliseconds, when the event occurred. If not included, the time will default to when the event is processed and stored in LaunchDarkly.
"1706701522000"
A JSON object containing metadata about the event
Show child attributes
{ "buildSystemVersion": "v1.2.3" }A JSON object containing metadata about the deployment
Show child attributes
{ "buildNumber": "1234" }Created
curl --request POST \
--url https://app.launchdarkly.com/api/v2/engineering-insights/deployment-events \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"projectKey": "default",
"environmentKey": "production",
"applicationKey": "billing-service",
"version": "a90a8a2",
"eventType": "started",
"applicationName": "Billing Service",
"applicationKind": "server",
"versionName": "v1.0.0",
"eventTime": "1706701522000",
"eventMetadata": {
"buildSystemVersion": "v1.2.3"
},
"deploymentMetadata": {
"buildNumber": "1234"
}
}
'{
"code": "invalid_request",
"message": "validation failed",
"errors": [
{
"attribute": "projectKey",
"reason": "must be present"
}
]
}