launchdarkly/api-client-php

# Overview ## Authentication All REST API resources are authenticated with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens), or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens

7.1.1 2022-01-15 00:51 UTC

This package is auto-updated.

Last update: 2022-01-15 00:51:28 UTC


README

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.

OpenAPIClient-php

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 client-side SDKs, respectively. These keys cannot be used to access our REST API. These keys are environment-specific, and can only perform read-only operations (fetching feature flag settings).

Auth mechanism Allowed resources Use cases
Personal access tokens Can be customized on a per-token basis Building scripts, custom integrations, data export
SDK keys Can only access read-only SDK-specific resources and the firehose, restricted to a single environment Server-side SDKs, Firehose API
Mobile keys Can only access read-only mobile SDK-specific resources, restricted to a single environment Mobile SDKs
Client-side ID Single environment, only flags marked available to client-side 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.

Via 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.

Via session cookie

For testing purposes, you can make API calls directly from your web browser. If you're logged in to the 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 will also send a JSON body. Read Errors for a more detailed description of the error format used by the API.

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

In addition, request bodies for PUT, POST, REPORT and PATCH 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 (for example, a single feature flag), you receive a detailed representation containing all of the attributes 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.

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 (the URL) and a type (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, and support the JSON Patch format. Some resources also support the JSON Merge Patch format. In addition, some resources support optional comments that can be submitted with updates. Comments appear in outgoing webhooks, the audit log, and other integrations.

Updates via JSON Patch

JSON Patch is a way to specify the modifications to perform on a resource. 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\" }]

JSON Patch documents are always arrays. 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 aren't editable, like a resource's _links, have names that start with an underscore.

Updates via JSON Merge Patch

The API also supports the JSON Merge Patch format, as well as the Update feature flag resource.

JSON Merge Patch is less expressive than JSON Patch but 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 with comments

You can submit optional comments with PATCH changes. The Update feature flag resource supports comments.

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\" }
}

Updates via semantic patches

The API also supports 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.

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. Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, semantic patch instructions can also be defined independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date.

For example, in this feature flag configuration in environment Production:

{
    \"name\": \"Alternate sort order\",
    \"kind\": \"boolean\",
    \"key\": \"sort.order\",
   ...
    \"environments\": {
        \"production\": {
            \"on\": true,
            \"archived\": false,
            \"salt\": \"c29ydC5vcmRlcg==\",
            \"sel\": \"8de1085cb7354b0ab41c0e778376dfd3\",
            \"lastModified\": 1469131558260,
            \"version\": 81,
            \"targets\": [
                {
                    \"values\": [
                        \"Gerhard.Little@yahoo.com\"
                    ],
                    \"variation\": 0
                },
                {
                    \"values\": [
                        \"1461797806429-33-861961230\",
                        \"438580d8-02ee-418d-9eec-0085cab2bdf0\"
                    ],
                    \"variation\": 1
                }
            ],
            \"rules\": [],
            \"fallthrough\": {
                \"variation\": 0
            },
            \"offVariation\": 1,
            \"prerequisites\": [],
            \"_site\": {
                \"href\": \"/default/production/features/sort.order\",
                \"type\": \"text/html\"
            }
       }
    }
}

You can add a date you want a user to be removed from the feature flag's user targets. For example, “remove user 1461797806429-33-861961230 from the user target for variation 0 on the Alternate sort order flag in the production environment on Wed Jul 08 2020 at 15:27:41 pm”. This is done using the following:

{
  \"comment\": \"update expiring user targets\",
  \"instructions\": [
    {
      \"kind\": \"removeExpireUserTargetDate\",
      \"userKey\": \"userKey\",
      \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\"
    },
    {
      \"kind\": \"updateExpireUserTargetDate\",
      \"userKey\": \"userKey2\",
      \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\",
      \"value\": 1587582000000
    },
    {
      \"kind\": \"addExpireUserTargetDate\",
      \"userKey\": \"userKey3\",
      \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\",
      \"value\": 1594247266386
    }
  ]
}

Here is another example. In this feature flag configuration:

{
  \"name\": \"New recommendations engine\",
  \"key\": \"engine.enable\",
  \"environments\": {
    \"test\": {
      \"on\": true
    }
  }
}

You can change the feature flag's description with the following patch document as a set of executable instructions. For example, “add user X to targets for variation Y and remove user A from targets for variation B for test flag”:

{
  \"comment\": \"\",
  \"instructions\": [
    {
      \"kind\": \"removeUserTargets\",
      \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"],
      \"variationId\": \"852cb784-54ff-46b9-8c35-5498d2e4f270\"
    },
    {
      \"kind\": \"addUserTargets\",
      \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"],
      \"variationId\": \"1bb18465-33b6-49aa-a3bd-eeb6650b33ad\"
    }
  ]
}

Supported semantic patch API endpoints

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 general class of error is indicated by the code. 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 Desc. Possible Solution
400 Bad Request A request that fails may return this HTTP response code. Ensure JSON syntax in request body is correct.
401 Unauthorized User doesn't have permission to an API call. Ensure your SDK key is good.
403 Forbidden User does not have permission for operation. Ensure that the user or access token has proper permissions set.
409 Conflict The API request could not be completed because it conflicted with a concurrent API request. Retry your request.
429 Too many requests See 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, a wildcard is returned: Access-Control-Allow-Origin: *. For more information on CORS, see 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’re using session auth, you should set the withCredentials property for your xhr request to true. You should never expose your access tokens to untrusted users.

Rate limiting

We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs will return a 429 status code. Calls to our APIs will 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.

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

Global rate limits

Authenticated requests are subject to a global limit. This is the maximum number of calls that can be made to the API per ten seconds. All 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 will 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 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 will 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 can be made 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)

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

You can use this specification to generate client libraries to interact with our REST API in your language of choice.

This specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to ease use in navigating the APIs in the tooling.

Client libraries

We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit GitHub.

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 PUT, PATCH, and DELETE verbs will be inaccessible.

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

For example, if you wish to call one of our PATCH resources via 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.

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'll receive a 403 response.

Use this header:

LD-API-Version: beta

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: 20191212

The header value is the version number of the API version you'd like to request. The number for each version corresponds to the date the version was released. In the example above the version 20191212 corresponds to December 12, 2019.

Setting the API version per access token

When creating 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 (the version of the API that existed before versioning) 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.

For more information, please visit https://support.launchdarkly.com.

Installation & Usage

Requirements

PHP 7.3 and later. Should also work with PHP 8.0 but has not been tested.

Composer

To install the bindings via Composer, add the following to composer.json:

{
  "repositories": [
    {
      "type": "vcs",
      "url": "https://github.com/launchdarkly/api-client-php.git"
    }
  ],
  "require": {
    "launchdarkly/api-client-php": "*@dev"
  }
}

Then run composer install

Manual Installation

Download the files and include autoload.php:

<?php
require_once('/path/to/OpenAPIClient-php/vendor/autoload.php');

Getting Started

Please follow the installation procedure and then run the following:

<?php
require_once(__DIR__ . '/vendor/autoload.php');



// Configure API key authorization: ApiKey
$config = LaunchDarklyApi\Configuration::getDefaultConfiguration()->setApiKey('Authorization', 'YOUR_API_KEY');
// Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
// $config = LaunchDarklyApi\Configuration::getDefaultConfiguration()->setApiKeyPrefix('Authorization', 'Bearer');


$apiInstance = new LaunchDarklyApi\Api\AccessTokensApi(
    // If you want use custom http client, pass your client which implements `GuzzleHttp\ClientInterface`.
    // This is optional, `GuzzleHttp\Client` will be used as default.
    new GuzzleHttp\Client(),
    $config
);
$id = 'id_example'; // string | The ID of the access token to update

try {
    $apiInstance->deleteToken($id);
} catch (Exception $e) {
    echo 'Exception when calling AccessTokensApi->deleteToken: ', $e->getMessage(), PHP_EOL;
}

API Endpoints

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

Class Method HTTP request Description
AccessTokensApi deleteToken DELETE /api/v2/tokens/{id} Delete access token
AccessTokensApi getToken GET /api/v2/tokens/{id} Get access token
AccessTokensApi getTokens GET /api/v2/tokens List access tokens
AccessTokensApi patchToken PATCH /api/v2/tokens/{id} Patch access token
AccessTokensApi postToken POST /api/v2/tokens Create access token
AccessTokensApi resetToken POST /api/v2/tokens/{id}/reset Reset access token
AccountMembersApi deleteMember DELETE /api/v2/members/{id} Delete account member
AccountMembersApi getMember GET /api/v2/members/{id} Get account member
AccountMembersApi getMembers GET /api/v2/members List account members
AccountMembersApi patchMember PATCH /api/v2/members/{id} Modify an account member
AccountMembersApi postMemberTeams POST /api/v2/members/{id}/teams Add member to teams
AccountMembersApi postMembers POST /api/v2/members Invite new members
AccountUsageBetaApi getEvaluationsUsage GET /api/v2/usage/evaluations/{projKey}/{envKey}/{flagKey} Get evaluations usage
AccountUsageBetaApi getEventsUsage GET /api/v2/usage/events/{type} Get events usage
AccountUsageBetaApi getMauSdksByType GET /api/v2/usage/mau/sdks Get MAU SDKs by type
AccountUsageBetaApi getMauUsage GET /api/v2/usage/mau Get MAU usage
AccountUsageBetaApi getMauUsageByCategory GET /api/v2/usage/mau/bycategory Get MAU usage by category
AccountUsageBetaApi getStreamUsage GET /api/v2/usage/streams/{source} Get stream usage
AccountUsageBetaApi getStreamUsageBySdkVersion GET /api/v2/usage/streams/{source}/bysdkversion Get stream usage by SDK version
AccountUsageBetaApi getStreamUsageSdkversion GET /api/v2/usage/streams/{source}/sdkversions Get stream usage SDK versions
ApprovalsApi deleteApprovalRequest DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id} Delete approval request
ApprovalsApi getApproval GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id} Get approval request
ApprovalsApi getApprovals GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests List all approval requests
ApprovalsApi postApprovalRequest POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests Create approval request
ApprovalsApi postApprovalRequestApplyRequest POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id}/apply Apply approval request
ApprovalsApi postApprovalRequestReview POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{id}/reviews Review approval request
ApprovalsApi postFlagCopyConfigApprovalRequest POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests-flag-copy Create approval request to copy flag configurations across environments
AuditLogApi getAuditLogEntries GET /api/v2/auditlog List audit log feature flag entries
AuditLogApi getAuditLogEntry GET /api/v2/auditlog/{id} Get audit log entry
CodeReferencesApi deleteBranches POST /api/v2/code-refs/repositories/{repo}/branch-delete-tasks Delete branches
CodeReferencesApi deleteRepository DELETE /api/v2/code-refs/repositories/{repo} Delete repository
CodeReferencesApi getBranch GET /api/v2/code-refs/repositories/{repo}/branches/{branch} Get branch
CodeReferencesApi getBranches GET /api/v2/code-refs/repositories/{repo}/branches List branches
CodeReferencesApi getExtinctions GET /api/v2/code-refs/extinctions List extinctions
CodeReferencesApi getRepositories GET /api/v2/code-refs/repositories List repositories
CodeReferencesApi getRepository GET /api/v2/code-refs/repositories/{repo} Get repository
CodeReferencesApi getRootStatistic GET /api/v2/code-refs/statistics Get links to code reference repositories for each project
CodeReferencesApi getStatistics GET /api/v2/code-refs/statistics/{projKey} Get number of code references for flags
CodeReferencesApi patchRepository PATCH /api/v2/code-refs/repositories/{repo} Update repository
CodeReferencesApi postExtinction POST /api/v2/code-refs/repositories/{repo}/branches/{branch}/extinction-events Create extinction
CodeReferencesApi postRepository POST /api/v2/code-refs/repositories Create repository
CodeReferencesApi putBranch PUT /api/v2/code-refs/repositories/{repo}/branches/{branch} Upsert branch
CustomRolesApi deleteCustomRole DELETE /api/v2/roles/{key} Delete custom role
CustomRolesApi getCustomRole GET /api/v2/roles/{key} Get custom role
CustomRolesApi getCustomRoles GET /api/v2/roles List custom roles
CustomRolesApi patchCustomRole PATCH /api/v2/roles/{key} Update custom role
CustomRolesApi postCustomRole POST /api/v2/roles Create custom role
DataExportDestinationsApi deleteDestination DELETE /api/v2/destinations/{projKey}/{envKey}/{id} Delete Data Export destination
DataExportDestinationsApi getDestination GET /api/v2/destinations/{projKey}/{envKey}/{id} Get destination
DataExportDestinationsApi getDestinations GET /api/v2/destinations List destinations
DataExportDestinationsApi patchDestination PATCH /api/v2/destinations/{projKey}/{envKey}/{id} Update Data Export destination
DataExportDestinationsApi postDestination POST /api/v2/destinations/{projKey}/{envKey} Create data export destination
EnvironmentsApi deleteEnvironment DELETE /api/v2/projects/{projectKey}/environments/{environmentKey} Delete environment
EnvironmentsApi getEnvironment GET /api/v2/projects/{projectKey}/environments/{environmentKey} Get environment
EnvironmentsApi patchEnvironment PATCH /api/v2/projects/{projectKey}/environments/{environmentKey} Update environment
EnvironmentsApi postEnvironment POST /api/v2/projects/{projectKey}/environments Create environment
EnvironmentsApi resetEnvironmentMobileKey POST /api/v2/projects/{projectKey}/environments/{envKey}/mobileKey Reset environment mobile SDK key
EnvironmentsApi resetEnvironmentSDKKey POST /api/v2/projects/{projectKey}/environments/{envKey}/apiKey Reset environment SDK key
ExperimentsBetaApi getExperiment GET /api/v2/flags/{projKey}/{flagKey}/experiments/{envKey}/{metricKey} Get experiment results
ExperimentsBetaApi resetExperiment DELETE /api/v2/flags/{projKey}/{flagKey}/experiments/{envKey}/{metricKey}/results Reset experiment results
FeatureFlagsApi copyFeatureFlag POST /api/v2/flags/{projKey}/{featureFlagKey}/copy Copy feature flag
FeatureFlagsApi deleteFeatureFlag DELETE /api/v2/flags/{projKey}/{key} Delete feature flag
FeatureFlagsApi getExpiringUserTargets GET /api/v2/flags/{projKey}/{flagKey}/expiring-user-targets/{envKey} Get expiring user targets for feature flag
FeatureFlagsApi getFeatureFlag GET /api/v2/flags/{projKey}/{key} Get feature flag
FeatureFlagsApi getFeatureFlagStatus GET /api/v2/flag-statuses/{projKey}/{envKey}/{key} Get feature flag status
FeatureFlagsApi getFeatureFlagStatusAcrossEnvironments GET /api/v2/flag-status/{projKey}/{key} Get flag status across environments
FeatureFlagsApi getFeatureFlagStatuses GET /api/v2/flag-statuses/{projKey}/{envKey} List feature flag statuses
FeatureFlagsApi getFeatureFlags GET /api/v2/flags/{projKey} List feature flags
FeatureFlagsApi patchExpiringUserTargets PATCH /api/v2/flags/{projKey}/{flagKey}/expiring-user-targets/{envKey} Update expiring user targets on feature flag
FeatureFlagsApi patchFeatureFlag PATCH /api/v2/flags/{projKey}/{key} Update feature flag
FeatureFlagsApi postFeatureFlag POST /api/v2/flags/{projKey} Create a feature flag
FeatureFlagsBetaApi getDependentFlags GET /api/v2/flags/{projKey}/{flagKey}/dependent-flags List dependent feature flags
FeatureFlagsBetaApi getDependentFlagsByEnv GET /api/v2/flags/{projKey}/{envKey}/{flagKey}/dependent-flags List dependent feature flags by environment
FlagTriggersApi createTriggerWorkflow POST /api/v2/flags/{projKey}/{flagKey}/triggers/{envKey} Create flag trigger
FlagTriggersApi deleteTriggerWorkflow DELETE /api/v2/flags/{projKey}/{flagKey}/triggers/{envKey}/{id} Delete flag trigger
FlagTriggersApi getTriggerWorkflowById GET /api/v2/flags/{projKey}/{flagKey}/triggers/{envKey}/{id} Get flag trigger by ID
FlagTriggersApi getTriggerWorkflows GET /api/v2/flags/{projKey}/{flagKey}/triggers/{envKey} List flag triggers
FlagTriggersApi patchTriggerWorkflow PATCH /api/v2/flags/{projKey}/{flagKey}/triggers/{envKey}/{id} Update flag trigger
IntegrationAuditLogSubscriptionsApi createSubscription POST /api/v2/integrations/{integrationKey} Create audit log subscription
IntegrationAuditLogSubscriptionsApi deleteSubscription DELETE /api/v2/integrations/{integrationKey}/{id} Delete audit log subscription
IntegrationAuditLogSubscriptionsApi getSubscriptionByID GET /api/v2/integrations/{integrationKey}/{id} Get audit log subscription by ID
IntegrationAuditLogSubscriptionsApi getSubscriptions GET /api/v2/integrations/{integrationKey} Get audit log subscriptions by integration
IntegrationAuditLogSubscriptionsApi updateSubscription PATCH /api/v2/integrations/{integrationKey}/{id} Update audit log subscription
MetricsApi deleteMetric DELETE /api/v2/metrics/{projectKey}/{key} Delete metric
MetricsApi getMetric GET /api/v2/metrics/{projectKey}/{key} Get metric
MetricsApi getMetrics GET /api/v2/metrics/{projectKey} List metrics
MetricsApi patchMetric PATCH /api/v2/metrics/{projectKey}/{key} Update metric
MetricsApi postMetric POST /api/v2/metrics/{projectKey} Create metric
OtherApi getIps GET /api/v2/public-ip-list Gets the public IP list
OtherApi getOpenapiSpec GET /api/v2/openapi.json Gets the OpenAPI spec in json
OtherApi getRoot GET /api/v2 Root resource
OtherApi getVersions GET /api/v2/versions Get version information
ProjectsApi deleteProject DELETE /api/v2/projects/{projectKey} Delete project
ProjectsApi getProject GET /api/v2/projects/{projectKey} Get project
ProjectsApi getProjects GET /api/v2/projects List projects
ProjectsApi patchProject PATCH /api/v2/projects/{projectKey} Update project
ProjectsApi postProject POST /api/v2/projects Create project
RelayProxyConfigurationsApi deleteRelayAutoConfig DELETE /api/v2/account/relay-auto-configs/{id} Delete Relay Proxy config by ID
RelayProxyConfigurationsApi getRelayProxyConfig GET /api/v2/account/relay-auto-configs/{id} Get Relay Proxy config
RelayProxyConfigurationsApi getRelayProxyConfigs GET /api/v2/account/relay-auto-configs List Relay Proxy configs
RelayProxyConfigurationsApi patchRelayAutoConfig PATCH /api/v2/account/relay-auto-configs/{id} Update a Relay Proxy config
RelayProxyConfigurationsApi postRelayAutoConfig POST /api/v2/account/relay-auto-configs Create a new Relay Proxy config
RelayProxyConfigurationsApi resetRelayAutoConfig POST /api/v2/account/relay-auto-configs/{id}/reset Reset Relay Proxy configuration key
ScheduledChangesApi deleteFlagConfigScheduledChanges DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Delete scheduled changes workflow
ScheduledChangesApi getFeatureFlagScheduledChange GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Get a scheduled change
ScheduledChangesApi getFlagConfigScheduledChanges GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes List scheduled changes
ScheduledChangesApi patchFlagConfigScheduledChange PATCH /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{id} Update scheduled changes workflow
ScheduledChangesApi postFlagConfigScheduledChanges POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes Create scheduled changes workflow
SegmentsApi deleteSegment DELETE /api/v2/segments/{projKey}/{envKey}/{key} Delete segment
SegmentsApi getExpiringUserTargetsForSegment GET /api/v2/segments/{projKey}/{segmentKey}/expiring-user-targets/{envKey} Get expiring user targets for segment
SegmentsApi getSegment GET /api/v2/segments/{projKey}/{envKey}/{key} Get segment
SegmentsApi getSegmentMembershipForUser GET /api/v2/segments/{projKey}/{envKey}/{key}/users/{userKey} Get Big Segment membership for user
SegmentsApi getSegments GET /api/v2/segments/{projKey}/{envKey} List segments
SegmentsApi patchExpiringUserTargetsForSegment PATCH /api/v2/segments/{projKey}/{segmentKey}/expiring-user-targets/{envKey} Update expiring user targets for segment
SegmentsApi patchSegment PATCH /api/v2/segments/{projKey}/{envKey}/{key} Patch segment
SegmentsApi postSegment POST /api/v2/segments/{projKey}/{envKey} Create segment
SegmentsApi updateBigSegmentTargets POST /api/v2/segments/{projKey}/{envKey}/{key}/users Update targets on a Big Segment
TeamsBetaApi deleteTeam DELETE /api/v2/teams/{key} Delete team
TeamsBetaApi getTeam GET /api/v2/teams/{key} Get team
TeamsBetaApi getTeams GET /api/v2/teams List teams
TeamsBetaApi patchTeam PATCH /api/v2/teams/{key} Update team
TeamsBetaApi postTeam POST /api/v2/teams Create team
TeamsBetaApi postTeamMembers POST /api/v2/teams/{key}/members Add members to team
UserSettingsApi getExpiringFlagsForUser GET /api/v2/users/{projKey}/{userKey}/expiring-user-targets/{envKey} Get expiring dates on flags for user
UserSettingsApi getUserFlagSetting GET /api/v2/users/{projKey}/{envKey}/{key}/flags/{featureKey} Get flag setting for user
UserSettingsApi getUserFlagSettings GET /api/v2/users/{projKey}/{envKey}/{key}/flags List flag settings for user
UserSettingsApi patchExpiringFlagsForUser PATCH /api/v2/users/{projKey}/{userKey}/expiring-user-targets/{envKey} Update expiring user target for flags
UserSettingsApi putFlagSetting PUT /api/v2/users/{projKey}/{envKey}/{key}/flags/{featureKey} Update flag settings for user
UsersApi deleteUser DELETE /api/v2/users/{projKey}/{envKey}/{key} Delete user
UsersApi getSearchUsers GET /api/v2/user-search/{projKey}/{envKey} Find users
UsersApi getUser GET /api/v2/users/{projKey}/{envKey}/{key} Get user
UsersApi getUsers GET /api/v2/users/{projKey}/{envKey} List users
UsersBetaApi getUserAttributeNames GET /api/v2/user-attributes/{projectKey}/{environmentKey} Get user attribute names
WebhooksApi deleteWebhook DELETE /api/v2/webhooks/{id} Delete webhook
WebhooksApi getAllWebhooks GET /api/v2/webhooks List webhooks
WebhooksApi getWebhook GET /api/v2/webhooks/{id} Get webhook
WebhooksApi patchWebhook PATCH /api/v2/webhooks/{id} Update webhook
WebhooksApi postWebhook POST /api/v2/webhooks Creates a webhook
WorkflowsBetaApi deleteWorkflow DELETE /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows/{workflowId} Delete workflow
WorkflowsBetaApi getCustomWorkflow GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows/{workflowId} Get custom workflow
WorkflowsBetaApi getWorkflows GET /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows Get workflows
WorkflowsBetaApi postWorkflow POST /api/v2/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/workflows Create workflow

Models

Authorization

ApiKey

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

Tests

To run the tests, use:

composer install
vendor/bin/phpunit

Author

support@launchdarkly.com

About this package

This PHP package is automatically generated by the OpenAPI Generator project:

  • API version: 2.0
    • Package version: 7.1.1
  • Build package: org.openapitools.codegen.languages.PhpClientCodegen