Create deployment event
Create deployment event
Authorization
ApiKey read, writeIn: header
Scope: read, write
Request Body
application/json
The project key
The environment key
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.
The application name. This defines how the application is displayed
The kind of application. Default: server
Value in
- "server"
- "browser"
- "mobile"
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.
The version name. This defines how the version is displayed
The event type
Value in
- "started"
- "failed"
- "finished"
- "custom"
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.
int64A JSON object containing metadata about the event
A JSON object containing metadata about the deployment
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/v2/engineering-insights/deployment-events" \ -H "Content-Type: application/json" \ -d '{ "projectKey": "default", "environmentKey": "production", "applicationKey": "billing-service", "version": "a90a8a2", "eventType": "started" }'Get release frequency chart data GET
Get release frequency chart data. Engineering insights displays release frequency data in the [release frequency metric view](https://launchdarkly.com/docs/home/observability/releases).
List deployments GET
Get a list of deployments ### Expanding the deployment collection response LaunchDarkly supports expanding the deployment collection response to include additional fields. To expand the response, append the `expand` query parameter and include the following: * `pullRequests` includes details on all of the pull requests associated with each deployment * `flagReferences` includes details on all of the references to flags in each deployment For example, use `?expand=pullRequests` to include the `pullRequests` field in the response. By default, this field is **not** included in the response.