launchdarkly-api

14.0.0 • Public • Published

This repository contains a client library for LaunchDarkly's REST API. This client was automatically generated from our OpenAPI specification using a code generation library. View our sample code for example usage.

This REST API is for custom integrations, data export, or automating your feature flag workflows. DO NOT use this client library to include feature flags in your web or mobile application. To integrate feature flags with your application, read the SDK documentation.

This client library is only compatible with the latest version of our REST API, version 20220603. Previous versions of this client library, prior to version 10.0.0, are only compatible with earlier versions of our REST API. When you create an access token, you can set the REST API version associated with the token. By default, API requests you send using the token will use the specified API version. To learn more, read Versioning.

launchdarkly-api

LaunchDarklyApi - JavaScript client for launchdarkly-api

Overview

Authentication

All REST API resources are authenticated with either personal or service access tokens, or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens on your Account settings page.

LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are used by our server-side SDKs, mobile SDKs, and JavaScript-based SDKs, respectively. These keys cannot be used to access our REST API. These keys are environment-specific, and can only perform read-only operations such as fetching feature flag settings.

Auth mechanism Allowed resources Use cases
Personal or service access tokens Can be customized on a per-token basis Building scripts, custom integrations, data export.
SDK keys Can only access read-only resources specific to server-side SDKs. Restricted to a single environment. Server-side SDKs
Mobile keys Can only access read-only resources specific to mobile SDKs, and only for flags marked available to mobile keys. Restricted to a single environment. Mobile SDKs
Client-side ID Can only access read-only resources specific to JavaScript-based client-side SDKs, and only for flags marked available to client-side. Restricted to a single environment. Client-side JavaScript

Keep your access tokens and SDK keys private

Access tokens should never be exposed in untrusted contexts. Never put an access token in client-side JavaScript, or embed it in a mobile application. LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally expose an access token or SDK key, you can reset it from your Account settings page.

The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript.

Authentication using request header

The preferred way to authenticate with the API is by adding an Authorization header containing your access token to your requests. The value of the Authorization header must be your access token.

Manage personal access tokens from the Account settings page.

Authentication using session cookie

For testing purposes, you can make API calls directly from your web browser. If you are logged in to the LaunchDarkly application, the API will use your existing session to authenticate calls.

If you have a role other than Admin, or have a custom role defined, you may not have permission to perform some API calls. You will receive a 401 response code in that case.

Modifying the Origin header causes an error

LaunchDarkly validates that the Origin header for any API request authenticated by a session cookie matches the expected Origin header. The expected Origin header is https://app.launchdarkly.com.

If the Origin header does not match what's expected, LaunchDarkly returns an error. This error can prevent the LaunchDarkly app from working correctly.

Any browser extension that intentionally changes the Origin header can cause this problem. For example, the Allow-Control-Allow-Origin: * Chrome extension changes the Origin header to http://evil.com and causes the app to fail.

To prevent this error, do not modify your Origin header.

LaunchDarkly does not require origin matching when authenticating with an access token, so this issue does not affect normal API usage.

Representations

All resources expect and return JSON response bodies. Error responses also send a JSON body. To learn more about the error format of the API, read Errors.

In practice this means that you always get a response with a Content-Type header set to application/json.

In addition, request bodies for PATCH, POST, and PUT requests must be encoded as JSON with a Content-Type header set to application/json.

Summary and detailed representations

When you fetch a list of resources, the response includes only the most important attributes of each resource. This is a summary representation of the resource. When you fetch an individual resource, such as a single feature flag, you receive a detailed representation of the resource.

The best way to find a detailed representation is to follow links. Every summary representation includes a link to its detailed representation.

Expanding responses

Sometimes the detailed representation of a resource does not include all of the attributes of the resource by default. If this is the case, the request method will clearly document this and describe which attributes you can include in an expanded response.

To include the additional attributes, append the expand request parameter to your request and add a comma-separated list of the attributes to include. For example, when you append ?expand=members,roles to the Get team endpoint, the expanded response includes both of these attributes.

Links and addressability

The best way to navigate the API is by following links. These are attributes in representations that link to other resources. The API always uses the same format for links:

  • Links to other resources within the API are encapsulated in a _links object
  • If the resource has a corresponding link to HTML content on the site, it is stored in a special _site link

Each link has two attributes:

  • An href, which contains the URL
  • A type, which describes the content type

For example, a feature resource might return the following:

{
  \"_links\": {
    \"parent\": {
      \"href\": \"/api/features\",
      \"type\": \"application/json\"
    },
    \"self\": {
      \"href\": \"/api/features/sort.order\",
      \"type\": \"application/json\"
    }
  },
  \"_site\": {
    \"href\": \"/features/sort.order\",
    \"type\": \"text/html\"
  }
}

From this, you can navigate to the parent collection of features by following the parent link, or navigate to the site page for the feature by following the _site link.

Collections are always represented as a JSON object with an items attribute containing an array of representations. Like all other representations, collections have _links defined at the top level.

Paginated collections include first, last, next, and prev links containing a URL with the respective set of elements in the collection.

Updates

Resources that accept partial updates use the PATCH verb. Most resources support the JSON patch format. Some resources also support the JSON merge patch format, and some resources support the semantic patch format, which is a way to specify the modifications to perform as a set of executable instructions. Each resource supports optional comments that you can submit with updates. Comments appear in outgoing webhooks, the audit log, and other integrations.

When a resource supports both JSON patch and semantic patch, we document both in the request method. However, the specific request body fields and descriptions included in our documentation only match one type of patch or the other.

Updates using JSON patch

JSON patch is a way to specify the modifications to perform on a resource. JSON patch uses paths and a limited set of operations to describe how to transform the current state of the resource into a new state. JSON patch documents are always arrays, where each element contains an operation, a path to the field to update, and the new value.

For example, in this feature flag representation:

{
    \"name\": \"New recommendations engine\",
    \"key\": \"engine.enable\",
    \"description\": \"This is the description\",
    ...
}

You can change the feature flag's description with the following patch document:

[{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"This is the new description\" }]

You can specify multiple modifications to perform in a single request. You can also test that certain preconditions are met before applying the patch:

[
  { \"op\": \"test\", \"path\": \"/version\", \"value\": 10 },
  { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }
]

The above patch request tests whether the feature flag's version is 10, and if so, changes the feature flag's description.

Attributes that are not editable, such as a resource's _links, have names that start with an underscore.

Updates using JSON merge patch

JSON merge patch is another format for specifying the modifications to perform on a resource. JSON merge patch is less expressive than JSON patch. However, in many cases it is simpler to construct a merge patch document. For example, you can change a feature flag's description with the following merge patch document:

{
  \"description\": \"New flag description\"
}

Updates using semantic patch

Some resources support the semantic patch format. A semantic patch is a way to specify the modifications to perform on a resource as a set of executable instructions.

Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, you can define semantic patch instructions independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date.

To make a semantic patch request, you must append domain-model=launchdarkly.semanticpatch to your Content-Type header.

Here's how:

Content-Type: application/json; domain-model=launchdarkly.semanticpatch

If you call a semantic patch resource without this header, you will receive a 400 response because your semantic patch will be interpreted as a JSON patch.

The body of a semantic patch request takes the following properties:

  • comment (string): (Optional) A description of the update.
  • environmentKey (string): (Required for some resources only) The environment key.
  • instructions (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a kind property that indicates the instruction. If the instruction requires parameters, you must include those parameters as additional fields in the object. The documentation for each resource that supports semantic patch includes the available instructions and any additional parameters.

For example:

{
  \"comment\": \"optional comment\",
  \"instructions\": [ {\"kind\": \"turnFlagOn\"} ]
}

If any instruction in the patch encounters an error, the endpoint returns an error and will not change the resource. In general, each instruction silently does nothing if the resource is already in the state you request.

Updates with comments

You can submit optional comments with PATCH changes.

To submit a comment along with a JSON patch document, use the following format:

{
  \"comment\": \"This is a comment string\",
  \"patch\": [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }]
}

To submit a comment along with a JSON merge patch document, use the following format:

{
  \"comment\": \"This is a comment string\",
  \"merge\": { \"description\": \"New flag description\" }
}

To submit a comment along with a semantic patch, use the following format:

{
  \"comment\": \"This is a comment string\",
  \"instructions\": [ {\"kind\": \"turnFlagOn\"} ]
}

Errors

The API always returns errors in a common format. Here's an example:

{
  \"code\": \"invalid_request\",
  \"message\": \"A feature with that key already exists\",
  \"id\": \"30ce6058-87da-11e4-b116-123b93f75cba\"
}

The code indicates the general class of error. The message is a human-readable explanation of what went wrong. The id is a unique identifier. Use it when you're working with LaunchDarkly Support to debug a problem with a specific API call.

HTTP status error response codes

Code Definition Description Possible Solution
400 Invalid request The request cannot be understood. Ensure JSON syntax in request body is correct.
401 Invalid access token Requestor is unauthorized or does not have permission for this API call. Ensure your API access token is valid and has the appropriate permissions.
403 Forbidden Requestor does not have access to this resource. Ensure that the account member or access token has proper permissions set.
404 Invalid resource identifier The requested resource is not valid. Ensure that the resource is correctly identified by ID or key.
405 Method not allowed The request method is not allowed on this resource. Ensure that the HTTP verb is correct.
409 Conflict The API request can not be completed because it conflicts with a concurrent API request. Retry your request.
422 Unprocessable entity The API request can not be completed because the update description can not be understood. Ensure that the request body is correct for the type of patch you are using, either JSON patch or semantic patch.
429 Too many requests Read Rate limiting. Wait and try again later.

CORS

The LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. If an Origin header is given in a request, it will be echoed as an explicitly allowed origin. Otherwise the request returns a wildcard, Access-Control-Allow-Origin: *. For more information on CORS, read the CORS W3C Recommendation. Example CORS headers might look like:

Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization
Access-Control-Allow-Methods: OPTIONS, GET, DELETE, PATCH
Access-Control-Allow-Origin: *
Access-Control-Max-Age: 300

You can make authenticated CORS calls just as you would make same-origin calls, using either token or session-based authentication. If you are using session authentication, you should set the withCredentials property for your xhr request to true. You should never expose your access tokens to untrusted entities.

Rate limiting

We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs return a 429 status code. Calls to our APIs include headers indicating the current rate limit status. The specific headers returned depend on the API route being called. The limits differ based on the route, authentication mechanism, and other factors. Routes that are not rate limited may not contain any of the headers described below.

Rate limiting and SDKs

LaunchDarkly SDKs are never rate limited and do not use the API endpoints defined here. LaunchDarkly uses a different set of approaches, including streaming/server-sent events and a global CDN, to ensure availability to the routes used by LaunchDarkly SDKs.

Global rate limits

Authenticated requests are subject to a global limit. This is the maximum number of calls that your account can make to the API per ten seconds. All service and personal access tokens on the account share this limit, so exceeding the limit with one access token will impact other tokens. Calls that are subject to global rate limits may return the headers below:

Header name Description
X-Ratelimit-Global-Remaining The maximum number of requests the account is permitted to make per ten seconds.
X-Ratelimit-Reset The time at which the current rate limit window resets in epoch milliseconds.

We do not publicly document the specific number of calls that can be made globally. This limit may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limit.

Route-level rate limits

Some authenticated routes have custom rate limits. These also reset every ten seconds. Any service or personal access tokens hitting the same route share this limit, so exceeding the limit with one access token may impact other tokens. Calls that are subject to route-level rate limits return the headers below:

Header name Description
X-Ratelimit-Route-Remaining The maximum number of requests to the current route the account is permitted to make per ten seconds.
X-Ratelimit-Reset The time at which the current rate limit window resets in epoch milliseconds.

A route represents a specific URL pattern and verb. For example, the Delete environment endpoint is considered a single route, and each call to delete an environment counts against your route-level rate limit for that route.

We do not publicly document the specific number of calls that an account can make to each endpoint per ten seconds. These limits may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limits.

IP-based rate limiting

We also employ IP-based rate limiting on some API routes. If you hit an IP-based rate limit, your API response will include a Retry-After header indicating how long to wait before re-trying the call. Clients must wait at least Retry-After seconds before making additional calls to our API, and should employ jitter and backoff strategies to avoid triggering rate limits again.

OpenAPI (Swagger) and client libraries

We have a complete OpenAPI (Swagger) specification for our API.

We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit the collection of client libraries on GitHub. You can also use this specification to generate client libraries to interact with our REST API in your language of choice.

Our OpenAPI specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to explore our APIs.

Method overriding

Some firewalls and HTTP clients restrict the use of verbs other than GET and POST. In those environments, our API endpoints that use DELETE, PATCH, and PUT verbs are inaccessible.

To avoid this issue, our API supports the X-HTTP-Method-Override header, allowing clients to "tunnel" DELETE, PATCH, and PUT requests using a POST request.

For example, to call a PATCH endpoint using a POST request, you can include X-HTTP-Method-Override:PATCH as a header.

Beta resources

We sometimes release new API resources in beta status before we release them with general availability.

Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible.

We try to promote resources into general availability as quickly as possible. This happens after sufficient testing and when we're satisfied that we no longer need to make backwards-incompatible changes.

We mark beta resources with a "Beta" callout in our documentation, pictured below:

This feature is in beta

To use this feature, pass in a header including the LD-API-Version key with value set to beta. Use this header with each call. To learn more, read Beta resources.

Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible.

Using beta resources

To use a beta resource, you must include a header in the request. If you call a beta resource without this header, you receive a 403 response.

Use this header:

LD-API-Version: beta

Federal environments

The version of LaunchDarkly that is available on domains controlled by the United States government is different from the version of LaunchDarkly available to the general public. If you are an employee or contractor for a United States federal agency and use LaunchDarkly in your work, you likely use the federal instance of LaunchDarkly.

If you are working in the federal instance of LaunchDarkly, the base URI for each request is https://app.launchdarkly.us. In the "Try it" sandbox for each request, click the request path to view the complete resource path for the federal environment.

To learn more, read LaunchDarkly in federal environments.

Versioning

We try hard to keep our REST API backwards compatible, but we occasionally have to make backwards-incompatible changes in the process of shipping new features. These breaking changes can cause unexpected behavior if you don't prepare for them accordingly.

Updates to our REST API include support for the latest features in LaunchDarkly. We also release a new version of our REST API every time we make a breaking change. We provide simultaneous support for multiple API versions so you can migrate from your current API version to a new version at your own pace.

Setting the API version per request

You can set the API version on a specific request by sending an LD-API-Version header, as shown in the example below:

LD-API-Version: 20220603

The header value is the version number of the API version you would like to request. The number for each version corresponds to the date the version was released in yyyymmdd format. In the example above the version 20220603 corresponds to June 03, 2022.

Setting the API version per access token

When you create an access token, you must specify a specific version of the API to use. This ensures that integrations using this token cannot be broken by version changes.

Tokens created before versioning was released have their version set to 20160426, which is the version of the API that existed before the current versioning scheme, so that they continue working the same way they did before versioning.

If you would like to upgrade your integration to use a new API version, you can explicitly set the header described above.

Best practice: Set the header for every client or integration

We recommend that you set the API version header explicitly in any client or integration you build.

Only rely on the access token API version during manual testing.

API version changelog

<div style="width:75px">Version Changes End of life (EOL)
20220603
  • Changed the list projects return value:
    • Response is now paginated with a default limit of 20.
    • Added support for filter and sort.
    • The project environments field is now expandable. This field is omitted by default.
  • Changed the get project return value:
    • The environments field is now expandable. This field is omitted by default.
Current
20210729
  • Changed the create approval request return value. It now returns HTTP Status Code 201 instead of 200.
  • Changed the get users return value. It now returns a user record, not a user.
  • Added additional optional fields to environment, segments, flags, members, and segments, including the ability to create Big Segments.
  • Added default values for flag variations when new environments are created.
  • Added filtering and pagination for getting flags and members, including limit, number, filter, and sort query parameters.
  • Added endpoints for expiring user targets for flags and segments, scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions, and approvals.
2023-06-03
20191212
  • List feature flags now defaults to sending summaries of feature flag configurations, equivalent to setting the query parameter summary=true. Summaries omit flag targeting rules and individual user targets from the payload.
  • Added endpoints for flags, flag status, projects, environments, audit logs, members, users, custom roles, segments, usage, streams, events, and data export.
2022-07-29
20160426
  • Initial versioning of API. Tokens created before versioning have their version set to this.
2020-12-12

This SDK is automatically generated by the OpenAPI Generator project:

  • API version: 2.0
  • Package version: 14.0.0
  • Build package: org.openapitools.codegen.languages.JavascriptClientCodegen For more information, please visit https://support.launchdarkly.com

Installation

For Node.js

npm

To publish the library as a npm, please follow the procedure in "Publishing npm packages".

Then install it via:

npm install launchdarkly-api --save

Finally, you need to build the module:

npm run build
Local development

To use the library locally without publishing to a remote npm registry, first install the dependencies by changing into the directory containing package.json (and this README). Let's call this JAVASCRIPT_CLIENT_DIR. Then run:

npm install

Next, link it globally in npm with the following, also from JAVASCRIPT_CLIENT_DIR:

npm link

To use the link you just defined in your project, switch to the directory you want to use your launchdarkly-api from, and run:

npm link /path/to/<JAVASCRIPT_CLIENT_DIR>

Finally, you need to build the module:

npm run build

git

If the library is hosted at a git repository, e.g.https://github.com/launchdarkly/api-client-javascript then install it via:

    npm install launchdarkly/api-client-javascript --save

For browser

The library also works in the browser environment via npm and browserify. After following the above steps with Node.js and installing browserify with npm install -g browserify, perform the following (assuming main.js is your entry file):

browserify main.js > bundle.js

Then include bundle.js in the HTML pages.

Webpack Configuration

Using Webpack you may encounter the following error: "Module not found: Error: Cannot resolve module", most certainly you should disable AMD loader. Add/merge the following section to your webpack config:

module: {
  rules: [
    {
      parser: {
        amd: false
      }
    }
  ]
}

Getting Started

Please follow the installation instruction and execute the following JS code:

var LaunchDarklyApi = require('launchdarkly-api');

var defaultClient = LaunchDarklyApi.ApiClient.instance;
// Configure API key authorization: ApiKey
var ApiKey = defaultClient.authentications['ApiKey'];
ApiKey.apiKey = "YOUR API KEY"
// Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
//ApiKey.apiKeyPrefix['Authorization'] = "Token"

var api = new LaunchDarklyApi.AccessTokensApi()
var id = "id_example"; // {String} The ID of the access token to update
var callback = function(error, data, response) {
  if (error) {
    console.error(error);
  } else {
    console.log('API called successfully.');
  }
};
api.deleteToken(id, callback);

Documentation for API Endpoints

All URIs are relative to https://app.launchdarkly.com

Class Method HTTP request Description
LaunchDarklyApi.AccessTokensApi deleteToken DELETE /api/v2/tokens/{id} Delete access token
LaunchDarklyApi.AccessTokensApi getToken GET /api/v2/tokens/{id} Get access token
LaunchDarklyApi.AccessTokensApi getTokens GET /api/v2/tokens List access tokens
LaunchDarklyApi.AccessTokensApi patchToken PATCH /api/v2/tokens/{id} Patch access token
LaunchDarklyApi.AccessTokensApi postToken POST /api/v2/tokens Create access token
LaunchDarklyApi.AccessTokensApi resetToken POST /api/v2/tokens/{id}/reset Reset access token
LaunchDarklyApi.AccountMembersApi deleteMember DELETE /api/v2/members/{id} Delete account member
LaunchDarklyApi.AccountMembersApi getMember GET /api/v2/members/{id} Get account member
LaunchDarklyApi.AccountMembersApi getMembers GET /api/v2/members List account members
LaunchDarklyApi.AccountMembersApi patchMember PATCH /api/v2/members/{id} Modify an account member
LaunchDarklyApi.AccountMembersApi postMemberTeams POST /api/v2/members/{id}/teams Add a member to teams
LaunchDarklyApi.AccountMembersApi postMembers POST /api/v2/members Invite new members
LaunchDarklyApi.AccountMembersBetaApi patchMembers PATCH /api/v2/members Modify account members
LaunchDarklyApi.AccountUsageBetaApi getEvaluationsUsage GET /api/v2/usage/evaluations/{projectKey}/{environmentKey}/{featureFlagKey} Get evaluations usage
LaunchDarklyApi.AccountUsageBetaApi getEventsUsage GET /api/v2/usage/events/{type} Get events usage
LaunchDarklyApi.AccountUsageBetaApi getExperimentationKeysUsage GET /api/v2/usage/experimentation-keys Get experimentation keys usage
LaunchDarklyApi.AccountUsageBetaApi getExperimentationUnitsUsage GET /api/v2/usage/experimentation-units Get experimentation units usage
LaunchDarklyApi.AccountUsageBetaApi getMauSdksByType GET /api/v2/usage/mau/sdks Get MAU SDKs by type
LaunchDarklyApi.AccountUsageBetaApi getMauUsage GET /api/v2/usage/mau Get MAU usage
LaunchDarklyApi.AccountUsageBetaApi getMauUsageByCategory GET /api/v2/usage/mau/bycategory Get MAU usage by category
LaunchDarklyApi.AccountUsageBetaApi getStreamUsage GET /api/v2/usage/streams/{source} Get stream usage
LaunchDarklyApi.AccountUsageBetaApi getStreamUsageBySdkVersion GET /api/v2/usage/streams/{source}/bysdkversion Get stream usage by SDK version
LaunchDarklyApi.AccountUsageBetaApi getStreamUsageSdkversion GET /api/v2/usage/streams/{source}/sdkversions Get stream usage SDK versions
LaunchDarklyApi.ApplicationsBetaApi createApplication POST /api/v2/applications Post application
LaunchDarklyApi.ApplicationsBetaApi deleteApplication DELETE /api/v2/applications/{applicationKey} Delete application
LaunchDarklyApi.ApplicationsBetaApi deleteApplicationVersion DELETE /api/v2/applications/{applicationKey}/versions/{versionKey} Delete application version
LaunchDarklyApi.ApplicationsBetaApi getApplication GET /api/v2/applications/{applicationKey} Get application by key
LaunchDarklyApi.ApplicationsBetaApi getApplicationVersions GET /api/v2/applications/{applicationKey}/versions Get application versions by application key
LaunchDarklyApi.ApplicationsBetaApi getApplications GET /api/v2/applications Get applications
LaunchDarklyApi.ApplicationsBetaApi patchApplication PATCH /api/v2/applications/{applicationKey} Update application
LaunchDarklyApi.ApplicationsBetaApi patchApplicationVersion PATCH /api/v2/applications/{applicationKey}/versions/{versionKey} Update application version
LaunchDarklyApi.ApplicationsBetaApi postApplicationVersion POST /api/v2/applications/{applicationKey}/versions Post application version
LaunchDarklyApi.ApprovalsApi deleteApprovalRequest DELETE /api/v2/approval-requests/{id} Delete approval request
LaunchDarklyApi.ApprovalsApi deleteApprovalRequestForFlag DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id} Delete approval request for a flag
LaunchDarklyApi.ApprovalsApi getApprovalForFlag GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id} Get approval request for a flag
LaunchDarklyApi.ApprovalsApi getApprovalRequest GET /api/v2/approval-requests/{id} Get approval request
LaunchDarklyApi.ApprovalsApi getApprovalRequests GET /api/v2/approval-requests List approval requests
LaunchDarklyApi.ApprovalsApi getApprovalsForFlag GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests List approval requests for a flag
LaunchDarklyApi.ApprovalsApi postApprovalRequest POST /api/v2/approval-requests Create approval request
LaunchDarklyApi.ApprovalsApi postApprovalRequestApply POST /api/v2/approval-requests/{id}/apply Apply approval request
LaunchDarklyApi.ApprovalsApi postApprovalRequestApplyForFlag POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id}/apply Apply approval request for a flag
LaunchDarklyApi.ApprovalsApi postApprovalRequestForFlag POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests Create approval request for a flag
LaunchDarklyApi.ApprovalsApi postApprovalRequestReview POST /api/v2/approval-requests/{id}/reviews Review approval request
LaunchDarklyApi.ApprovalsApi postApprovalRequestReviewForFlag POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id}/reviews Review approval request for a flag
LaunchDarklyApi.ApprovalsApi postFlagCopyConfigApprovalRequest POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests-flag-copy Create approval request to copy flag configurations across environments
LaunchDarklyApi.AuditLogApi getAuditLogEntries GET /api/v2/auditlog List audit log entries
LaunchDarklyApi.AuditLogApi getAuditLogEntry GET /api/v2/auditlog/{id} Get audit log entry
LaunchDarklyApi.CodeReferencesApi deleteBranches POST /api/v2/code-refs/repositories/{repo}/branch-delete-tasks Delete branches
LaunchDarklyApi.CodeReferencesApi deleteRepository DELETE /api/v2/code-refs/repositories/{repo} Delete repository
LaunchDarklyApi.CodeReferencesApi getBranch GET /api/v2/code-refs/repositories/{repo}/branches/{branch} Get branch
LaunchDarklyApi.CodeReferencesApi getBranches GET /api/v2/code-refs/repositories/{repo}/branches List branches
LaunchDarklyApi.CodeReferencesApi getExtinctions GET /api/v2/code-refs/extinctions List extinctions
LaunchDarklyApi.CodeReferencesApi getRepositories GET /api/v2/code-refs/repositories List repositories
LaunchDarklyApi.CodeReferencesApi getRepository GET /api/v2/code-refs/repositories/{repo} Get repository
LaunchDarklyApi.CodeReferencesApi getRootStatistic GET /api/v2/code-refs/statistics Get links to code reference repositories for each project
LaunchDarklyApi.CodeReferencesApi getStatistics GET /api/v2/code-refs/statistics/{projectKey} Get code references statistics for flags
LaunchDarklyApi.CodeReferencesApi patchRepository PATCH /api/v2/code-refs/repositories/{repo} Update repository
LaunchDarklyApi.CodeReferencesApi postExtinction POST /api/v2/code-refs/repositories/{repo}/branches/{branch}/extinction-events Create extinction
LaunchDarklyApi.CodeReferencesApi postRepository POST /api/v2/code-refs/repositories Create repository
LaunchDarklyApi.CodeReferencesApi putBranch PUT /api/v2/code-refs/repositories/{repo}/branches/{branch} Upsert branch
LaunchDarklyApi.ContextSettingsApi putContextFlagSetting PUT /api/v2/projects/{projectKey}/environments/{environmentKey}/contexts/{contextKind}/{contextKey}/flags/{featureFlagKey} Update flag settings for context
LaunchDarklyApi.ContextsApi deleteContextInstances DELETE /api/v2/projects/{projectKey}/environments/{environmentKey}/context-instances/{id} Delete context instances
LaunchDarklyApi.ContextsApi evaluateContextInstance POST /api/v2/projects/{projectKey}/environments/{environmentKey}/flags/evaluate Evaluate flags for context instance
LaunchDarklyApi.ContextsApi getContextAttributeNames GET /api/v2/projects/{projectKey}/environments/{environmentKey}/context-attributes Get context attribute names
LaunchDarklyApi.ContextsApi getContextAttributeValues GET /api/v2/projects/{projectKey}/environments/{environmentKey}/context-attributes/{attributeName} Get context attribute values
LaunchDarklyApi.ContextsApi getContextInstances GET /api/v2/projects/{projectKey}/environments/{environmentKey}/context-instances/{id} Get context instances
LaunchDarklyApi.ContextsApi getContextKindsByProjectKey GET /api/v2/projects/{projectKey}/context-kinds Get context kinds
LaunchDarklyApi.ContextsApi getContexts GET /api/v2/projects/{projectKey}/environments/{environmentKey}/contexts/{kind}/{key} Get contexts
LaunchDarklyApi.ContextsApi putContextKind PUT /api/v2/projects/{projectKey}/context-kinds/{key} Create or update context kind
LaunchDarklyApi.ContextsApi searchContextInstances POST /api/v2/projects/{projectKey}/environments/{environmentKey}/context-instances/search Search for context instances
LaunchDarklyApi.ContextsApi searchContexts POST /api/v2/projects/{projectKey}/environments/{environmentKey}/contexts/search Search for contexts
LaunchDarklyApi.CustomRolesApi deleteCustomRole DELETE /api/v2/roles/{customRoleKey} Delete custom role
LaunchDarklyApi.CustomRolesApi getCustomRole GET /api/v2/roles/{customRoleKey} Get custom role
LaunchDarklyApi.CustomRolesApi getCustomRoles GET /api/v2/roles List custom roles
LaunchDarklyApi.CustomRolesApi patchCustomRole PATCH /api/v2/roles/{customRoleKey} Update custom role
LaunchDarklyApi.CustomRolesApi postCustomRole POST /api/v2/roles Create custom role
LaunchDarklyApi.DataExportDestinationsApi deleteDestination DELETE /api/v2/destinations/{projectKey}/{environmentKey}/{id} Delete Data Export destination
LaunchDarklyApi.DataExportDestinationsApi getDestination GET /api/v2/destinations/{projectKey}/{environmentKey}/{id} Get destination
LaunchDarklyApi.DataExportDestinationsApi getDestinations GET /api/v2/destinations List destinations
LaunchDarklyApi.DataExportDestinationsApi patchDestination PATCH /api/v2/destinations/{projectKey}/{environmentKey}/{id} Update Data Export destination
LaunchDarklyApi.DataExportDestinationsApi postDestination POST /api/v2/destinations/{projectKey}/{environmentKey} Create Data Export destination
LaunchDarklyApi.EnvironmentsApi deleteEnvironment DELETE /api/v2/projects/{projectKey}/environments/{environmentKey} Delete environment
LaunchDarklyApi.EnvironmentsApi getEnvironment GET /api/v2/projects/{projectKey}/environments/{environmentKey} Get environment
LaunchDarklyApi.EnvironmentsApi getEnvironmentsByProject GET /api/v2/projects/{projectKey}/environments List environments
LaunchDarklyApi.EnvironmentsApi patchEnvironment PATCH /api/v2/projects/{projectKey}/environments/{environmentKey} Update environment
LaunchDarklyApi.EnvironmentsApi postEnvironment POST /api/v2/projects/{projectKey}/environments Create environment
LaunchDarklyApi.EnvironmentsApi resetEnvironmentMobileKey POST /api/v2/projects/{projectKey}/environments/{environmentKey}/mobileKey Reset environment mobile SDK key
LaunchDarklyApi.EnvironmentsApi resetEnvironmentSDKKey POST /api/v2/projects/{projectKey}/environments/{environmentKey}/apiKey Reset environment SDK key
LaunchDarklyApi.ExperimentsBetaApi createExperiment POST /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments Create experiment
LaunchDarklyApi.ExperimentsBetaApi createIteration POST /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments/{experimentKey}/iterations Create iteration
LaunchDarklyApi.ExperimentsBetaApi getExperiment GET /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments/{experimentKey} Get experiment
LaunchDarklyApi.ExperimentsBetaApi getExperimentResults GET /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments/{experimentKey}/metrics/{metricKey}/results Get experiment results
LaunchDarklyApi.ExperimentsBetaApi getExperimentResultsForMetricGroup GET /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments/{experimentKey}/metric-groups/{metricGroupKey}/results Get experiment results for metric group
LaunchDarklyApi.ExperimentsBetaApi getExperimentationSettings GET /api/v2/projects/{projectKey}/experimentation-settings Get experimentation settings
LaunchDarklyApi.ExperimentsBetaApi getExperiments GET /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments Get experiments
LaunchDarklyApi.ExperimentsBetaApi getLegacyExperimentResults GET /api/v2/flags/{projectKey}/{featureFlagKey}/experiments/{environmentKey}/{metricKey} Get legacy experiment results (deprecated)
LaunchDarklyApi.ExperimentsBetaApi patchExperiment PATCH /api/v2/projects/{projectKey}/environments/{environmentKey}/experiments/{experimentKey} Patch experiment
LaunchDarklyApi.ExperimentsBetaApi putExperimentationSettings PUT /api/v2/projects/{projectKey}/experimentation-settings Update experimentation settings
LaunchDarklyApi.ExperimentsBetaApi resetExperiment DELETE /api/v2/flags/{projectKey}/{featureFlagKey}/experiments/{environmentKey}/{metricKey}/results Reset experiment results
LaunchDarklyApi.FeatureFlagsApi copyFeatureFlag POST /api/v2/flags/{projectKey}/{featureFlagKey}/copy Copy feature flag
LaunchDarklyApi.FeatureFlagsApi deleteFeatureFlag DELETE /api/v2/flags/{projectKey}/{featureFlagKey} Delete feature flag
LaunchDarklyApi.FeatureFlagsApi getExpiringContextTargets GET /api/v2/flags/{projectKey}/{featureFlagKey}/expiring-targets/{environmentKey} Get expiring context targets for feature flag
LaunchDarklyApi.FeatureFlagsApi getExpiringUserTargets GET /api/v2/flags/{projectKey}/{featureFlagKey}/expiring-user-targets/{environmentKey} Get expiring user targets for feature flag
LaunchDarklyApi.FeatureFlagsApi getFeatureFlag GET /api/v2/flags/{projectKey}/{featureFlagKey} Get feature flag
LaunchDarklyApi.FeatureFlagsApi getFeatureFlagStatus GET /api/v2/flag-statuses/{projectKey}/{environmentKey}/{featureFlagKey} Get feature flag status
LaunchDarklyApi.FeatureFlagsApi getFeatureFlagStatusAcrossEnvironments GET /api/v2/flag-status/{projectKey}/{featureFlagKey} Get flag status across environments
LaunchDarklyApi.FeatureFlagsApi getFeatureFlagStatuses GET /api/v2/flag-statuses/{projectKey}/{environmentKey} List feature flag statuses
LaunchDarklyApi.FeatureFlagsApi getFeatureFlags GET /api/v2/flags/{projectKey} List feature flags
LaunchDarklyApi.FeatureFlagsApi patchExpiringTargets PATCH /api/v2/flags/{projectKey}/{featureFlagKey}/expiring-targets/{environmentKey} Update expiring context targets on feature flag
LaunchDarklyApi.FeatureFlagsApi patchExpiringUserTargets PATCH /api/v2/flags/{projectKey}/{featureFlagKey}/expiring-user-targets/{environmentKey} Update expiring user targets on feature flag
LaunchDarklyApi.FeatureFlagsApi patchFeatureFlag PATCH /api/v2/flags/{projectKey}/{featureFlagKey} Update feature flag
LaunchDarklyApi.FeatureFlagsApi postFeatureFlag POST /api/v2/flags/{projectKey} Create a feature flag
LaunchDarklyApi.FeatureFlagsBetaApi getDependentFlags GET /api/v2/flags/{projectKey}/{featureFlagKey}/dependent-flags List dependent feature flags
LaunchDarklyApi.FeatureFlagsBetaApi getDependentFlagsByEnv GET /api/v2/flags/{projectKey}/{environmentKey}/{featureFlagKey}/dependent-flags List dependent feature flags by environment
LaunchDarklyApi.FeatureFlagsBetaApi postMigrationSafetyIssues POST /api/v2/projects/{projectKey}/flags/{flagKey}/environments/{environmentKey}/migration-safety-issues Get migration safety issues
LaunchDarklyApi.FlagLinksBetaApi createFlagLink POST /api/v2/flag-links/projects/{projectKey}/flags/{featureFlagKey} Create flag link
LaunchDarklyApi.FlagLinksBetaApi deleteFlagLink DELETE /api/v2/flag-links/projects/{projectKey}/flags/{featureFlagKey}/{id} Delete flag link
LaunchDarklyApi.FlagLinksBetaApi getFlagLinks GET /api/v2/flag-links/projects/{projectKey}/flags/{featureFlagKey} List flag links
LaunchDarklyApi.FlagLinksBetaApi updateFlagLink PATCH /api/v2/flag-links/projects/{projectKey}/flags/{featureFlagKey}/{id} Update flag link
LaunchDarklyApi.FlagTriggersApi createTriggerWorkflow POST /api/v2/flags/{projectKey}/{featureFlagKey}/triggers/{environmentKey} Create flag trigger
LaunchDarklyApi.FlagTriggersApi deleteTriggerWorkflow DELETE /api/v2/flags/{projectKey}/{featureFlagKey}/triggers/{environmentKey}/{id} Delete flag trigger
LaunchDarklyApi.FlagTriggersApi getTriggerWorkflowById GET /api/v2/flags/{projectKey}/{featureFlagKey}/triggers/{environmentKey}/{id} Get flag trigger by ID
LaunchDarklyApi.FlagTriggersApi getTriggerWorkflows GET /api/v2/flags/{projectKey}/{featureFlagKey}/triggers/{environmentKey} List flag triggers
LaunchDarklyApi.FlagTriggersApi patchTriggerWorkflow PATCH /api/v2/flags/{projectKey}/{featureFlagKey}/triggers/{environmentKey}/{id} Update flag trigger
LaunchDarklyApi.FollowFlagsApi deleteFlagFollowers DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/followers/{memberId} Remove a member as a follower of a flag in a project and environment
LaunchDarklyApi.FollowFlagsApi getFlagFollowers GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/followers Get followers of a flag in a project and environment
LaunchDarklyApi.FollowFlagsApi getFollowersByProjEnv GET /api/v2/projects/{projectKey}/environments/{environmentKey}/followers Get followers of all flags in a given project and environment
LaunchDarklyApi.FollowFlagsApi putFlagFollowers PUT /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/followers/{memberId} Add a member as a follower of a flag in a project and environment
LaunchDarklyApi.IntegrationAuditLogSubscriptionsApi createSubscription POST /api/v2/integrations/{integrationKey} Create audit log subscription
LaunchDarklyApi.IntegrationAuditLogSubscriptionsApi deleteSubscription DELETE /api/v2/integrations/{integrationKey}/{id} Delete audit log subscription
LaunchDarklyApi.IntegrationAuditLogSubscriptionsApi getSubscriptionByID GET /api/v2/integrations/{integrationKey}/{id} Get audit log subscription by ID
LaunchDarklyApi.IntegrationAuditLogSubscriptionsApi getSubscriptions GET /api/v2/integrations/{integrationKey} Get audit log subscriptions by integration
LaunchDarklyApi.IntegrationAuditLogSubscriptionsApi updateSubscription PATCH /api/v2/integrations/{integrationKey}/{id} Update audit log subscription
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi createIntegrationDeliveryConfiguration POST /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey}/{integrationKey} Create delivery configuration
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi deleteIntegrationDeliveryConfiguration DELETE /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey}/{integrationKey}/{id} Delete delivery configuration
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi getIntegrationDeliveryConfigurationByEnvironment GET /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey} Get delivery configurations by environment
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi getIntegrationDeliveryConfigurationById GET /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey}/{integrationKey}/{id} Get delivery configuration by ID
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi getIntegrationDeliveryConfigurations GET /api/v2/integration-capabilities/featureStore List all delivery configurations
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi patchIntegrationDeliveryConfiguration PATCH /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey}/{integrationKey}/{id} Update delivery configuration
LaunchDarklyApi.IntegrationDeliveryConfigurationsBetaApi validateIntegrationDeliveryConfiguration POST /api/v2/integration-capabilities/featureStore/{projectKey}/{environmentKey}/{integrationKey}/{id}/validate Validate delivery configuration
LaunchDarklyApi.MetricsApi deleteMetric DELETE /api/v2/metrics/{projectKey}/{metricKey} Delete metric
LaunchDarklyApi.MetricsApi getMetric GET /api/v2/metrics/{projectKey}/{metricKey} Get metric
LaunchDarklyApi.MetricsApi getMetrics GET /api/v2/metrics/{projectKey} List metrics
LaunchDarklyApi.MetricsApi patchMetric PATCH /api/v2/metrics/{projectKey}/{metricKey} Update metric
LaunchDarklyApi.MetricsApi postMetric POST /api/v2/metrics/{projectKey} Create metric
LaunchDarklyApi.MetricsBetaApi createMetricGroup POST /api/v2/projects/{projectKey}/metric-groups Create metric group
LaunchDarklyApi.MetricsBetaApi deleteMetricGroup DELETE /api/v2/projects/{projectKey}/metric-groups/{metricGroupKey} Delete metric group
LaunchDarklyApi.MetricsBetaApi getMetricGroup GET /api/v2/projects/{projectKey}/metric-groups/{metricGroupKey} Get metric group
LaunchDarklyApi.MetricsBetaApi getMetricGroups GET /api/v2/projects/{projectKey}/metric-groups List metric groups
LaunchDarklyApi.MetricsBetaApi patchMetricGroup PATCH /api/v2/projects/{projectKey}/metric-groups/{metricGroupKey} Patch metric group
LaunchDarklyApi.OAuth2ClientsApi createOAuth2Client POST /api/v2/oauth/clients Create a LaunchDarkly OAuth 2.0 client
LaunchDarklyApi.OAuth2ClientsApi deleteOAuthClient DELETE /api/v2/oauth/clients/{clientId} Delete OAuth 2.0 client
LaunchDarklyApi.OAuth2ClientsApi getOAuthClientById GET /api/v2/oauth/clients/{clientId} Get client by ID
LaunchDarklyApi.OAuth2ClientsApi getOAuthClients GET /api/v2/oauth/clients Get clients
LaunchDarklyApi.OAuth2ClientsApi patchOAuthClient PATCH /api/v2/oauth/clients/{clientId} Patch client by ID
LaunchDarklyApi.OtherApi getIps GET /api/v2/public-ip-list Gets the public IP list
LaunchDarklyApi.OtherApi getOpenapiSpec GET /api/v2/openapi.json Gets the OpenAPI spec in json
LaunchDarklyApi.OtherApi getRoot GET /api/v2 Root resource
LaunchDarklyApi.OtherApi getVersions GET /api/v2/versions Get version information
LaunchDarklyApi.ProjectsApi deleteProject DELETE /api/v2/projects/{projectKey} Delete project
LaunchDarklyApi.ProjectsApi getFlagDefaultsByProject GET /api/v2/projects/{projectKey}/flag-defaults Get flag defaults for project
LaunchDarklyApi.ProjectsApi getProject GET /api/v2/projects/{projectKey} Get project
LaunchDarklyApi.ProjectsApi getProjects GET /api/v2/projects List projects
LaunchDarklyApi.ProjectsApi patchFlagDefaultsByProject PATCH /api/v2/projects/{projectKey}/flag-defaults Update flag default for project
LaunchDarklyApi.ProjectsApi patchProject PATCH /api/v2/projects/{projectKey} Update project
LaunchDarklyApi.ProjectsApi postProject POST /api/v2/projects Create project
LaunchDarklyApi.ProjectsApi putFlagDefaultsByProject PUT /api/v2/projects/{projectKey}/flag-defaults Create or update flag defaults for project
LaunchDarklyApi.RelayProxyConfigurationsApi deleteRelayAutoConfig DELETE /api/v2/account/relay-auto-configs/{id} Delete Relay Proxy config by ID
LaunchDarklyApi.RelayProxyConfigurationsApi getRelayProxyConfig GET /api/v2/account/relay-auto-configs/{id} Get Relay Proxy config
LaunchDarklyApi.RelayProxyConfigurationsApi getRelayProxyConfigs GET /api/v2/account/relay-auto-configs List Relay Proxy configs
LaunchDarklyApi.RelayProxyConfigurationsApi patchRelayAutoConfig PATCH /api/v2/account/relay-auto-configs/{id} Update a Relay Proxy config
LaunchDarklyApi.RelayProxyConfigurationsApi postRelayAutoConfig POST /api/v2/account/relay-auto-configs Create a new Relay Proxy config
LaunchDarklyApi.RelayProxyConfigurationsApi resetRelayAutoConfig POST /api/v2/account/relay-auto-configs/{id}/reset Reset Relay Proxy configuration key
LaunchDarklyApi.ReleasePipelinesBetaApi deleteReleasePipeline DELETE /api/v2/projects/{projectKey}/release-pipelines/{pipelineKey} Delete release pipeline
LaunchDarklyApi.ReleasePipelinesBetaApi getAllReleasePipelines GET /api/v2/projects/{projectKey}/release-pipelines Get all release pipelines
LaunchDarklyApi.ReleasePipelinesBetaApi getReleasePipelineByKey GET /api/v2/projects/{projectKey}/release-pipelines/{pipelineKey} Get release pipeline by key
LaunchDarklyApi.ReleasePipelinesBetaApi patchReleasePipeline PATCH /api/v2/projects/{projectKey}/release-pipelines/{pipelineKey} Update a release pipeline
LaunchDarklyApi.ReleasePipelinesBetaApi postReleasePipeline POST /api/v2/projects/{projectKey}/release-pipelines Create a release pipeline
LaunchDarklyApi.ReleasesBetaApi getReleaseByFlagKey GET /api/v2/flags/{projectKey}/{flagKey}/release Get release for flag
LaunchDarklyApi.ReleasesBetaApi patchReleaseByFlagKey PATCH /api/v2/flags/{projectKey}/{flagKey}/release Patch release for flag
LaunchDarklyApi.ScheduledChangesApi deleteFlagConfigScheduledChanges DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Delete scheduled changes workflow
LaunchDarklyApi.ScheduledChangesApi getFeatureFlagScheduledChange GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Get a scheduled change
LaunchDarklyApi.ScheduledChangesApi getFlagConfigScheduledChanges GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes List scheduled changes
LaunchDarklyApi.ScheduledChangesApi patchFlagConfigScheduledChange PATCH /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Update scheduled changes workflow
LaunchDarklyApi.ScheduledChangesApi postFlagConfigScheduledChanges POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes Create scheduled changes workflow
LaunchDarklyApi.SegmentsApi deleteSegment DELETE /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey} Delete segment
LaunchDarklyApi.SegmentsApi getContextInstanceSegmentsMembershipByEnv POST /api/v2/projects/{projectKey}/environments/{environmentKey}/segments/evaluate List segment memberships for context instance
LaunchDarklyApi.SegmentsApi getExpiringTargetsForSegment GET /api/v2/segments/{projectKey}/{segmentKey}/expiring-targets/{environmentKey} Get expiring targets for segment
LaunchDarklyApi.SegmentsApi getExpiringUserTargetsForSegment GET /api/v2/segments/{projectKey}/{segmentKey}/expiring-user-targets/{environmentKey} Get expiring user targets for segment
LaunchDarklyApi.SegmentsApi getSegment GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey} Get segment
LaunchDarklyApi.SegmentsApi getSegmentMembershipForContext GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/contexts/{contextKey} Get Big Segment membership for context
LaunchDarklyApi.SegmentsApi getSegmentMembershipForUser GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/users/{userKey} Get Big Segment membership for user
LaunchDarklyApi.SegmentsApi getSegments GET /api/v2/segments/{projectKey}/{environmentKey} List segments
LaunchDarklyApi.SegmentsApi patchExpiringTargetsForSegment PATCH /api/v2/segments/{projectKey}/{segmentKey}/expiring-targets/{environmentKey} Update expiring targets for segment
LaunchDarklyApi.SegmentsApi patchExpiringUserTargetsForSegment PATCH /api/v2/segments/{projectKey}/{segmentKey}/expiring-user-targets/{environmentKey} Update expiring user targets for segment
LaunchDarklyApi.SegmentsApi patchSegment PATCH /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey} Patch segment
LaunchDarklyApi.SegmentsApi postSegment POST /api/v2/segments/{projectKey}/{environmentKey} Create segment
LaunchDarklyApi.SegmentsApi updateBigSegmentContextTargets POST /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/contexts Update context targets on a Big Segment
LaunchDarklyApi.SegmentsApi updateBigSegmentTargets POST /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/users Update user context targets on a Big Segment
LaunchDarklyApi.SegmentsBetaApi createBigSegmentExport POST /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/exports Create Big Segment export
LaunchDarklyApi.SegmentsBetaApi createBigSegmentImport POST /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/imports Create Big Segment import
LaunchDarklyApi.SegmentsBetaApi getBigSegmentExport GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/exports/{exportID} Get Big Segment export
LaunchDarklyApi.SegmentsBetaApi getBigSegmentImport GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/imports/{importID} Get Big Segment import
LaunchDarklyApi.TagsApi getTags GET /api/v2/tags List tags
LaunchDarklyApi.TeamsApi deleteTeam DELETE /api/v2/teams/{teamKey} Delete team
LaunchDarklyApi.TeamsApi getTeam GET /api/v2/teams/{teamKey} Get team
LaunchDarklyApi.TeamsApi getTeamMaintainers GET /api/v2/teams/{teamKey}/maintainers Get team maintainers
LaunchDarklyApi.TeamsApi getTeamRoles GET /api/v2/teams/{teamKey}/roles Get team custom roles
LaunchDarklyApi.TeamsApi getTeams GET /api/v2/teams List teams
LaunchDarklyApi.TeamsApi patchTeam PATCH /api/v2/teams/{teamKey} Update team
LaunchDarklyApi.TeamsApi postTeam POST /api/v2/teams Create team
LaunchDarklyApi.TeamsApi postTeamMembers POST /api/v2/teams/{teamKey}/members Add multiple members to team
LaunchDarklyApi.TeamsBetaApi patchTeams PATCH /api/v2/teams Update teams
LaunchDarklyApi.UserSettingsApi getExpiringFlagsForUser GET /api/v2/users/{projectKey}/{userKey}/expiring-user-targets/{environmentKey} Get expiring dates on flags for user
LaunchDarklyApi.UserSettingsApi getUserFlagSetting GET /api/v2/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey} Get flag setting for user
LaunchDarklyApi.UserSettingsApi getUserFlagSettings GET /api/v2/users/{projectKey}/{environmentKey}/{userKey}/flags List flag settings for user
LaunchDarklyApi.UserSettingsApi patchExpiringFlagsForUser PATCH /api/v2/users/{projectKey}/{userKey}/expiring-user-targets/{environmentKey} Update expiring user target for flags
LaunchDarklyApi.UserSettingsApi putFlagSetting PUT /api/v2/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey} Update flag settings for user
LaunchDarklyApi.UsersApi deleteUser DELETE /api/v2/users/{projectKey}/{environmentKey}/{userKey} Delete user
LaunchDarklyApi.UsersApi getSearchUsers GET /api/v2/user-search/{projectKey}/{environmentKey} Find users
LaunchDarklyApi.UsersApi getUser GET /api/v2/users/{projectKey}/{environmentKey}/{userKey} Get user
LaunchDarklyApi.UsersApi getUsers GET /api/v2/users/{projectKey}/{environmentKey} List users
LaunchDarklyApi.UsersBetaApi getUserAttributeNames GET /api/v2/user-attributes/{projectKey}/{environmentKey} Get user attribute names
LaunchDarklyApi.WebhooksApi deleteWebhook DELETE /api/v2/webhooks/{id} Delete webhook
LaunchDarklyApi.WebhooksApi getAllWebhooks GET /api/v2/webhooks List webhooks
LaunchDarklyApi.WebhooksApi getWebhook GET /api/v2/webhooks/{id} Get webhook
LaunchDarklyApi.WebhooksApi patchWebhook PATCH /api/v2/webhooks/{id} Update webhook
LaunchDarklyApi.WebhooksApi postWebhook POST /api/v2/webhooks Creates a webhook
LaunchDarklyApi.WorkflowTemplatesApi createWorkflowTemplate POST /api/v2/templates Create workflow template
LaunchDarklyApi.WorkflowTemplatesApi deleteWorkflowTemplate DELETE /api/v2/templates/{templateKey} Delete workflow template
LaunchDarklyApi.WorkflowTemplatesApi getWorkflowTemplates GET /api/v2/templates Get workflow templates
LaunchDarklyApi.WorkflowsApi deleteWorkflow DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows/{workflowId} Delete workflow
LaunchDarklyApi.WorkflowsApi getCustomWorkflow GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows/{workflowId} Get custom workflow
LaunchDarklyApi.WorkflowsApi getWorkflows GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows Get workflows
LaunchDarklyApi.WorkflowsApi postWorkflow POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows Create workflow

Documentation for Models

Documentation for Authorization

ApiKey

  • Type: API key
  • API key parameter name: Authorization
  • Location: HTTP header

Sample Code

var LaunchDarklyApi = require('launchdarkly-api');

var defaultClient = LaunchDarklyApi.ApiClient.instance;

var Token = defaultClient.authentications['ApiKey'];
Token.apiKey = process.env.LD_API_KEY;

var apiInstance = new LaunchDarklyApi.FeatureFlagsApi();

const projectName = "openapi";
const keyName = "test-javascript";

var callback = function(error, data) {
  if (error) {
    console.error(error);
    process.exit(1);
  } else {
    console.log('API called successfully. Returned data: ' + JSON.stringify(data));
  }
};

var postCallback = function(error, data) {
  callback(error, data);

  if (!error) {
    // Clean up
    apiInstance.deleteFeatureFlag(projectName, keyName, callback);
  }
};

apiInstance.postFeatureFlag(projectName,
  {
    name: "Test Flag Javascript",
    key: keyName,
    variations: [{value: [1, 2]}, {value: [3, 4]}, {value: [5]}]
  }, {}, postCallback);

Readme

Keywords

none

Package Sidebar

Install

npm i launchdarkly-api

Weekly Downloads

1,129

Version

14.0.0

License

Apache 2.0

Unpacked Size

14.7 MB

Total Files

429

Last publish

Collaborators

  • launchdarkly