Skip to main content
LaunchDarkly logo
  • Category: developer tools
  • Auth: API_KEY, OAUTH2
  • Composio-managed OAuth available? No
  • Tools: 248
  • Triggers: 16
  • Slug: LAUNCH_DARKLY
  • Version: 20261101_00

Tools

Slug: LAUNCH_DARKLY_ADD_MEMBER_TO_TEAMSTool to add a LaunchDarkly member to one or more teams. Use when you need to grant a member access to specific teams within your organization.

Input Parameters

string
required
The unique member ID. This is the member’s identifier in LaunchDarkly.
array
required
List of team keys to add the member to. Each team key must be a valid, existing team in your LaunchDarkly organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_APPLY_APPROVAL_REQUESTTool to apply an approved approval request in LaunchDarkly. Use when you need to execute changes that have been approved.

Input Parameters

string
required
The approval request ID to apply. Example: ‘697ca5410a055f0a0a8079d6’
string
Optional comment about the approval request application.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_APPLY_APPROVAL_REQUEST_FOR_FLAGTool to apply an approved approval request for a feature flag in LaunchDarkly. Use when you need to execute changes that have been approved for a specific flag in an environment.

Input Parameters

string
required
The unique identifier (ID) of the approval request to apply. This ID is returned when creating an approval request or can be found using the approval requests API.
string
Optional comment about the approval request application.
string
required
The unique key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the approval request is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the approval request to apply.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_COPY_FEATURE_FLAGTool to copy a feature flag’s configuration from one environment to another within the same project. Use when you need to replicate flag settings across environments, such as promoting configurations from test to production.

Input Parameters

object
required
The source environment from which to copy the feature flag configuration.
object
required
The target environment to which to copy the feature flag configuration.
string
Optional comment describing the purpose of this copy operation.
string
required
The project key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
array
Optional list of flag changes NOT to copy from source to target. You may include either includedActions or excludedActions, but not both. If neither is provided, all flag changes will be copied.
array
Optional list of flag changes to copy from source to target. You may include either includedActions or excludedActions, but not both. If neither is provided, all flag changes will be copied.
string
required
The feature flag key. The key identifies the flag in your code.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_ANNOUNCEMENT_PUBLICTool to create a public announcement in LaunchDarkly. Use when you need to notify users about system maintenance, important updates, or critical information. Announcements can be scheduled to appear at specific times and optionally set to auto-expire.

Input Parameters

string
required
The title of the announcement. This will be displayed as the heading of the announcement.
integer
The end time of the announcement. This is a Unix timestamp in milliseconds. The announcement will automatically hide after this time. If not provided, the announcement will remain visible until manually removed.
string
required
The message content of the announcement. Supports markdown formatting for rich text display.
string ("info" | "warning" | "critical")
required
The severity level of the announcement. This affects how the announcement is displayed to users.
integer
required
The start time of the announcement. This is a Unix timestamp in milliseconds. The announcement will be visible starting from this time.
boolean
required
Whether users can dismiss the announcement. If true, users can close the announcement; if false, it will be shown until it expires.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_APPROVAL_REQUESTTool to create an approval request in LaunchDarkly. Use when you need to request approval for flag changes before they are applied. The request requires a resource ID, description, and a list of instructions in semantic patch format.

Input Parameters

string
Optional comment providing additional context about the approval request.
string
required
String representation of the resource specifier. Format: proj/{projectKey}:env/:flag/{flagKey}. Note: The environment portion must use wildcard '' for all environments. Example: ‘proj/default:env/*:flag/sample-feature’
string
required
A brief description of the changes being requested in this approval request.
array
required
Array of instruction objects in semantic patch format. Each instruction must have a ‘kind’ property specifying the operation type. Supported kinds: addVariation, removeVariation, updateVariation, updateDefaultVariation.
array
Array of team keys whose members should be notified to review this approval request.
array
Array of member IDs to notify for reviewing this approval request. These members will receive notifications to review the request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_FOR_FLAGTool to create an approval request for a feature flag in LaunchDarkly. Use when you need to request approval for changes to a feature flag before applying them. Approval requests enable workflow controls and review processes for flag changes.

Input Parameters

string
Optional comment describing the approval request in more detail.
string
required
A brief description of the changes you’re requesting. This helps reviewers understand what the approval request is for.
string
required
The unique key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
array
required
An array of instruction objects defining the changes to be made to the flag. Each instruction must have a ‘kind’ field. Common kinds include: ‘turnFlagOn’, ‘turnFlagOff’, ‘updateFallthrough’, ‘updateTargets’, etc. Example: [{‘kind’: ‘turnFlagOn’}]
integer
Unix timestamp (in milliseconds) for when the approval should be executed. If not provided, the approval will be executed immediately upon approval.
string
required
The environment key where the approval request will be created (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
The ID of a scheduled change. Include this if your instructions include editing or deleting a scheduled change.
string
required
The unique key of the feature flag for which to create an approval request.
array
An array of team keys. The members of these teams are notified to review the approval request.
array
An array of member IDs. These members are notified to review the approval request.
object
Optional integration configuration object for external approval systems.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_REVIEWTool to review an approval request by approving, declining, or commenting on changes. Use when you need to provide feedback or make a decision on a pending approval request in LaunchDarkly.

Input Parameters

string
required
The approval request ID to review. Example: ‘6990dd06e218990a1077bc26’
string ("approve" | "comment" | "decline")
required
The type of review for this approval request. Use ‘approve’ to approve the changes, ‘decline’ to reject them, or ‘comment’ to add feedback without approving or declining.
string
Optional comment about the approval request. Provide context, reasoning, or feedback for your review decision.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_REVIEW_FOR_FLAGTool to review an approval request for a feature flag by approving, declining, or commenting on the changes. Use when you need to provide feedback or make a decision on a pending flag approval request.

Input Parameters

string
required
The unique identifier of the approval request to review.
string ("approve" | "comment" | "decline")
required
The type of review for this approval request: ‘approve’ to approve changes, ‘decline’ to reject changes, or ‘comment’ to add comments without approval decision.
string
Optional comment about the approval request review.
string
required
The project key identifying the project containing the feature flag.
string
required
The environment key where the approval request is configured (e.g., ‘test’, ‘production’).
string
required
The feature flag key identifying the specific flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_BIG_SEGMENT_EXPORTCreate an export for a big segment in LaunchDarkly, such as a synced segment or a list-based segment with 15,000+ entries. When available, the returned export ID can be used to check export status.

Input Parameters

string
required
The project key identifying the project containing the segment. Use ‘List Projects’ action to find available project keys.
string
required
The segment key identifying the specific big segment to export. Big segments are synced segments or list-based segments with 15,000+ entries.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_BIG_SEGMENT_STORE_INTEGRATIONTool to create a persistent store integration for big segments in LaunchDarkly. Use when you need to set up a new Redis or DynamoDB integration for syncing large list-based segments. This integration is required for server-side SDKs to evaluate segments synced from external tools.

Input Parameters

boolean
Whether the integration configuration is active. Default value is false if not specified.
string
Human-readable name to identify the integration. If not provided, a default name will be assigned.
array
List of tags to associate with the integration for organization and filtering.
object
required
Configuration settings for the integration. For Redis: required field is ‘host’ (string), optional fields are ‘port’ (string, e.g., ‘6379’), ‘username’ (string), ‘password’ (string), ‘tlsEnabled’ (bool). For DynamoDB: required fields vary based on AWS setup (table name, region, role ARN, etc.).
string
required
The project key identifying the project for the integration. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the integration will be configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string ("redis" | "dynamodb")
required
The type of big segment store integration to create, either ‘redis’ or ‘dynamodb’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_CUSTOM_ROLETool to create a new custom role in LaunchDarkly. Use when you need to define a custom set of permissions for members or teams. The role must have a unique key and at least one policy statement defining the allowed or denied actions.

Input Parameters

string
required
The custom role key. Must be unique within the account.
string
required
A human-friendly name for the custom role.
array
required
An array of policy statements that define the permissions for this custom role. Each statement must have an ‘effect’ and can specify ‘resources’, ‘actions’, ‘notResources’, or ‘notActions’.
string
Description of the custom role.
string
Legacy base permissions for the role. This field is deprecated and should not be used for new roles.
string ("organization" | "project" | "any")
Category of resources this role applies to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_DESTINATIONTool to create a new Data Export destination for exporting LaunchDarkly event data to external services. Use when you need to set up integrations with services like Kinesis, Google PubSub, Azure Event Hubs, or other supported destinations.

Input Parameters

boolean
Whether the export should be enabled immediately after creation. Displayed as the integration status in the LaunchDarkly UI. Defaults to false if not specified.
string ("google-pubsub" | "kinesis" | "mparticle" | "segment" | "azure-event-hubs" | "snowflake-v2" | "databricks" | "bigquery" | "redshift")
required
The type of Data Export destination. Each destination type requires specific configuration parameters in the ‘config’ field.
string
required
A human-readable name for your Data Export destination.
object
required
Configuration parameters required for the destination type. For Kinesis: requires ‘region’, ‘roleArn’, ‘streamName’. For Google PubSub: requires ‘project’, ‘topic’. For Azure Event Hubs: requires ‘namespace’, ‘name’, ‘policyName’, ‘policyKey’. Configuration varies by destination kind.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the destination should be created (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_ENVIRONMENTTool to create a new environment within a LaunchDarkly project. Use when you need to add a new environment such as development, staging, or production.

Input Parameters

string
required
A project-unique key for the new environment. Must be unique within the project.
string
required
A human-friendly name for the new environment.
array
Tags to apply to the new environment.
string
required
A color to indicate this environment in the UI. Provide as a hex color code without the # symbol.
object
Source environment configuration for cloning.
boolean
Whether the environment is critical (e.g., production environments).
integer
The default time (in minutes) that the PHP SDK can cache feature flag rules locally.
string
required
The project key identifying the project where the environment will be created. Use LIST_PROJECTS to discover available project keys.
boolean
Ensures that one end user of the client-side SDK cannot inspect the variations for another end user.
boolean
Requires confirmation for all flag and segment changes via the UI in this environment.
boolean
Requires comments for all flag and segment changes via the UI in this environment.
boolean
Enables tracking detailed information for new flags by default.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_EXPERIMENTTool to create a new experiment in LaunchDarkly. Use when you need to set up A/B tests or multivariate experiments to measure the impact of feature flag variations on specified metrics.

Input Parameters

string
required
The unique key for the experiment. This key is used to reference the experiment in API calls and must be unique within the project and environment.
string
required
The human-readable name of the experiment.
array
Tags for the experiment to help with organization and filtering.
string
The ID of the holdout to associate with this experiment.
object
required
The initial iteration configuration for the experiment. This defines the hypothesis, metrics, treatments, and flags for the experiment.
string
required
The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys.
string
A detailed description of the experiment.
string
The ID of the member who maintains this experiment. If not provided, the creator will be set as the maintainer.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_EXTINCTIONTool to create new extinction events for feature flags in LaunchDarkly. Use when you need to record that a feature flag has been removed from the codebase. Extinction events track when flags are no longer referenced in code.

Input Parameters

string
required
The repository name. This is the name of the code reference repository configured in LaunchDarkly.
string
required
The branch name. Branch names with special characters like slashes will be automatically URL-encoded.
array
required
Array of extinction event objects to create. Each object represents a flag that has been removed from the codebase.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_FEATURE_FLAGTool to create a new feature flag in LaunchDarkly. Use when you need to create a feature flag with a name, key, and optional variations. Supports creating both standard and migration flags.

Input Parameters

string
required
A unique key used to reference the flag in your code. Must be unique within the project.
string
required
A human-friendly name for the feature flag.
array
Tags for the feature flag. Defaults to an empty array.
string
The key of the feature flag to be cloned. Setting this copies the full targeting configuration for all environments from the original flag to the new flag.
string ("migration" | "holdout")
Purpose of the feature flag.
object
Default variation settings for a feature flag.
boolean
Whether to automatically turn the flag on across all environments at creation. Defaults to false.
boolean
Whether the flag is a temporary flag. Defaults to true.
string
required
The project key identifying the LaunchDarkly project where the flag will be created. Use ‘List Projects’ action to find available project keys.
array
An array of possible variations for the flag. If omitted, two boolean variations of true and false will be used.
string
Description of the feature flag. Defaults to an empty string.
string
The ID of the member who maintains this feature flag.
object
Custom properties for the feature flag.
string
The key of the team that maintains this feature flag.
object
Migration settings for a feature flag.
array
Initial set of prerequisite flags for all environments.
object
Client-side availability settings for a feature flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_FLAG_CONFIG_SCHEDULED_CHANGESTool to create a scheduled changes workflow for a feature flag in LaunchDarkly. Scheduled changes allow you to plan flag configuration updates for a future time. Use when you need to automate flag changes at a specific date/time.

Input Parameters

string
Optional comment describing the purpose of these scheduled changes.
string
required
The unique key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
array
required
List of instructions to execute at the scheduled time. Each instruction must have a ‘kind’ field (e.g., ‘turnFlagOn’, ‘turnFlagOff’).
integer
required
Unix timestamp in milliseconds indicating when the scheduled changes should be executed.
string
required
The environment key where the scheduled changes will be applied (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag to schedule changes for.
boolean
Whether to succeed (true) or fail (false) when these instructions conflict with existing scheduled changes. If not specified, conflicts will cause the request to fail.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_FLAG_COPY_CONFIG_APPROVAL_REQUESTTool to create an approval request for copying a feature flag’s configuration from one environment to another. Use when you need to promote flag settings across environments with approval workflow.

Input Parameters

object
required
The source environment from which to copy the flag configuration.
string
Optional comment providing additional context about the approval request.
string
required
A brief description of the changes and reason for copying the flag configuration. This helps reviewers understand the purpose of the approval request.
string
required
The project key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
string
required
The environment key for the target environment where the flag configuration will be copied to (e.g., ‘production’). Use ‘Get Environments’ action to list available environments.
array
Optional list of flag changes NOT to copy from the source environment to the target environment. You may include either ‘included_actions’ or ‘excluded_actions’, but not both. If neither are included, all flag changes will be copied.
string
required
The unique key of the feature flag whose configuration will be copied.
array
Optional list of specific flag changes to copy from the source environment to the target environment. You may include either ‘included_actions’ or ‘excluded_actions’, but not both. If neither are included, all flag changes will be copied.
array
An array of team keys whose members will be notified to review the approval request.
array
An array of member IDs to notify for reviewing the approval request. These members will receive notifications to review and approve/decline the request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_FLAG_IMPORT_CONFIGURATIONTool to create a new flag import configuration for importing feature flags from external feature management systems like Split or Unleash. Use when setting up automated flag synchronization from another platform into LaunchDarkly. The config object structure varies by integration key.

Input Parameters

string
required
Human-readable name to identify the flag import configuration.
array
List of tags to associate with the flag import configuration for organization and filtering.
object
required
Configuration object containing integration-specific settings. The structure varies based on the integration_key. For ‘split’: requires ‘workspaceId’, ‘workspaceApiKey’, ‘environmentId’, ‘ldApiKey’, ‘ldMaintainer’, ‘ldTag’, and optional ‘splitTag’. For ‘unleash’: check the integration’s formVariables in manifest.json.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string ("split" | "unleash")
required
The integration key identifying the feature management system from which the import occurs. Choose ‘SPLIT’ for Split.io or ‘UNLEASH’ for Unleash.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_HOLDOUTTool to create a new holdout in LaunchDarkly for experiment control groups. Use when you need to create a holdout to measure the impact of features against a control group. Requires LD-API-Version: beta header.

Input Parameters

string
required
A unique key that identifies the holdout. This key must be unique within the project and environment.
string
required
A human-friendly name for the holdout. This will be displayed in the LaunchDarkly UI.
array
Details on the metrics for this holdout. If not specified, only the primary metric will be included. Each metric must have a ‘key’ field.
array
The attributes that the holdout iteration’s results can be sliced by. These should be context attributes that exist in your LaunchDarkly environment.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
An optional description of the holdout. Provides additional context about the holdout’s purpose.
string
required
The ID of the member who will maintain this holdout. Use GET_MEMBERS to find valid member IDs.
string
Audience allocation for the holdout as a percentage string. For example, ‘10’ means 10% of traffic is allocated to the holdout. If not specified, defaults to a value set by LaunchDarkly.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The key of the primary metric for this holdout. This metric must already exist in the project. Use LIST_METRICS to discover available metrics.
string
required
The chosen randomization unit for the holdout base experiment. This determines how traffic is allocated. Common values: ‘user’, ‘device’, ‘session’.
string
required
The key of the flag that the holdout is dependent on. This flag must already exist and have purpose ‘holdout’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_INTEGRATION_CONFIGURATIONTool to create a new integration configuration in LaunchDarkly. Use when you need to set up automated workflows with external services like Slack, Datadog, Jira, custom webhooks, or other third-party integrations. Note: This endpoint requires the ‘LD-API-Version: beta’ header which is automatically included.

Input Parameters

string
required
The name of the integration configuration. This is a human-readable label to identify the configuration.
array
Tags for the integration configuration. Use tags to organize and categorize integrations.
boolean
Whether the integration configuration should be enabled. If omitted, defaults to true.
object
required
The unique set of fields required to configure the integration. The required fields vary by integration type. Refer to the ‘formVariables’ field in the corresponding manifest.json at https://github.com/launchdarkly/integration-framework/tree/main/integrations for the specific fields needed for your integration.
string
required
The integration key identifying the type of integration. Common values include ‘slack’, ‘datadog’, ‘jira’, ‘custom-approvals’, ‘webhook’, etc. This must match an available integration in LaunchDarkly’s integration framework.
object
Configuration for integration capabilities.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_ITERATIONTool to create a new iteration for an experiment in LaunchDarkly. Use when you need to set up a new experiment iteration with specific hypothesis, metrics, treatments (variations), and feature flag configurations.

Input Parameters

object
required
Dictionary mapping flag keys to their configuration for this experiment. Keys are flag keys, values are flag configuration objects.
array
required
List of metrics to track in this iteration. At least one metric must be specified, and one should be marked as primary.
array
The attributes that this iteration’s results can be sliced by for analysis.
string
required
The hypothesis for this experiment iteration - the expected outcome you’re testing.
string
required
The project key identifying the LaunchDarkly project containing the experiment. Use LIST_PROJECTS to discover available project keys.
array
required
List of treatment groups for the experiment. Must include at least 2 treatments, and exactly one must be marked as baseline.
string
required
The unique key identifying the experiment to add this iteration to. Use GET_EXPERIMENTS to discover available experiment keys.
string
required
The environment key where the experiment iteration will be created. Common values include ‘production’, ‘staging’, ‘test’.
string
The key of the primary funnel (metric group) for this experiment. Either this or primarySingleMetricKey must be specified.
string
The unit of randomization for this iteration. Defaults to ‘user’.
boolean
Whether to allow the experiment to reassign traffic to different variations when you increase or decrease the traffic in your experiment audience (true) or keep all traffic assigned to its initial variation (false). Defaults to true.
string
The key of the primary single metric for this experiment. Either this or primaryFunnelKey must be specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_LAYERTool to create a new layer in a LaunchDarkly project. Use when you need to set up a new layer for organizing experiments.

Input Parameters

string
required
Unique identifier for the layer. Must be unique within the project.
string
required
Human-readable name for the layer.
string
required
The project key identifying the LaunchDarkly project where the layer will be created. Use LIST_PROJECTS to discover available project keys.
string
required
Description explaining the purpose and usage of the layer.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_MEMBERSTool to invite one or more new members to join a LaunchDarkly account. Use when you need to add new team members. Each member receives an invitation email and must have an email address and either a role or customRoles.

Input Parameters

array
required
Array of new members to invite. Each member must have an email and either a role or customRoles.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_METRICTool to create a new metric in LaunchDarkly. Use when you need to define a new metric for tracking pageviews, clicks, or custom events in experiments.

Input Parameters

string
required
A unique key to reference the metric
string ("pageview" | "click" | "custom")
required
The kind of event your metric will track
string
A human-friendly name for the metric
array
Tags for the metric
string
The unit of measure. Applicable for numeric custom metrics only.
array
One or more target URLs. Required for click and pageview metrics only.
object
Filter configuration for the metric.
string
The event key to use in your code. Required for custom conversion/binary and custom numeric metrics only.
string
One or more CSS selectors. Required for click metrics only.
boolean
Whether to track numeric changes in value against a baseline (true) or to track a conversion when an end user takes an action (false). Required for custom metrics only.
object
Data source configuration for a metric.
string
required
The project key identifying the project where the metric will be created. Use LIST_PROJECTS to discover available project keys.
string
Description of the metric
string ("mean" | "percentile")
The method for analyzing metric events.
object
Default event configuration.
string
The ID of the member who maintains this metric
integer
The percentile for the analysis method. An integer denoting the target percentile between 0 and 100. Required when analysisType is percentile.
string ("HigherThanBaseline" | "LowerThanBaseline")
Success criteria for custom metrics.
array
An array of randomization units allowed for this metric
string ("average" | "sum")
The method by which multiple unit event values are aggregated.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_METRIC_GROUPTool to create a new metric group in LaunchDarkly. Use when you need to organize multiple metrics together for experiments or analysis. Metric groups must contain at least 2 metrics.

Input Parameters

string
required
A unique key to reference the metric group
string ("funnel" | "standard" | "guardrail")
required
The type of the metric group
string
required
A human-friendly name for the metric group
array
required
Tags for the metric group
array
required
An ordered list of the metrics in this metric group. Must contain at least 2 metrics.
string
required
The project key identifying the project where the metric group will be created. Use LIST_PROJECTS to discover available project keys.
string
Description of the metric group
string
required
The ID of the member who maintains this metric group. Use GET_MEMBERS to find available member IDs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_MIGRATION_SAFETY_ISSUESTool to check migration safety issues for a feature flag patch. Returns safety issues associated with the provided semantic patch instructions. Use when you need to validate if flag changes will cause migration issues before applying them.

Input Parameters

string
Optional comment providing additional context for the patch. Useful for documentation and audit trails.
string
required
The migration flag key identifying the specific flag to check for safety issues.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
array
required
Array of semantic patch instructions for the flag. Each instruction must have a ‘kind’ field specifying the operation type. These are the same instructions that are valid for feature flags. Common kinds include ‘turnFlagOn’, ‘turnFlagOff’, ‘addRule’, ‘removeRule’, ‘updateFallthroughVariationOrRollout’, etc.
string
required
The environment key where the migration safety check will be performed (e.g., ‘production’, ‘staging’). Use GET_ENVIRONMENTS to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_O_AUTH2_CLIENTTool to create (register) a LaunchDarkly OAuth 2.0 client. Use when you need to build custom integrations using LaunchDarkly as your identity provider. The client secret is only returned upon creation, so save it securely.

Input Parameters

string
required
The name of your new LaunchDarkly OAuth 2.0 client.
string
Description of your OAuth 2.0 client.
string
required
The redirect URI for your new OAuth 2.0 application. This should be an absolute URL conforming with the standard HTTPS protocol.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_PROJECTTool to create a new project with the given key and name. Project keys must be unique within an account. Use when you need to set up a new project in LaunchDarkly.

Input Parameters

string
required
A unique key used to reference the project in your code. Project keys must be unique within an account.
string
required
A human-friendly name for the project.
array
Tags for the project.
array
Creates the provided environments for this project. If omitted default environments will be created instead.
object
Naming convention settings for flag keys in the project.
boolean
Whether or not flags created in this project are made available to the client-side JavaScript SDK by default.
object
Client-side SDK availability settings for the project.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_RELAY_AUTO_CONFIGTool to create a new Relay Proxy configuration in LaunchDarkly. Use when you need to set up a new Relay Proxy with specific access policies for environments and projects. The response includes the full configuration key which is only shown once.

Input Parameters

string
required
A human-friendly name for the Relay Proxy configuration. This will help identify the configuration in the LaunchDarkly UI.
array
required
An array of policy statements that define what environments and projects the Relay Proxy should include or exclude. Each statement must have an ‘effect’ field and optionally ‘resources’ and ‘actions’ fields. To learn more, read the LaunchDarkly documentation on inline policies.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_RELEASE_FOR_FLAGTool to create a release by adding a flag to a release pipeline in LaunchDarkly. Use when you need to add a feature flag to a release pipeline for progressive rollout across multiple phases.

Input Parameters

string
required
The unique key of the feature flag to add to the release pipeline.
string
required
The unique key identifying the LaunchDarkly project containing the flag. Use ‘List Projects’ action to find available project keys.
string
required
The key of the release pipeline to attach the flag to. Use ‘Get All Release Pipelines’ action to find available pipeline keys.
string
The variation ID to release across all phases. If not specified, the default variation will be used.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_RELEASE_PIPELINETool to create a release pipeline in LaunchDarkly. Release pipelines standardize and automate the feature flag release process across a series of phases. Use when you need to set up a structured rollout process.

Input Parameters

string
required
A unique identifier for the release pipeline. This must be unique within the project.
string
required
A human-friendly name for the release pipeline.
array
Tags for organizing and categorizing the release pipeline.
array
required
An ordered list of release pipeline phases. Each phase is a logical grouping of one or more environments that share attributes for rolling out changes.
boolean
Whether the pipeline is enabled for Release Automation.
string
A description of the release pipeline.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
boolean
Whether this pipeline should be set as the default pipeline for the project.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_RELEASE_POLICYTool to create a new release policy for a specified project. Use when you need to set up release automation policies for progressive or guarded rollouts. Requires beta API version header.

Input Parameters

string
required
A unique key used to reference the release policy. Must be unique within the project.
string
required
A human-friendly name for the release policy.
object
Target environments and flag tags for a release policy.
string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.
string ("guarded-release" | "progressive-release")
required
The release method for this policy: ‘guarded-release’ monitors metrics during rollout, ‘progressive-release’ follows staged rollout without metric monitoring.
object
Configuration for guarded release policies.
object
Configuration for progressive release policies.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_REPOSITORYTool to create a code reference repository with the specified name. Use when you need to set up a new repository for code reference scanning in LaunchDarkly. This enables tracking of feature flag usage across your codebase.

Input Parameters

string
required
The repository name.
string ("bitbucket" | "custom" | "github" | "gitlab")
Enum for supported repository types.
A URL to access the repository.
string
The repository’s default branch. If not specified, the default value is ‘main’.
string
A template for constructing a valid URL to view the hunk.
string
A template for constructing a valid URL to view the commit.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_SEGMENTTool to create a new segment in LaunchDarkly. Segments are groups of contexts that you can use to manage flag targeting rules. Use when you need to organize users, devices, or other contexts into logical groups for feature flag targeting.

Input Parameters

string
required
A unique key used to reference the segment. Must be unique within the project and environment. Use lowercase letters, numbers, dots, hyphens, and underscores.
string
required
A human-friendly name for the segment. This is displayed in the LaunchDarkly UI.
array
Tags for organizing and filtering segments. Use tags to categorize segments for easier management.
boolean
Whether to create a standard segment (false) or a big segment (true). Standard segments include rule-based and smaller list-based segments. Big segments include larger list-based segments and synced segments. Only use a big segment if you need to add more than 15,000 individual targets.
string
A description of the segment’s purpose. Helps document why the segment exists and how it should be used.
string
required
The project key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the segment will be created (e.g., ‘production’, ‘staging’). Use ‘Get Environments’ action to list available environments.
string
For big segments, the targeted context kind (e.g., ‘user’, ‘device’). Required when unbounded is true.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_SUBSCRIPTIONTool to create a new audit log subscription for forwarding LaunchDarkly audit events to external services. Use when you need to set up integrations with monitoring or logging platforms like Datadog, Splunk, Elastic, or Microsoft Teams to receive real-time audit log notifications.

Input Parameters

boolean
Whether you want your subscription to actively send events immediately after creation. If true, the subscription will begin forwarding audit log events to the configured destination. If false or omitted, the subscription will be created but will not send events until enabled.
string
Slack webhook receiver URL. This field is only necessary for legacy Slack webhook integrations and should not be used for other integration types.
string
required
A human-friendly name for your audit log subscription. This name helps identify the subscription in the LaunchDarkly UI and API responses.
array
An array of tags for organizing and filtering this subscription. Tags can be used for categorization, filtering, and management of multiple subscriptions.
string
Datadog API key. This field is only necessary for legacy Datadog webhook integrations and should not be used for other integration types. For modern integrations, include the API key in the ‘config’ field instead.
object
required
The unique set of fields required to configure an audit log subscription integration of this type. Configuration fields vary by integration type. For example, Datadog requires ‘apiKey’, while other integrations may require different fields like ‘url’, ‘token’, or service-specific credentials. Refer to the integration’s manifest.json at https://github.com/launchdarkly/integration-framework/tree/main/integrations for a full list of required and optional fields for your chosen integration.
array
An array of policy statements defining which audit log events this subscription should receive. Each statement uses a custom role policy format with ‘effect’, ‘resources’, and optionally ‘actions’, ‘notResources’, and ‘notActions’. This allows fine-grained control over which resource types and actions trigger notifications. See https://launchdarkly.com/docs/home/account/role-concepts for more details on custom role policies.
string
required
The integration key identifying the type of audit log subscription to create (e.g., ‘datadog’, ‘dynatrace’, ‘elastic’, ‘honeycomb’, ‘logdna’, ‘msteams’, ‘new-relic-apm’, ‘signalfx’, ‘splunk’). This key determines which external service will receive the audit log events.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_TEAMTool to create a new team in LaunchDarkly. Use when you need to set up a new team for organizing members and managing permissions. To learn more, read Creating a team documentation.

Input Parameters

string
required
The unique key to identify the team. Must be unique within the account.
string
required
A human-friendly name for the team.
string
A comma-separated list of properties that can reveal additional information in the response. Options: ‘members’ (includes member details), ‘roles’ (includes custom roles), ‘projects’ (includes projects with write access), ‘maintainers’ (includes maintainer list). Example: ‘members,maintainers’.
array
A list of member IDs who will belong to the team.
string
A description of the team’s purpose and responsibilities.
array
List of custom role keys that the team will have access to.
object
Custom role attributes assigned to the team.
array
A list of permission grants. Permission grants allow access to a specific action, without having to create or update a custom role.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOWCreates a flag trigger workflow in LaunchDarkly. Flag triggers allow you to automatically toggle feature flags on or off in response to external events (e.g., monitoring alerts from Datadog, Honeycomb, or custom webhooks). The trigger generates a unique URL that can be called to execute the configured flag action.

Input Parameters

string
An optional comment describing the purpose of this trigger for documentation
string
required
The unique key identifying the LaunchDarkly project
array
List of flag actions to execute when the trigger fires. Each instruction specifies what action to take (turnFlagOn or turnFlagOff)
string
required
The environment key where the trigger will be active (e.g., ‘production’, ‘test’)
string
The integration identifier for the trigger. Use ‘generic-trigger’ for custom webhooks, or specific integration keys like ‘datadog’, ‘honeycomb’, ‘dynatrace’ for supported integrations
string
required
The unique key identifying the feature flag to attach the trigger to

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_WEBHOOKTool to create a new webhook in LaunchDarkly. Use when you need to set up HTTP callbacks to receive notifications about events in your LaunchDarkly environment.

Input Parameters

boolean
required
Whether this webhook is enabled. Set to true to activate the webhook immediately.
string
required
The URL of the remote webhook endpoint. LaunchDarkly will send HTTP POST payloads to this URL when events occur.
string
A human-readable name for your webhook. Helps identify the webhook’s purpose in the LaunchDarkly UI.
boolean
required
Whether to sign webhook requests with a signature header. If true and no secret is provided, LaunchDarkly will automatically generate a secret.
array
List of tags for organizing and categorizing this webhook.
string
Secret key for signing webhook requests. Only used if ‘sign’ is true. If omitted when ‘sign’ is true, LaunchDarkly generates a secret automatically.
array
Custom role policy statements that define which resource kinds and actions trigger this webhook. If omitted, the webhook responds to all events.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_WORKFLOWTool to create a workflow in LaunchDarkly for automating flag changes. Use when you need to schedule flag changes or set up approval-based flag management. Workflows can execute flag actions based on time schedules or approval conditions.

Input Parameters

string
required
Human-readable name for the workflow
array
required
List of workflow stages. At least one stage is required. Each stage contains conditions and actions.
boolean
Whether to call the endpoint in dry-run mode to validate without creating
string
Detailed description of what the workflow does
string
required
The project key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
The template key to apply as a starting point for the new workflow (query parameter)
string
required
The environment key where the workflow will run (e.g., ‘test’, ‘production’)
string
required
The feature flag key that this workflow will manage

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_CREATE_WORKFLOW_TEMPLATETool to create a workflow template in LaunchDarkly. Workflow templates provide reusable patterns for common flag change workflows. Use when you need to standardize workflow processes across teams or projects. Either provide an existing workflowId to convert a workflow into a template, or provide stages with flagKey and environmentKey to define a new template from scratch.

Input Parameters

string
required
Unique identifier for the workflow template. Must be unique across all templates in the account.
string
Human-readable name for the workflow template
array
List of workflow stages defining the template. Either workflowId or stages must be provided. When stages is provided, flagKey and environmentKey are also required.
string
The feature flag key to associate with the template. Required when stages is provided.
string
The project key to associate with the template
string
ID of an existing workflow to use as the basis for this template. Either workflowId or stages must be provided.
string
Detailed description of what the workflow template does and when to use it
string
The environment key to associate with the template. Required when stages is provided.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_ANNOUNCEMENT_PUBLICTool to permanently delete an announcement from LaunchDarkly. Use when you need to remove an announcement that is no longer needed. Once deleted, the announcement cannot be recovered.

Input Parameters

string
required
The unique identifier of the announcement to delete. This ID is returned when creating an announcement or can be retrieved by listing announcements.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_APPROVAL_REQUESTTool to delete an approval request in LaunchDarkly. Use when you need to remove a pending or declined approval request. Once deleted, the approval request cannot be recovered.

Input Parameters

string
required
The unique identifier (ID) of the approval request to delete. This is the approval request ID returned when creating or listing approval requests.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_APPROVAL_REQUEST_FOR_FLAGPermanently deletes an approval request for a feature flag in LaunchDarkly. Approval requests allow teams to review and approve flag changes before they are applied. Once deleted, the approval request cannot be recovered. Ensure you have the correct approval request ID before proceeding.

Input Parameters

string
required
The unique identifier (ID) of the approval request to delete. This ID is returned when creating an approval request or can be found using the approval requests API.
string
required
The unique key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the approval request is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the approval request to delete.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_BIG_SEGMENT_STORE_INTEGRATIONTool to permanently delete a persistent store integration for big segments. Each integration uses either Redis or DynamoDB. Use when you need to remove a big segment store configuration from an environment.

Input Parameters

string
required
The project key identifying the project containing the integration. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the big segment store integration to delete.
string
required
The environment key where the integration is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string ("redis" | "dynamodb")
required
The type of big segment store integration, either ‘redis’ or ‘dynamodb’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_BRANCHESAsynchronously deletes multiple branches from a LaunchDarkly code reference repository. Use this tool to clean up old or unused branches from your code reference configuration. The operation is asynchronous - branches are queued for deletion rather than deleted immediately.

Input Parameters

string
required
The repository name to delete branches for. This is the name of the code reference repository configured in LaunchDarkly.
array
required
Array of branch names to delete from the repository. Each branch name should be a string.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_CUSTOM_ROLEPermanently deletes a custom role from LaunchDarkly. Once deleted, the role cannot be recovered and will be removed from all members and teams it was assigned to. Ensure you have the correct role key before proceeding.

Input Parameters

string
required
The unique key identifying the custom role to delete. This is the key used when the role was created (not the role name or ID).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_DESTINATIONPermanently deletes a Data Export destination from LaunchDarkly. Data Export destinations allow you to export event data to external services. Once deleted, the destination cannot be recovered. Ensure you have the correct destination ID before proceeding.

Input Parameters

string
required
The unique identifier (ID) of the Data Export destination to delete. This ID is returned when creating a destination or can be found by listing destinations.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the destination is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_ENVIRONMENTTool to permanently delete an environment from a LaunchDarkly project. Once deleted, the environment and its configuration cannot be recovered. Ensure you have the correct project and environment keys before proceeding.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the environment. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the environment to delete (e.g., ‘test’, ‘staging’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_FEATURE_FLAGTool to permanently delete a feature flag from LaunchDarkly. Use when you need to remove a feature flag that is no longer needed. Once deleted, the flag cannot be recovered.

Input Parameters

string
required
The project key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
string
required
The feature flag key identifying the flag to delete. The key identifies the flag in your code.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_FLAG_CONFIG_SCHEDULED_CHANGESTool to delete scheduled changes workflow for a feature flag in LaunchDarkly. Scheduled changes allow you to plan flag configuration updates for a future time. Once deleted, the scheduled changes cannot be recovered.

Input Parameters

string
required
The unique identifier (ID) of the scheduled change to delete. This ID is returned when creating a scheduled change or can be found using the flag’s scheduled changes endpoint.
string
required
The unique key identifying the LaunchDarkly project containing the feature flag. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the scheduled changes are configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the scheduled changes to delete.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_FLAG_IMPORT_CONFIGURATIONTool to delete a flag import configuration by ID. The integration key identifies the feature management system from which the import occurs (e.g., ‘split’). This action requires the LD-API-Version: beta header.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the flag import configuration to delete.
string
required
The integration key identifying the feature management system from which the import occurs (e.g., ‘split’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_INTEGRATION_CONFIGURATIONPermanently deletes an integration configuration from LaunchDarkly. Integration configurations enable automated workflows with external services like Slack, Datadog, or custom webhooks. Once deleted, the configuration cannot be recovered.

Input Parameters

string
required
The unique ID of the integration configuration to delete. This is returned when creating an integration configuration or can be found by listing existing integration configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_MEMBERTool to permanently delete an account member from LaunchDarkly. Use when you need to remove a member’s access to the organization. Once deleted, the member will lose all access and need to be re-invited to regain access.

Input Parameters

string
required
The unique member ID to delete. This is the member’s identifier in LaunchDarkly, not their email address.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_METRICTool to permanently delete a metric from LaunchDarkly. Use when you need to remove a metric that is no longer needed. Once deleted, the metric cannot be recovered.

Input Parameters

string
required
The unique key of the metric to delete. This is the identifier for the metric within the project.
string
required
The unique key identifying the LaunchDarkly project containing the metric. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_METRIC_GROUPTool to permanently delete a metric group from LaunchDarkly. Use when you need to remove a metric group that is no longer needed. Once deleted, the metric group cannot be recovered.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the metric group. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the metric group to delete. This identifies the specific metric group within the project.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_O_AUTH_CLIENTPermanently deletes an OAuth 2.0 client from LaunchDarkly. OAuth 2.0 clients are used for programmatic access to the LaunchDarkly API. Once deleted, the client and its credentials cannot be recovered. Ensure you have the correct client ID before proceeding.

Input Parameters

string
required
The unique client ID of the OAuth 2.0 client to delete. This ID is returned when creating an OAuth client or can be found by listing OAuth clients.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_PROJECTTool to permanently delete a project from LaunchDarkly. Once deleted, the project, its environments, feature flags, and all associated data cannot be recovered. Use with caution and ensure you have the correct project key before proceeding.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project to delete. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_RELAY_AUTO_CONFIGTool to delete a Relay Proxy auto configuration by ID. Use when you need to permanently remove a relay proxy configuration from LaunchDarkly. Once deleted, the configuration cannot be recovered.

Input Parameters

string
required
The unique ID of the Relay Proxy auto configuration to delete. This is returned when creating a relay auto config or can be found by listing existing relay auto configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_RELEASE_BY_FLAG_KEYTool to delete a release from a feature flag. Use when you need to remove a release associated with a flag in LaunchDarkly.

Input Parameters

string
required
The unique key of the feature flag from which to delete the release.
string
required
The unique key identifying the LaunchDarkly project containing the flag. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_RELEASE_PIPELINETool to permanently delete a release pipeline from LaunchDarkly. Use when you need to remove a pipeline that is no longer needed.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the release pipeline. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the release pipeline to delete.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_RELEASE_POLICYTool to permanently delete a release policy from a LaunchDarkly project. Once deleted, the policy cannot be recovered. Requires beta API version header.

Input Parameters

string
required
The human-readable key of the release policy to delete. This is the unique identifier for the policy within the project.
string
required
The unique key identifying the LaunchDarkly project containing the release policy. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_REPOSITORYTool to delete a code reference repository with the specified name. Use when you need to permanently remove a repository from LaunchDarkly’s code references system. Once deleted, the repository and its associated data cannot be recovered.

Input Parameters

string
required
The repository name to delete. This is the unique identifier for the code reference repository in LaunchDarkly.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_SEGMENTPermanently deletes a segment from LaunchDarkly. Segments are groups of contexts that you can use to manage flag targeting rules. Once deleted, the segment cannot be recovered. Ensure you have the correct segment key before proceeding.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the segment. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the segment to delete. This identifies the specific segment within the project and environment.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_SUBSCRIPTIONTool to permanently delete an audit log subscription in LaunchDarkly. Audit log subscriptions forward LaunchDarkly audit events to external services like Datadog, Splunk, or Microsoft Teams. Once deleted, the subscription cannot be recovered and audit events will no longer be forwarded to that integration endpoint.

Input Parameters

string
required
The unique identifier (ID) of the audit log subscription to delete. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration.
string
required
The integration key identifying the type of audit log subscription (e.g., ‘datadog’, ‘splunk’, ‘msteams’). This key determines which integration service the subscription belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_TEAMPermanently deletes a team from LaunchDarkly organization. Once deleted, the team and its associated settings cannot be recovered. Ensure you have the correct team key before proceeding.

Input Parameters

string
required
The unique key identifying the team to delete. Use ‘List Teams’ action to find available team keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_TOKENTool to permanently delete an access token from LaunchDarkly. Once deleted, the token cannot be recovered and any integrations using it will no longer be able to authenticate.

Input Parameters

string
required
The unique identifier (ID) of the access token to delete. This ID is returned when creating a token or can be found using the list tokens endpoint.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOWPermanently deletes a flag trigger workflow from LaunchDarkly. Flag triggers allow you to initiate flag changes remotely using a unique webhook URL. Once deleted, the trigger and its URL cannot be recovered. Ensure you have the correct trigger ID before proceeding.

Input Parameters

string
required
The unique identifier (ID) of the flag trigger to delete. This ID is returned when creating a trigger or can be found using the ‘List Flag Triggers’ API endpoint.
string
required
The unique key identifying the LaunchDarkly project containing the flag trigger. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the trigger is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the trigger to delete. This is the flag the trigger is associated with.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_WEBHOOKTool to delete a webhook from LaunchDarkly. Use when you need to remove an existing webhook integration. Once deleted, the webhook and its configuration cannot be recovered.

Input Parameters

string
required
The unique identifier (ID) of the webhook to delete. This ID can be obtained from listing webhooks or when creating a webhook.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_WORKFLOWPermanently deletes a workflow from LaunchDarkly. Workflows automate flag changes based on conditions or schedules. Once deleted, the workflow cannot be recovered. Ensure you have the correct workflow ID before proceeding.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the workflow. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the workflow to delete. This ID is returned when creating a workflow or can be found using the ‘List Workflows’ API endpoint.
string
required
The environment key where the workflow is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the workflow to delete. This is the flag the workflow is associated with.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_DELETE_WORKFLOW_TEMPLATEPermanently deletes a workflow template from LaunchDarkly. Workflow templates provide reusable patterns for common flag change workflows. Once deleted, the template cannot be recovered. Ensure you have the correct template key before proceeding.

Input Parameters

string
required
The unique key identifying the workflow template to delete. This is the template key returned when creating a template or found by listing existing workflow templates.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_EVALUATE_CONTEXT_INSTANCETool to evaluate flags for a context instance to determine expected flag variations. Important: Do not use this as a replacement for LaunchDarkly SDKs in production applications. SDKs are optimized for flag evaluation at scale and generate analytics events. This API is intended for testing, debugging, or administrative purposes only.

Input Parameters

string
required
A unique key for the context instance. This identifies the specific context (e.g., user ID, organization ID).
string
required
The kind of context instance. Common values include ‘user’, ‘organization’, ‘device’, or custom kinds.
string
A comma-separated list of fields to sort by. Fields prefixed by a dash (-) sort in descending order.
integer
The number of feature flags to return. Defaults to -1, which returns all flags. Use positive integers to limit results.
string
A comma-separated list of filters. Each filter is of the form ‘field operator value’.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment within the project.
object
Additional custom attributes for the context instance (e.g., name, email, custom properties). These attributes can be used in flag targeting rules.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GENERATE_TRUST_POLICYTool to generate an AWS trust policy for Data Export destinations. Use when you need to create or update IAM trust policies that allow LaunchDarkly to assume roles for exporting data to AWS services.

Input Parameters

string
required
The environment key where the Data Export destination is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ALL_HOLDOUTSList holdout configurations for a specific LaunchDarkly project and environment. Supports pagination.

Input Parameters

integer
The number of holdouts to return in the response. Defaults to 20.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ALL_INTEGRATION_CONFIGURATIONSTool to retrieve all integration configurations for a specific integration key. Use when you need to list or audit configurations for integrations like Slack, Datadog, custom approvals, webhooks, or other third-party services. Excludes persistent store and flag import configurations.

Input Parameters

string
required
The integration key to filter configurations by. Common values include ‘slack’, ‘datadog’, ‘jira’, ‘custom-approvals’, ‘webhook’, etc. This identifies the type of integration.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ALL_RELEASE_PIPELINESList release pipelines for a project, with filtering and pagination, to view pipelines available for feature flag releases.

Input Parameters

integer
Maximum number of release pipelines to return per page. Defaults to 20.
string
A comma-separated list of filters. Each filter is of the form field:value. Supported filter fields are described in the API documentation.
integer
Number of release pipelines to skip for pagination. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ALL_WEBHOOKSTool to retrieve all webhooks configured in the LaunchDarkly account. Use when you need to list, audit, or discover existing webhook integrations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ANNOUNCEMENTS_PUBLICTool to retrieve public announcements from LaunchDarkly. Use to get system announcements, maintenance notices, and updates.

Input Parameters

integer
The number of announcements to return.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string ("active" | "inactive" | "scheduled")
Status values for announcement filtering.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPLICATIONSTool to retrieve a list of applications in LaunchDarkly. Use to enumerate application keys and metadata. Supports filtering by key, name, kind, and autoAdded status.

Input Parameters

string
Sort order and fields. Fields can be comma-separated. Supported fields: ‘creationDate’, ‘name’. Prefix with ’-’ for descending order. Examples: ‘name’ (ascending by name), ‘-name,creationDate’ (descending by name, then ascending by creation date).
integer
Maximum number of applications to return per page. Defaults to 10 if not specified.
string
Comma-separated list of properties to expand in the response. Options: ‘flags’ (includes flag information for each application).
string
Filter expression to narrow results. Supported filters: ‘key’, ‘name’, ‘kind’, and ‘autoAdded’. Examples: ‘key:my-app’, ‘kind:browser’, ‘autoAdded:false’. See https://launchdarkly.com/docs/api/applications-beta#filtering-applications-and-application-versions for syntax details.
integer
Number of applications to skip for pagination. Use with ‘limit’ to paginate through results.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPLICATION_VERSIONSList versions for a specific LaunchDarkly application to inspect version history or supported versions. Supports filtering, sorting, and pagination.

Input Parameters

string
Sort order and fields (comma-separated). Available fields: ‘creationDate’, ‘name’. Prefix with ’-’ for descending order. Examples: ‘name’ (ascending by name), ‘-name,creationDate’ (descending by name, then ascending by creation date).
integer
Maximum number of versions to return per page. Defaults to 50 if not specified.
string
Filter expression to narrow down results. Supported filters: ‘key’ (version key), ‘name’ (version name), ‘supported’ (boolean), ‘autoAdded’ (boolean). See https://launchdarkly.com/docs/api/applications-beta#filtering-applications-and-application-versions for filter syntax details.
integer
Number of versions to skip for pagination. Use with ‘limit’ for paged results.
string
required
The application key identifying the application. This is the unique identifier for the application whose versions you want to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPROVAL_FOR_FLAGTool to get a single approval request for a feature flag in LaunchDarkly. Use when you need detailed information about a specific approval request including its review status, conflicts, and metadata.

Input Parameters

string
required
The feature flag approval request ID. This ID is returned when creating an approval request or can be found using the approval requests API.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key where the approval request exists (e.g., ‘test’, ‘production’). Use GET_ENVIRONMENTS to list available environments.
string
required
The feature flag key identifying the specific flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPROVAL_REQUESTTool to get a specific approval request by ID from LaunchDarkly. Use when you need detailed information about a particular approval request.

Input Parameters

string
required
The approval request ID. Example: ‘697ca6af08d12709fda933a4’
string
A comma-separated list of fields to expand in the response. Supported fields may include additional details about members, projects, flags, or environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPROVAL_REQUESTSRetrieve a page of approval requests from LaunchDarkly, with optional filtering and pagination. Use to monitor pending approvals, track approval history, or audit changes requiring approval.

Input Parameters

integer
Maximum number of approval requests to return (1-200). Defaults to 20.
string
Comma-separated list of fields to expand in the response. Supported fields may include additional details about members, projects, or flags.
string
Filter approval requests using format ‘field:value’. Supported fields: ‘requestorId’ (filter by requestor member ID), ‘projectKey’ (filter by project), ‘notifyMemberIds’ (filter by members to notify), ‘reviewStatus’ (pending, approved, declined), ‘status’ (pending, applied, declined). Use comma-separated values for multiple filters. Example: ‘reviewStatus:pending’ or ‘projectKey:my-project,status:pending’.
integer
Starting index for pagination. Defaults to 0.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPROVAL_REQUEST_SETTINGSTool to retrieve approval request settings for a project. Use to understand approval requirements for different resource kinds and environments. Supports filtering by environment and resource kind.

Input Parameters

string
Comma-separated list of fields to expand in the response. Options include ‘default’ and ‘strict’.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
Filter approval settings by resource kind (e.g., ‘flag’, ‘segment’). If omitted, returns settings for all resource kinds.
string
Filter approval settings by environment key. If omitted, returns settings for all environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_APPROVALS_FOR_FLAGRetrieve approval requests for a specific feature flag in an environment, with optional pagination. Use to monitor pending approvals or review approval history for the flag.

Input Parameters

integer
The maximum number of approval requests to return. Defaults to returning all items if not specified.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string
required
The project key identifying the project containing the feature flag.
string
required
The environment key for which to retrieve approval requests.
string
required
The feature flag key identifying the specific flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_AUDIT_LOG_ENTRIESRetrieve audit log entries to review account activity, track resource changes, or audit modifications. Results can be filtered by date ranges, resource specifiers, or text search.

Input Parameters

string
Text to search for. You can search for the full or partial name of the resource.
string
A resource specifier that lets you filter audit log listings by resource. See https://launchdarkly.com/docs/home/account/role-resources for syntax details.
integer
A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries this returns occurred after the timestamp.
integer
A limit on the number of audit log entries that return. Set between 1 and 20. The default is 10.
integer
A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries this returns occurred before the timestamp.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_AUDIT_LOG_ENTRYTool to retrieve a single audit log entry by ID. Use when you need to inspect details of a specific audit event.

Input Parameters

string
required
The ID of the audit log entry to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_BIG_SEGMENT_EXPORTTool to retrieve a specific big segment export by its ID. Use when you need to check the status or details of a segment export operation.

Input Parameters

string
required
The export ID identifying the specific export to retrieve.
string
required
The project key identifying the project containing the segment. Use ‘List Projects’ action to find available project keys.
string
required
The segment key identifying the specific big segment.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_BIG_SEGMENT_IMPORTTool to retrieve the status and details of a big segment import by its ID. Use when you need to check the progress or completion status of an import operation.

Input Parameters

string
required
The unique identifier (ID) of the import to retrieve.
string
required
The project key identifying the project containing the segment. Use LIST_PROJECTS to discover available project keys.
string
required
The segment key identifying the big segment.
string
required
The environment key where the segment exists (e.g., ‘test’, ‘production’). Use GET_ENVIRONMENTS to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_BIG_SEGMENT_STORE_INTEGRATIONTool to retrieve a specific persistent store integration for big segments by its ID. Use when you need to inspect the configuration, status, or details of a big segment store integration.

Input Parameters

string
required
The project key identifying the project containing the integration. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the big segment store integration to retrieve.
string
required
The environment key where the integration is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string ("redis" | "dynamodb")
required
The type of big segment store integration, either ‘redis’ or ‘dynamodb’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_BIG_SEGMENT_STORE_INTEGRATIONSTool to retrieve all persistent store integrations for big segments. Use when you need to list configured Redis or DynamoDB integrations across all projects and environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_BRANCHTool to retrieve branch information from a LaunchDarkly code reference repository. Use to view branch metadata, HEAD commit, sync status, and flag references within the branch.

Input Parameters

string
required
The repository name. This is the name of the code reference repository configured in LaunchDarkly.
string
required
The branch name. Branch names with special characters like slashes will be automatically URL-encoded.
string
Filter results to a specific flag key. Only references to this flag will be included.
string
Filter results to a specific project key. Only flag references for this project will be included.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CALLER_IDENTITYTool to retrieve basic information about the identity used to authenticate API calls. Use when you need to verify authentication credentials or inspect API token details.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXT_ATTRIBUTE_NAMESTool to retrieve context attribute names for a project and environment. Use when you need to discover available context attributes grouped by context kind.

Input Parameters

integer
Maximum number of items to return in the collection (max: 100, default: 100).
string
A comma-separated list of context filters. This endpoint only accepts ‘kind’ filters with the ‘equals’ operator, and ‘name’ filters with the ‘startsWith’ operator. Example: ‘kind equals user,name startsWith email’. See LaunchDarkly docs for filtering contexts syntax.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXT_ATTRIBUTE_VALUESTool to retrieve unique values for a specific context attribute within a project environment. Use when you need to discover what values exist for a context attribute, optionally filtered by context kind.

Input Parameters

integer
Maximum number of items to return in the collection. Default: 50, Maximum: 100.
string
A comma-separated list of context filters. This endpoint only accepts ‘kind’ filters with the ‘equals’ operator, and ‘value’ filters with the ‘startsWith’ operator. Example: ‘kind equals “user”’ or ‘value startsWith “test”’.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The name of the context attribute to retrieve values for (e.g., ‘key’, ‘email’, ‘country’).
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXT_INSTANCESTool to get context instances for a specific context ID within a project and environment. Use when you need to retrieve context instance data.

Input Parameters

string
required
The context instance ID. Format is typically ‘kind:value’ (e.g., ‘user:test-user-123’).
string
Specifies a field by which to sort. LaunchDarkly supports sorting by timestamp in ascending order by specifying ‘ts’ for this value, or descending order by specifying ‘-ts’.
integer
Specifies the maximum number of context instances to return. Maximum is 50, default is 20.
string
A comma-separated list of context filters. This endpoint only accepts an ‘applicationId’ filter. To learn more about the filter syntax, read Filtering contexts and context instances.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment within the project.
string
Limits results to context instances with sort values after the value specified. You can use this for pagination, however, we recommend using the ‘next’ link instead.
boolean
Specifies whether to include or omit the total count of matching context instances. Defaults to true.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXT_KINDS_BY_PROJECT_KEYTool to retrieve all context kinds for a given project. Use when you need to understand available context kinds for targeting and segmentation.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXTSTool to retrieve context instances from a LaunchDarkly environment by kind and key. Use when you need to get specific context data for analysis or debugging.

Input Parameters

string
required
The context key uniquely identifying the context instance within the specified kind.
string
required
The context kind (e.g., ‘user’, ‘organization’). ‘user’ is the default context kind in LaunchDarkly.
string
Specifies a field by which to sort. Use ‘ts’ for ascending order by timestamp, or ‘-ts’ for descending order.
integer
Maximum number of context instances to return. Maximum: 50, default: 20.
string
A comma-separated list of context filters. This endpoint only accepts an ‘applicationId’ filter. Example: ‘applicationId:com.myapp’.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
Limits results to contexts with sort values after the value specified. You can use this for pagination, however, the ‘next’ link is recommended instead.
boolean
Whether to include the total count of matching contexts. Defaults to true.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXTS_CLIENTSIDE_USAGETool to get a detailed time series of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use this for breakdowns that go beyond the primary-only aggregation of MAU endpoints. The counts reflect data reported by client-side SDKs.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. contextKind is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions.
array
An SDK name to filter results by. Can be specified multiple times to filter by multiple SDK names.
array
An anonymous value to filter results by. Can be specified multiple times. Valid values: ‘true’, ‘false’.
array
A project key to filter results by. Can be specified multiple times to filter by multiple projects.
array
A context kind to filter results by. Can be specified multiple times to filter by multiple context kinds.
string ("daily" | "monthly")
Data granularity for usage series.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation method for usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXTS_SERVERSIDE_USAGETool to get detailed time series of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use for breakdowns beyond primary-only MAU aggregation. The counts reflect data from server-side SDKs. Maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
string
If specified, returns data for each distinct value of the given field. contextKind is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: projectId, environmentId, sdkName, sdkAppId, anonymousV2.
string
An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name.
string
An anonymous value to filter results by. Can be specified multiple times, one query parameter per anonymous value. Valid values: true, false.
string
A project key to filter results by. Can be specified multiple times, one query parameter per project key.
string
A context kind to filter results by. Can be specified multiple times, one query parameter per context kind.
string
Specifies the data granularity. Defaults to daily. Valid values depend on aggregationType: month_to_date supports daily and monthly; incremental and rolling_30d support daily only.
string
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key.
string
Specifies the aggregation method. Defaults to month_to_date. Valid values: month_to_date, incremental, rolling_30d.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CONTEXTS_TOTAL_USAGETool to get a detailed time series of the number of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use this for breakdowns that go beyond the primary-only aggregation of MAU endpoints. The supported granularity varies by aggregation type, and the maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. contextKind is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions. Valid values: projectId, environmentId, sdkName, sdkType, sdkAppId, anonymousV2.
array
An SDK name to filter results by. Can be specified multiple times to filter by multiple SDK names.
array
An SDK type to filter results by. Can be specified multiple times to filter by multiple SDK types.
array
An anonymous value to filter results by. Can be specified multiple times. Valid values: ‘true’, ‘false’.
array
A project key to filter results by. Can be specified multiple times to filter by multiple projects.
array
A context kind to filter results by. Can be specified multiple times to filter by multiple context kinds.
string ("daily" | "monthly")
Data granularity for usage series.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation method for usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CTX_INSTANCE_SEGMENTS_MEMBERSHIPTool to get segment membership details for a given context instance with attributes. Returns which segments the context belongs to and how (individually targeted or rule-based). Use when you need to understand segment membership for a specific user, organization, or other context type.

Input Parameters

string
required
The context instance key (unique identifier for the context).
string
required
The context kind (e.g., ‘user’, ‘organization’, ‘device’). Defaults to ‘user’ if not specified in most SDKs.
string
An optional human-readable name for the context instance.
boolean
Whether the context is anonymous. Anonymous contexts are not stored in the LaunchDarkly database.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
object
Optional custom attributes for the context instance. These can be used for segment targeting rules.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CUSTOM_ROLETool to retrieve a single custom role by key or ID. Use when you need detailed information about a specific role’s permissions and policy statements.

Input Parameters

string
required
The custom role key or ID identifying the specific role to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CUSTOM_ROLESTool to retrieve a list of all custom roles. Use when you need to list roles for permissions audits or configuration reviews. Note: results are paginated.

Input Parameters

integer
Maximum number of custom roles to return. Defaults to 20.
integer
Number of custom roles to skip before returning results. Defaults to 0.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_CUSTOM_WORKFLOWTool to retrieve details of a specific custom workflow by ID. Use when you need to inspect workflow configuration, stages, execution status, or identify conflicts.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the workflow. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the custom workflow to retrieve. This ID is returned when creating a workflow or can be found using the ‘List Workflows’ API endpoint.
string
required
The environment key where the workflow is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the workflow. This is the flag the workflow is associated with.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_DATA_EXPORT_EVENTS_USAGETool to retrieve a time series array showing the number of data export events from your account. Use when you need to analyze data export usage patterns over time. The supported granularity varies by aggregation type. The maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: ‘environmentId’, ‘eventKind’.
array
An event kind to filter results by. Can be specified multiple times, one query parameter per event kind.
array
A project key to filter results by. Can be specified multiple times, one query parameter per project key.
string
Specifies the data granularity. Defaults to ‘daily’. ‘monthly’ granularity is only supported with the month_to_date aggregation type. Valid values: ‘daily’, ‘hourly’, ‘monthly’.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key.
string
Specifies the aggregation method. Defaults to ‘month_to_date’. Valid values: ‘month_to_date’, ‘incremental’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_DEPENDENT_FLAGSTool to list dependent feature flags for a specific flag. Use when you need to identify which flags depend on a given feature flag across environments.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The feature flag key for which to retrieve dependent flags. This is the key of the flag whose dependencies you want to list.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_DEPENDENT_FLAGS_BY_ENVList dependent flags for a specified flag in a specified environment. A dependent flag uses another flag as a prerequisite.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The key of the feature flag for which to list dependent flags.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_DESTINATIONTool to retrieve a specific Data Export destination by ID. Use when you need to inspect the configuration details of a destination.

Input Parameters

string
required
The unique identifier (ID) of the Data Export destination to retrieve. This ID is returned when creating a destination or can be found by listing destinations.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the destination is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_DESTINATIONSTool to retrieve all Data Export destinations configured across all projects and environments. Use when you need to list, audit, or discover available data export destinations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ENVIRONMENTTool to retrieve a specific environment by project key and environment key. Use when you need detailed information about an environment’s configuration and settings.

Input Parameters

string
required
The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the specific environment to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ENVIRONMENTSTool to retrieve a list of all environments within a project. Use after confirming the project key; supports pagination.

Input Parameters

string
Field to sort by. Prefix with ’-’ for descending order. Example: ‘name’ for ascending, ‘-name’ for descending.
integer
Maximum number of environments to return per page. Defaults to 20.
string
Filter expression in ‘field:value’ format. Supported filters include ‘query’ for text search (e.g., ‘query:production’).
integer
Number of environments to skip for pagination. Defaults to 0.
string
required
The project key identifying the project containing the environments. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EVALUATIONS_USAGETool to get time-series arrays of flag evaluation counts, broken down by variation. Use when analyzing flag usage patterns over time. Granularity is automatic: minutely data within 2 hours, hourly within 2 days, otherwise daily.

Input Parameters

string
The series of data returned ends at this timestamp. Defaults to the current time if not specified. Format: ISO 8601 timestamp or Unix timestamp in milliseconds.
string
The timezone to use for breaks between days when returning daily data. Examples: ‘America/New_York’, ‘UTC’, ‘Europe/London’.
string
The series of data returned starts from this timestamp. Defaults to 30 days ago if not specified. Format: ISO 8601 timestamp or Unix timestamp in milliseconds.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The feature flag key identifying the specific flag to get evaluations usage for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EVENTS_USAGETool to get time-series arrays of flag evaluation events. Use when analyzing flag usage patterns or tracking evaluation counts broken down by variation. Granularity varies: minutely for data within 2 hours, hourly for within 2 days, otherwise daily.

Input Parameters

string
The series of data returned ends at this timestamp (ISO 8601 format or Unix timestamp). Defaults to the current time.
string
The series of data returned starts from this timestamp (ISO 8601 format or Unix timestamp). Defaults to 24 hours ago.
string ("received" | "published")
required
The type of event to retrieve. Must be either ‘received’ or ‘published’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPERIMENTTool to retrieve a specific experiment by project key, environment key, and experiment key. Use when you need detailed information about an experiment’s configuration, iterations, and metrics.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Supported values: previousIterations (includes all prior iterations), draftIteration (includes the iteration which has not been started yet), secondaryMetrics (includes secondary metrics), treatments (includes all treatment and parameter details).
string
required
The project key identifying the project containing the experiment. Use LIST_PROJECTS to discover available project keys.
string
required
The experiment key identifying the specific experiment to retrieve.
string
required
The environment key identifying the environment containing the experiment.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPERIMENTATION_EVENTS_USAGETool to retrieve a time series array showing the number of experimentation events from your account. Use when analyzing experimentation event usage patterns over time.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions. Valid values: environmentId, eventKey, eventKind.
array
An event key to filter results by. Can be specified multiple times to filter by multiple event keys.
array
An event kind to filter results by. Can be specified multiple times to filter by multiple event kinds.
array
A project key to filter results by. Can be specified multiple times to filter by multiple projects.
string
Specifies the data granularity. Defaults to daily. monthly granularity is only supported with the month_to_date aggregation type. Valid values: daily, hourly, monthly.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments.
string
Specifies the aggregation method. Defaults to month_to_date. Valid values: month_to_date, incremental.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPERIMENTATION_KEYS_USAGETool to get a time series showing the number of experimentation keys from your account. Use when you need to track experimentation key usage over time with support for filtering by project, environment, or experiment. Maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
string ("projectId" | "environmentId" | "experimentId")
Valid dimensions for grouping experimentation keys usage data.
string
A project key to filter results by. Can be specified multiple times for multiple projects.
string ("daily" | "hourly" | "monthly")
Supported granularity levels for experimentation keys usage.
string
An experiment ID to filter results by. Can be specified multiple times for multiple experiments.
string
An environment key to filter results by. If specified, exactly one projectKey must be provided.
string ("month_to_date" | "incremental")
Supported aggregation types for experimentation keys usage.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPERIMENTATION_SETTINGSTool to retrieve experimentation settings for a project. Use when you need to understand how experiments are configured in a project.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPERIMENTSTool to retrieve experiments from a project and environment. Use after confirming project and environment keys to enumerate experiments and their configurations.

Input Parameters

integer
Maximum number of experiments to return per page. Defaults to 20.
string
Comma-separated list of properties that can reveal additional information in the response. Supported fields include metrics, environments, and more.
string
Comma-separated list of filters in field:value format. Each filter is of the form field:value. Supported fields include query for text search.
integer
Number of experiments to skip for pagination. Use this with limit to page through results.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
Comma-separated list of experiment archived states. Supports ‘archived’, ‘active’, or both. Defaults to ‘active’ experiments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPIRING_CONTEXT_TARGETSTool to retrieve context targets scheduled for removal from a feature flag. Use when you need to check which targets will be automatically removed.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The feature flag key identifying the flag with expiring targets. Use GET_FEATURE_FLAGS to discover available flag keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXPIRING_TARGETS_FOR_SEGMENTTool to retrieve context targets scheduled for removal from a segment. Use when you need to check which targets will be automatically removed from a segment.

Input Parameters

string
required
The project key identifying the project containing the segment. Use LIST_PROJECTS to discover available project keys.
string
required
The segment key identifying the segment with expiring targets.
string
required
The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_EXTINCTIONSTool to get a list of all extinctions. LaunchDarkly creates an extinction event after you remove all code references to a flag. Use to discover flags that have been removed from your codebase. To learn more, read About extinction events.

Input Parameters

integer
Filter results to a specific timeframe based on commit time, expressed as a Unix epoch time in milliseconds. Must be used with from.
integer
Filter results to a specific timeframe based on commit time, expressed as a Unix epoch time in milliseconds. Must be used with to.
string
Filter results to a specific flag key.
string
Filter results to a specific project.
string
Filter results to a specific repository.
string
Filter results to a specific branch. By default, only the default branch will be queried for extinctions.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAGTool to retrieve a specific feature flag by project key and flag key. Use when you need detailed information about a flag’s configuration, variations, and targeting rules.

Input Parameters

string
Filter configurations by environment. When specified, only environment-specific configuration for that environment will be included in the response.
string
A comma-separated list of fields to expand in the response. Supported fields may include specific nested properties.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The feature flag key identifying the specific flag to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAGSList feature flags in a project, with optional filters and pagination. Results can include flag configurations, depending on the request and API version.

Input Parameters

string
Filter configurations by environment. Setting this adds environment-specific configuration details to the response.
string
Filter feature flags by tag.
string
Comma-separated list of fields to sort by. Prefix with ’-’ for descending order. Examples: ‘name’, ‘-creationDate’.
integer
Maximum number of feature flags to return. Defaults to 20.
string
Comma-separated list of fields to expand in response. Examples: ‘evaluation’, ‘migrationSettings’.
string
Comma-separated list of filters in field:value format. Examples: ‘archived:true’, ‘tags:beta’, ‘query:my-flag’.
integer
Number of flags to skip for pagination. Use with limit for paging through results.
boolean
Filter to only flags with differences between environments. Deprecated, unavailable in API version 20240415.
boolean
By default, flags do not include prerequisites, targets, or rules. Set summary=false and include env parameter to get these details.
boolean
Filter to archived or unarchived flags. Deprecated, use filter=archived:true instead.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAG_SCHEDULED_CHANGETool to retrieve a specific scheduled change for a feature flag. Use when you need details about a scheduled flag update, including execution time and instructions.

Input Parameters

string
required
The scheduled change ID to retrieve.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment for the scheduled change.
string
required
The feature flag key identifying the specific flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUSTool to retrieve the status of a feature flag. Returns the current status (new, inactive, active, or launched) along with metadata.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The feature flag key identifying the specific flag. This is the unique key assigned to the feature flag within the project.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUS_ACROSS_ENVIRONMENTSTool to retrieve the status of a feature flag across all environments in a project. Use when you need to check flag status across multiple environments.

Input Parameters

string
Optional environment filter. When specified, returns status only for the specified environment.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The feature flag key identifying the flag to retrieve status for. Use GET_FEATURE_FLAGS to discover available feature flag keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUSESTool to retrieve status information for all feature flags in a project environment. The status includes last request time and state (new, active, inactive, or launched).

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment within the project. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FLAG_CONFIG_SCHEDULED_CHANGESTool to retrieve scheduled changes for a feature flag. Use when you need to see planned configuration updates for a flag in a specific environment.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key where the scheduled changes are configured (e.g., ‘production’, ‘staging’). Use GET_ENVIRONMENTS to list available environments.
string
required
The feature flag key identifying the specific flag to retrieve scheduled changes for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FLAG_DEFAULTS_BY_PROJECTTool to retrieve flag defaults for a specific project. Use when you need to understand the default configuration settings applied to new flags in a project.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FLAG_FOLLOWERSTool to retrieve followers of a flag in a project and environment. Use when you need to see which team members are following a specific feature flag for notifications.

Input Parameters

string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the specific environment.
string
required
The feature flag key identifying the specific flag.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FLAG_IMPORT_CONFIGURATIONTool to retrieve a single flag import configuration by project key, integration key, and integration ID. Use when you need to inspect the details of a specific flag import configuration.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the flag import configuration to retrieve.
string ("split" | "unleash")
required
The integration key identifying the feature management system from which the import occurs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FLAG_IMPORT_CONFIGURATIONSTool to list all flag import configurations. Use to discover existing configurations for importing flags from external feature management systems. This action requires the LD-API-Version: beta header.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_FOLLOWERS_BY_PROJ_ENVTool to retrieve followers of all flags in a given project and environment. Use when you need to see which team members are following which feature flags.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_HOLDOUTTool to retrieve a specific holdout experiment by project key, environment key, and holdout key. Use when you need detailed information about a holdout experiment configuration, status, and related experiments.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Holdout experiment expansion fields have no prefix. Related experiment expansion fields have ‘rel-’ as a prefix.
string
required
The holdout experiment key to retrieve.
string
required
The project key identifying the project containing the holdout. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment where the holdout exists.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_INTEGRATION_CONFIGURATIONTool to retrieve a specific integration configuration by ID. Use when you need to inspect the configuration details of an integration with external services like Slack, Datadog, or custom approvals.

Input Parameters

string
required
The unique ID of the integration configuration to retrieve. This is returned when creating an integration configuration or can be found by listing existing integration configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_INTEGRATION_DELIVERY_CONFIG_BY_ENVTool to get delivery configurations by environment for feature store integrations. Use when you need to retrieve integration delivery configurations for a specific project and environment.

Input Parameters

string
required
The project key to retrieve configurations for. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key to retrieve configurations for. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_IPSTool to retrieve the list of IP ranges used by the LaunchDarkly service. Use to configure firewall rules that allow LaunchDarkly traffic.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_LAYERSTool to retrieve layers for a project. Use when you need to list all layers or filter by experiment key.

Input Parameters

string
A comma-separated list of filters. This endpoint only accepts filtering by experimentKey. The filter returns layers which include that experiment for the selected environment(s). Example: ‘filter=reservations.experimentKey contains expKey’.
string
required
The project key identifying the project containing the layers. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MAU_CLIENTSIDE_USAGETool to get a time series of context key usages observed by LaunchDarkly client-side SDKs for the primary context kind. Use when analyzing MAU trends for client applications. The supported granularity varies by aggregation type, and the maximum time range is 365 days.

Input Parameters

string
End timestamp for the time series in Unix milliseconds. Defaults to the current time if not specified.
string
Start timestamp for the time series in Unix milliseconds. Defaults to the beginning of the current month if not specified. Maximum time range is 365 days.
array
Group data by specified dimensions. Returns separate time series for each distinct value of the given field(s). Can specify multiple dimensions to create multi-dimensional groupings.
array
Filter results by SDK name(s). Can specify multiple SDK names to filter by client-side SDK types.
array
Filter results by anonymous context values. Can specify multiple values to include both anonymous and identified contexts.
array
Filter results by project key(s). Can specify multiple project keys to include data from multiple projects.
string ("daily" | "monthly")
Valid granularity values for MAU data.
array
Filter results by environment key(s). If specified, exactly one projectKey must be provided. Can specify multiple environment keys.
string ("month_to_date" | "incremental" | "rolling_30d")
Valid aggregation methods for MAU data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MAU_TOTAL_USAGETool to get a time series of the number of context key usages observed by LaunchDarkly in your account, for the primary context kind only. The maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: projectId, environmentId, sdkName, sdkType, sdkAppId, anonymousV2.
array
An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name.
array
An SDK type to filter results by. Can be specified multiple times, one query parameter per SDK type.
string
An anonymous value to filter results by. Can be specified multiple times, one query parameter per anonymous value. Valid values: ‘true’, ‘false’.
array
A project key to filter results by. Can be specified multiple times, one query parameter per project key.
string ("daily" | "monthly")
Data granularity for MAU total usage.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation type for MAU total usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MAU_USAGETool to get a time-series array of monthly active users (MAU) seen by LaunchDarkly from your account. The granularity is always daily. Note: This endpoint is deprecated and does not return information about active context instances after SDK upgrade to contexts. Use for legacy MAU tracking only.

Input Parameters

string
ISO 8601 timestamp (e.g., ‘2024-01-31T23:59:59Z’) or Unix epoch in milliseconds. The series of data returned ends at this timestamp. Defaults to the current time if not specified.
array
One or more SDK names to filter results (e.g., ‘python-server’, ‘js-client’).
string
ISO 8601 timestamp (e.g., ‘2024-01-01T00:00:00Z’) or Unix epoch in milliseconds. The series of data returned starts from this timestamp. Defaults to 30 days ago if not specified.
array
One or more fields to group data by. Returns data for each distinct value of the given field(s). Can group by multiple dimensions (e.g., project and SDK).
array
One or more project keys to filter results. Specify multiple project keys to view data for multiple projects.
array
One or more SDK types to filter results. Valid values are ‘client’ or ‘server’.
string
Filter results to either anonymous or nonanonymous users. Set to ‘true’ for anonymous users, ‘false’ for nonanonymous users.
array
One or more context kinds to filter results. If not set, queries for the ‘user’ context kind. Specify multiple context kinds to view data for multiple context types.
array
One or more environment keys to filter results. When using this parameter, exactly one project key must also be set. Specify multiple environment keys to view data for multiple environments within a single project.
string ("rolling_30d" | "month_to_date" | "daily_incremental")
Aggregation type for MAU data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MAU_USAGE_BY_CATEGORYTool to get time-series arrays of monthly active users (MAU) by category (browser, mobile, or backend). Use when you need historical MAU metrics broken down by user category. Note: This endpoint is deprecated and does not return information about active context instances.

Input Parameters

string
The series of data returned ends at this timestamp (Unix epoch milliseconds or ISO 8601 format). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix epoch milliseconds or ISO 8601 format). Defaults to 30 days ago.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MEMBERTool to retrieve detailed information about a specific LaunchDarkly account member. Use when you need to view member details, roles, permissions, or team memberships.

Input Parameters

string
required
The unique member ID to retrieve. This is the member’s identifier in LaunchDarkly.
string
A comma-separated list of properties that can reveal additional information in the response. Example: ‘teams,roles’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_MEMBERSTool to retrieve a list of account members. Use when you need to list members for management, audit, or access control purposes. Supports filtering and pagination. By default, returns the first 20 members.

Input Parameters

string
Comma-separated list of fields to sort by. Prefix with ’-’ for descending order. Example: ‘email’ for ascending, ‘-creationDate’ for descending.
integer
Maximum number of members to return per page. Defaults to 20.
string
Comma-separated list of properties to expand in the response. Can reveal additional information such as teams, roles, or permissions. Example: ‘teams,roles’.
string
Comma-separated list of filters in ‘field:value’ format. Supported filters depend on the API documentation. Example: ‘role:admin’ or ‘email:user@example.com’.
integer
Number of members to skip for pagination. For example, an offset of 10 skips the first ten items and returns the next items.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_METRICTool to retrieve a specific metric by project key and metric key. Use when you need detailed information about a metric’s configuration, experiments, and usage.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Supported fields are ‘experiments’, ‘experimentCount’, ‘metricGroups’, ‘metricGroupCount’, ‘eventSources’, ‘guardedRollouts’, ‘guardedRolloutCount’, ‘lastUsedInExperiment’, and ‘lastUsedInGuardedRollout’.
string
The specific version ID of the metric
string
required
The metric key identifying the specific metric to retrieve.
string
required
The project key identifying the project containing the metric. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_METRIC_GROUPTool to retrieve a specific metric group by project key and metric group key. Use when you need detailed information about a metric group’s configuration, metrics, and experiments.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Supported fields may include experiments and other related resources.
string
required
The project key identifying the project containing the metric group. Use LIST_PROJECTS to discover available project keys.
string
required
The metric group key identifying the specific metric group to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_O_AUTH_CLIENT_BY_IDTool to retrieve a registered OAuth 2.0 client by its unique client ID. Use when you need to view details about an OAuth client including its name, description, and redirect URI.

Input Parameters

string
required
The unique client ID of the OAuth 2.0 client to retrieve. This ID is returned when creating an OAuth client or can be found by listing OAuth clients.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_O_AUTH_CLIENTSTool to retrieve all OAuth 2.0 clients registered by your account. Use when you need to list, audit, or manage OAuth clients for API access.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_OBSERVABILITY_ERRORS_USAGETool to get time-series arrays of the number of observability errors. Supports daily and monthly granularity. Use when you need to analyze error trends over time or monitor observability error counts.

Input Parameters

string
The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
array
A list of project keys to filter results by. Each project key is sent as a separate query parameter to the API.
string ("daily" | "monthly")
Valid granularity values for usage data.
string ("month_to_date" | "incremental" | "rolling_30d")
Valid aggregation types for usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_OBSERVABILITY_LOGS_USAGETool to retrieve time-series arrays of observability logs usage data. Supports daily and monthly granularity with various aggregation methods.

Input Parameters

string
The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
string
A project key to filter results by. Can be specified multiple times in the actual API call, one query parameter per project key.
string ("daily" | "monthly")
Granularity type for data aggregation.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation method for usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_OBSERVABILITY_SESSIONS_USAGETool to get time-series arrays of the number of observability sessions. Use when analyzing observability usage patterns. Supports ‘daily’ and ‘monthly’ granularity.

Input Parameters

string
The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
string
A project key to filter results by. Can be specified multiple times for multiple projects.
string ("daily" | "monthly")
Granularity level for observability sessions usage data.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation method for observability sessions usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_OBSERVABILITY_TRACES_USAGETool to retrieve time-series arrays of observability traces usage data. Supports daily and monthly granularity with various aggregation methods.

Input Parameters

string
The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
string
A project key to filter results by. Can be specified multiple times in the actual API call, one query parameter per project key.
string ("daily" | "monthly")
Granularity type for data aggregation.
string ("month_to_date" | "incremental" | "rolling_30d")
Aggregation method for usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_OPENAPI_SPECTool to retrieve the latest OpenAPI specification for LaunchDarkly’s API in JSON format. Use when you need the complete API schema, available endpoints, or integration documentation.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_PROJECTTool to retrieve a specific project by project key. Use when you need detailed information about a project’s configuration and settings.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Supported values: ‘environments’.
string
required
The project key identifying the project to retrieve. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELAY_PROXY_CONFIGTool to retrieve a single Relay Proxy auto configuration by ID. Use when you need to inspect the details of a specific relay proxy configuration.

Input Parameters

string
required
The relay auto config ID. Use this to uniquely identify the Relay Proxy configuration to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELAY_PROXY_CONFIGSTool to retrieve all Relay Proxy configurations in the LaunchDarkly account. Use when you need to list, audit, or manage Relay Proxy configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELEASE_BY_FLAG_KEYTool to retrieve the currently active release for a feature flag. Use when you need to check release status, phases, and configuration for a specific flag.

Input Parameters

string
required
The unique key of the feature flag to retrieve the release for.
string
required
The unique key identifying the LaunchDarkly project containing the flag. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELEASE_PIPELINE_BY_KEYTool to retrieve a release pipeline by its key. Use when you need detailed information about a release pipeline’s configuration, phases, and settings.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project containing the release pipeline. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the release pipeline to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELEASE_POLICIESTool to retrieve a list of release policies for a specified project. Use when you need to view available release automation policies for progressive or guarded rollouts. Requires beta API version header.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.
boolean
When true, exclude the default release policy from the response. When false or omitted, include the default policy if an environment filter is present.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELEASE_POLICYTool to retrieve a single release policy by its key for a specified project. Use when you need detailed information about a specific release automation policy. Requires beta API version header.

Input Parameters

string
required
The release policy key identifying the policy to retrieve. Use GET_RELEASE_POLICIES to discover available policy keys.
string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_RELEASE_PROGRESSIONS_FOR_PIPELINERetrieve a page of release progression details across flags for a release pipeline, including release status, active phases, and completion counts. Supports filtering and pagination.

Input Parameters

integer
The maximum number of items to return. Defaults to 20.
string
Accepts filter by ‘status’ and ‘activePhaseId’. ‘status’ can take a value of ‘completed’ or ‘active’. ‘activePhaseId’ takes a UUID and will filter results down to releases active on the specified phase. Providing ‘status equals completed’ along with an ‘activePhaseId’ filter will return an error as they are disjoint sets of data. The combination of ‘status equals active’ and ‘activePhaseId’ will return the same results as ‘activePhaseId’ alone.
integer
Where to start in the list. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The pipeline key identifying the release pipeline.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_REPOSITORYTool to get a single code reference repository by name. Use when you need to retrieve details about a specific repository configured in LaunchDarkly’s code references system.

Input Parameters

string
required
The repository name to retrieve. This is the unique identifier for the code reference repository in LaunchDarkly.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ROOTTool to retrieve the LaunchDarkly API root resource. Returns hypermedia links to all available API endpoints.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_ROOT_STATISTICTool to get links to code reference repositories for each project. Use to discover which projects have code references enabled.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SEGMENTTool to retrieve a specific segment by segment key. Use when you need detailed information about a segment’s configuration, targeting rules, and members. Segments are groups of contexts that you can use to manage flag targeting rules.

Input Parameters

string
required
The project key identifying the project containing the segment. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the segment to retrieve. This identifies the specific segment within the project and environment.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SEGMENT_MEMBERSHIP_FOR_CONTEXTTool to get big segment membership status for a specific context. Returns whether the context is explicitly included or excluded from the segment. Use when you need to check if a specific user or other context is a member of a big segment.

Input Parameters

string
required
The context key identifying the specific context (user, organization, etc.) to check segment membership for.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The segment key identifying the specific big segment to check membership for.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SEGMENTSLists segments in a project and environment, with filtering, sorting, and pagination. Use it to enumerate segments and their configurations across pages.

Input Parameters

string
Comma-separated list of fields to sort by. Prefix with ’-’ for descending order. Possible fields are ‘creationDate’, ‘name’, ‘lastModified’. Examples: ‘name’, ‘-creationDate’.
integer
Maximum number of segments to return. Defaults to 20.
string
Filter expression to narrow results. Accepts filter by ‘excludedKeys’, ‘external’, ‘includedKeys’, ‘query’, ‘tags’, ‘unbounded’, ‘view’. Example: ‘tags:beta’.
integer
Number of segments to skip for pagination. Use with limit for paging through results.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key where segments are configured (e.g., ‘test’, ‘production’). Use GET_ENVIRONMENTS to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SERVICE_CONNECTIONS_USAGETool to get a time series array showing the number of service connection minutes from your account. Use when you need to monitor or analyze service connection usage over time. The supported granularity varies by aggregation type, and the maximum time range is 365 days.

Input Parameters

string
The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time.
string
The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month.
array
If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions.
array
An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name.
array
An SDK type to filter results by. Can be specified multiple times, one query parameter per SDK type.
array
A project key to filter results by. Can be specified multiple times, one query parameter per project key.
array
An SDK version to filter results by. Can be specified multiple times, one query parameter per SDK version.
string ("daily" | "hourly" | "monthly")
Data granularity for service connections usage time series.
array
A relay version to filter results by. Can be specified multiple times, one query parameter per relay version.
array
A connection type to filter results by. Can be specified multiple times, one query parameter per connection type.
array
An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key.
string ("month_to_date" | "incremental")
Aggregation method for service connections usage data.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_STATISTICSTool to retrieve code references statistics for feature flags. Use when you need to understand where flags are referenced in your codebase.

Input Parameters

string
Filter results to a specific flag key. If provided, returns statistics only for the specified flag.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_STREAM_USAGETool to get time-series data of streaming connections to LaunchDarkly. Returns minutely data for requests within the past 2 hours, hourly data for the last 2 days, and daily data otherwise.

Input Parameters

string
The series of data returned ends at this timestamp. Defaults to the current time.
string
The timezone to use for breaks between days when returning daily data.
string
The series of data returned starts from this timestamp. Defaults to 30 days ago.
string ("client" | "server")
required
The source of streaming connections to describe. Must be either ‘client’ or ‘server’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_STREAM_USAGE_BY_SDK_VERSIONTool to get time-series data of streaming connections to LaunchDarkly, separated by SDK type and version. Use when you need to analyze connection patterns by SDK version. The granularity varies: minutely data for the past 2 hours, hourly data for the past 2 days, otherwise daily data.

Input Parameters

string
The series of data returned ends at this timestamp. Defaults to the current time. Accepts Unix epoch milliseconds or ISO 8601 format.
string
The timezone to use for breaks between days when returning daily data. Uses IANA timezone names (e.g., ‘America/New_York’, ‘Europe/London’).
string
If included, this filters the returned series to only those that match this SDK name (e.g., ‘node-server-sdk’, ‘python-server-sdk’).
string
The series of data returned starts from this timestamp. Defaults to 24 hours ago. Accepts Unix epoch milliseconds or ISO 8601 format.
string ("client" | "server")
required
The source of streaming connections to describe. Must be either ‘client’ or ‘server’.
string
If included, this filters the returned series to only those that match this SDK version (e.g., ‘6.2.0’, ‘7.0.1’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_STREAM_USAGE_SDK_VERSIONSGet SDK version objects for client or server streaming connections to LaunchDarkly from your account in the past 60 days.

Input Parameters

string ("client" | "server")
required
The source of streaming connections to describe. Must be either ‘client’ or ‘server’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SUBSCRIPTION_BY_IDTool to retrieve a specific audit log subscription by ID. Use when you need to inspect the configuration, status, and details of an existing audit log subscription.

Input Parameters

string
required
The unique identifier (ID) of the audit log subscription to retrieve. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration.
string
required
The integration key identifying the type of audit log subscription (e.g., ‘slack’, ‘datadog’, ‘splunk’, ‘msteams’). This key determines which integration service the subscription belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_SUBSCRIPTIONSTool to retrieve all audit log subscriptions for a given integration. Use when you need to list all configured audit log forwarding endpoints for a specific integration type.

Input Parameters

string
required
The integration key identifying the type of audit log subscription. Valid values include: ‘datadog’, ‘dynatrace’, ‘elastic’, ‘honeycomb’, ‘logdna’, ‘msteams’, ‘new-relic-apm’, ‘signalfx’, ‘splunk’. This key determines which integration service type to retrieve subscriptions for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TAGSTool to retrieve a list of tags from LaunchDarkly. Use when you need to view available tags or filter tags by resource type or prefix.

Input Parameters

string
Return tags with the specified prefix. Use this to filter tags that start with a specific string.
string
The time to retrieve tags as of. Default is the current time. Must be a valid ISO 8601 timestamp.
array
Fetch tags associated with the specified resource type(s). Options are flag, project, environment, segment, metric, metric-data-source, aiconfig, and view. Returns all types by default.
integer
The number of tags to return. Maximum is 1000. Defaults to 20 if not specified.
integer
The index of the first tag to return. Default is 0. Use this for pagination.
boolean
Whether or not to return archived flags. Only applicable when filtering by flag resource type.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TEAMTool to fetch a specific team by key. Use when you need detailed information about a team’s configuration, members, roles, or projects.

Input Parameters

string
A comma-separated list of properties that can reveal additional information in the response. Supported values: ‘members’ (includes team members), ‘roles’ (includes custom roles), ‘roleAttributes’ (includes role attribute mappings), ‘projects’ (includes projects with write access), ‘maintainers’ (includes team maintainers). Example: ‘members,roles’.
string
required
The team key identifying the team to retrieve. Use LIST_TEAMS to discover available team keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TEAM_MAINTAINERS2Tool to retrieve the list of maintainers for a specific LaunchDarkly team. Use when you need to view which members have been assigned as maintainers for a team.

Input Parameters

integer
The number of maintainers to return in the response. Defaults to 20.
integer
Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string
required
The team key identifying the team to retrieve maintainers for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TEAM_ROLESTool to fetch the custom roles that have been assigned to a team. Use when you need to review team permissions or audit role assignments.

Input Parameters

integer
The number of roles to return in the response. Defaults to 20.
integer
Specifies the starting position for pagination. Defaults to 0.
string
required
The team key to fetch roles for. This is the unique identifier of the team.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TOKENTool to retrieve detailed information about a specific LaunchDarkly access token by its ID. Use when you need to view token details, permissions, or metadata.

Input Parameters

string
required
The ID of the access token to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TOKENSLists LaunchDarkly access tokens for audit or management, with pagination. An Admin can request personal access tokens for all members.

Input Parameters

integer
The number of access tokens to return in the response. Defaults to 25.
integer
Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
boolean
If set to true, and the authentication access token has the ‘Admin’ role, personal access tokens for all members will be retrieved.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TRIGGER_WORKFLOW_BY_IDTool to retrieve details of a specific flag trigger by ID. Use when you need to inspect trigger configuration, status, or execution history.

Input Parameters

string
required
The unique identifier (ID) of the flag trigger to retrieve. This ID is returned when creating a trigger or can be found using the ‘List Flag Triggers’ API endpoint.
string
required
The unique key identifying the LaunchDarkly project containing the flag trigger. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the trigger is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the trigger. This is the flag the trigger is associated with.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_TRIGGER_WORKFLOWSTool to retrieve all flag triggers for a specific feature flag in an environment. Use when you need to list existing triggers configured for flag automation.

Input Parameters

string
required
The project key
string
required
The environment key
string
required
The feature flag key

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_VERSIONSTool to retrieve LaunchDarkly API version information. Returns the latest API version, list of valid versions, and the version being used for the request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_WEBHOOKTool to retrieve a specific webhook by ID. Use when you need to inspect the configuration details of a webhook.

Input Parameters

string
required
The unique identifier (ID) of the webhook to retrieve. This ID can be obtained from listing webhooks or when creating a webhook.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_WORKFLOWSTool to retrieve workflows for a specific feature flag in an environment. Use when you need to list existing workflows configured for flag workflow automation.

Input Parameters

string
A field to sort the items by. Prefix field by a dash ( - ) to sort in descending order. This endpoint supports sorting by creationDate or stopDate.
integer
The maximum number of workflows to return. Defaults to 20.
integer
Where to start in the list. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit.
string ("active" | "completed" | "failed")
Valid workflow status filter values.
string
required
The project key identifying the project
string
required
The environment key identifying the environment
string
required
The feature flag key identifying the specific flag

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_GET_WORKFLOW_TEMPLATESTool to retrieve workflow templates belonging to an account. Use when you need to list available templates for workflow automation.

Input Parameters

The substring in either the name or description of a template
boolean
Whether the entire template object or just a summary should be returned

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_BRANCHESTool to list branches in a LaunchDarkly code reference repository. Use this to retrieve all branches that have been synced for a specific repository, including their commit information and sync timestamps.

Input Parameters

string
required
The repository name to list branches for. This is the name of the code reference repository configured in LaunchDarkly.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIESLists all code reference repositories configured in LaunchDarkly. Code references allow LaunchDarkly to track where feature flags are used in your codebase. Use this tool to retrieve all connected repositories, optionally filtering by project or flag key. Note: Code references is an Enterprise feature. This endpoint requires write permissions for the code-reference-repository resource.

Input Parameters

string
A feature flag key. If provided, filters code references to the specified flag.
string
A LaunchDarkly project key. If provided, filters code reference results to the specified project.
string
If set to any value, the endpoint returns repositories with associated branch data.
string
If set to any value, returns repositories with branch data and code references for the default git branch.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_INTEGRATION_DELIVERY_CONFIGURATIONSTool to list all integration delivery configurations. Use when you need to retrieve all configured integrations for feature store capabilities.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_METRIC_GROUPSLists metric groups in a project for discovery, with optional filtering, sorting, and pagination. A single call returns one page.

Input Parameters

string
A comma-separated list of fields to sort by. Fields prefixed by a dash ( - ) sort in descending order. Available sort fields vary by endpoint.
integer
The number of metric groups to return in the response. Defaults to 20. Maximum limit is 50.
string
This parameter is reserved for future use and is not currently supported on this endpoint.
string
Filter expression. Accepts filtering by experimentStatus, query, kind, hasConnections, maintainerIds, and maintainerTeamKey. Example: filter=experimentStatus equals 'running' and query equals 'test'.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and returns the next limit items.
string
required
The project key identifying the project containing the metric groups. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_METRICSLists metrics in a project for experiments or analysis, with optional filtering, sorting, and pagination. A single call returns one page.

Input Parameters

string
A field to sort the items by. Prefix field by a dash ( - ) to sort in descending order. This endpoint supports sorting by createdAt or name.
integer
The number of metrics to return in the response. Defaults to 20. Maximum limit is 50.
string
A comma-separated list of properties that can reveal additional information in the response.
string
A comma-separated list of filters. This endpoint accepts filtering by query, tags, ‘eventKind’, ‘isNumeric’, ‘unitAggregationType, hasConnections, maintainerIds, maintainerTeamKey, view, dataSourceKeys, and metricUsedIn`.
integer
Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and returns the next limit items.
string
required
The project key identifying the project containing the metrics. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_PROJECTSRetrieve a page of LaunchDarkly projects to enumerate project keys and metadata. Supports pagination, filtering, sorting, and optional environment expansion.

Input Parameters

string
Field to sort results by. Use ‘name’ for ascending or ‘-name’ for descending. Default sorts by creation date.
integer
Maximum number of projects to return. Defaults to 20 if not specified.
string
Properties to expand in each project response. Use ‘environments’ to include the list of environments for each project.
string
Filter expression in field:value format. Supported fields: ‘query’ (search by name/key), ‘tags’ (filter by tag), ‘keys’ (filter by project key). Example: ‘query:myproject’ or ‘keys:proj1,proj2’.
integer
Starting index for pagination.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_LIST_TEAMSFetches one page of LaunchDarkly teams, with filtering by name or key and optional expansions such as member counts and maintainer information. Pagination is caller-driven using limit and offset; the response includes next-page indicators.

Input Parameters

integer
Number of teams to return in this single call (1-100). LaunchDarkly’s /api/v2/teams endpoint defaults to 20 and caps the limit at 100. ONE API call is made per invocation; to fetch additional pages, call this action again with offset=next_offset from the previous response.
string
Comma-separated list of fields to expand in the response. Options: ‘members’ (includes member count), ‘roles’ (includes custom roles), ‘projects’ (includes projects with write access), ‘maintainers’ (includes maintainer list), ‘roleAttributes’ (includes role attribute mappings). Example: ‘members,maintainers’.
string
Filter teams using format ‘field:value’. Supported filters: ‘query’ (searches team names and keys, case-insensitive), ‘nomembers’ (boolean, finds teams with zero members). Example: ‘query:engineering’ or ‘nomembers:true’.
integer
Zero-based index of the first team to return. Use the next_offset value returned in the previous response to fetch the next page; pass 0 (or omit) for the first page.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_APPROVAL_REQUEST_SETTINGSTool to perform a partial update to approval request settings for a project. Use to modify approval requirements for specific environments and resource kinds. Only the fields provided will be updated.

Input Parameters

boolean
If approvals are required for this environment.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
Which service to use for managing approvals.
string
required
The resource kind for which approval settings are being updated (e.g., ‘flag’, ‘segment’).
object
Arbitrary service-specific configuration.
string
required
The environment key for which approval settings are being updated.
integer
Sets the minimum number of approvals required before a member can apply a change. The minimum is one and the maximum is five.
boolean
Allow someone who makes an approval request to apply their own change.
array
Require approval only on flags with the provided tags. Otherwise all flags will require approval.
boolean
Allow applying the change as long as at least one person has approved.
boolean
Automatically apply changes that have been approved by all reviewers. This field is only applicable for approval services other than LaunchDarkly.
string
Optional integration configuration ID of a custom approval integration. This is an Enterprise-only feature.
boolean
Whether to skip approvals for pending changes.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_BIG_SEGMENT_STORE_INTEGRATIONTool to update a persistent store integration for big segments using JSON Patch operations. Use when you need to modify integration settings like name, enabled status, or configuration details.

Input Parameters

array
required
Array of JSON Patch operations to apply to the integration. Each operation modifies a specific field like name, on, config, or tags. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The project key identifying the project containing the integration. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the big segment store integration to update.
string
required
The environment key where the integration is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string ("redis" | "dynamodb")
required
The type of big segment store integration, either ‘redis’ or ‘dynamodb’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_CUSTOM_ROLETool to update a custom role’s settings using JSON Patch operations. Use when you need to modify role configuration like name, description, or policy statements.

Input Parameters

array
required
Array of JSON Patch operations to apply to the custom role. Each operation modifies a specific field like name, description, policy, or basePermissions. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
Optional comment describing the reason for the update.
string
required
The custom role key identifying the specific role to update.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_DESTINATIONTool to update a Data Export destination using JSON Patch operations. Use when you need to modify destination settings like enabling/disabling the export, changing the name, or updating configuration.

Input Parameters

string
required
The unique identifier (ID) of the Data Export destination to update. This ID is returned when creating a destination or can be found by listing destinations.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The environment key where the destination is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
array
required
An array of JSON Patch operations to apply to the destination. Each operation modifies a specific field. Common paths: ‘/on’ (boolean - enable/disable), ‘/name’ (string), ‘/config’ (object).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_ENVIRONMENTTool to update an environment’s settings using JSON Patch operations. Use when you need to modify environment configuration like name, color, approval settings, or behavior flags.

Input Parameters

array
required
Array of JSON Patch operations to apply to the environment. Each operation modifies a specific field like name, color, confirmChanges, requireComments, tags, critical, defaultTtl, secureMode, or defaultTrackEvents. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the specific environment to update.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_EXPERIMENTTool to update an experiment using semantic patch format. Use when you need to modify experiment properties like name, description, or manage iterations (start/stop). Requires Content-Type header with domain-model=launchdarkly.semanticpatch.

Input Parameters

string
Optional comment describing the purpose or reason for these changes. Useful for audit trails and team communication.
string
required
The project key identifying the LaunchDarkly project containing the experiment. Use LIST_PROJECTS to discover available project keys.
array
required
Array of instruction objects specifying the changes to apply to the experiment. Each instruction has a ‘kind’ field indicating the operation type and an optional ‘value’ field for the operation’s data.
string
required
The unique key identifying the experiment to update.
string
required
The environment key where the experiment is located. Common values include ‘production’, ‘staging’, ‘test’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_EXPIRING_TARGETSTool to update expiring context targets on a feature flag. Use when you need to add, update, or remove scheduled target expirations.

Input Parameters

string
Optional comment describing the change. This will be recorded in the audit log.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
array
required
Array of instructions to apply to the expiring targets. Each instruction specifies an operation (add, update, or remove) and the associated target details. Multiple instructions can be provided to perform batch updates.
string
required
The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys.
string
required
The feature flag key identifying the flag with expiring targets. Use GET_FEATURE_FLAGS to discover available flag keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_FEATURE_FLAGTool to update a feature flag’s settings using JSON Patch operations. Use when you need to modify flag configuration like description, name, tags, archived status, or other flag properties.

Input Parameters

array
required
Array of JSON Patch operations to apply to the feature flag. Each operation modifies a specific field like description, name, tags, temporary, archived, or maintainerId. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
boolean
If true, the patch will be validated but not persisted. Returns a preview of the flag after the patch is applied without making actual changes. Useful for testing patch operations.
string
Optional comment to describe the reason for the change or provide context about the update.
string
required
The project key identifying the LaunchDarkly project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
string
required
The feature flag key identifying the flag to update. The key identifies the flag in your code.
boolean
If true, the patch will be applied even if it causes a pending scheduled change or approval request to fail. Defaults to false if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_FLAG_CONFIG_APPROVAL_REQUESTTool to perform a partial update to a flag config approval request using semantic patch format. Use when you need to add reviewers to an approval request. Requires special headers: Content-Type with domain-model=launchdarkly.semanticpatch and LD-API-Version: beta.

Input Parameters

string
required
The approval request ID to update. Use GET_APPROVALS_FOR_FLAG to retrieve approval request IDs.
string
required
The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys.
array
required
Array of semantic patch instruction objects specifying the changes to apply to the approval request. Each instruction has a ‘kind’ field and relevant parameters.
string
required
The environment key where the approval request exists. Common values include ‘production’, ‘staging’, ‘test’.
string
required
The feature flag key identifying the specific flag with the approval request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_FLAG_CONFIG_SCHEDULED_CHANGETool to update a scheduled change workflow for a feature flag. Use when you need to modify the execution time or instructions of an existing scheduled change.

Input Parameters

string
required
The unique identifier of the scheduled change to update. Use GET_FLAG_CONFIG_SCHEDULED_CHANGES to list available scheduled changes and their IDs.
string
Optional comment describing the update to the scheduled change. Useful for audit trails and team communication.
string
required
The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys.
array
required
Array of semantic patch instructions to apply to the scheduled change. Each instruction must have a ‘kind’ field specifying the operation type (e.g., ‘updateScheduledChangesExecutionDate’, ‘replaceScheduledChangesInstructions’) and additional fields as required by that instruction type. For updateScheduledChangesExecutionDate, include ‘value’ as a Unix timestamp in milliseconds.
string
required
The environment key where the scheduled change is configured (e.g., ‘production’, ‘staging’). Use GET_ENVIRONMENTS to list available environments.
string
required
The feature flag key identifying the specific flag with the scheduled change to update.
boolean
Whether to succeed (true) or fail (false) when these new instructions conflict with existing scheduled changes. Defaults to false if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_FLAG_DEFAULTS_BY_PROJECTTool to update flag defaults for a project using JSON Patch operations. Use when you need to modify default settings that apply to new flags created in the project, such as tags, temporary status, boolean variation names, or client-side availability.

Input Parameters

array
required
Array of JSON Patch operations to apply to the flag defaults. Each operation modifies fields like tags, temporary, booleanDefaults, or defaultClientSideAvailability. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_FLAG_IMPORT_CONFIGURATIONTool to update a flag import configuration using JSON Patch operations. Use when you need to modify configuration settings like name, tags, or config values. To add to array fields, use ’/<array index>’ where ‘/0’ adds to beginning and ’/-’ adds to end.

Input Parameters

array
required
Array of JSON Patch operations to apply to the flag import configuration. You can update the ‘config’, ‘tags’, and ‘name’ fields. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the flag import configuration to update.
string ("split" | "unleash")
required
The integration key identifying the feature management system from which the import occurs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_HOLDOUTUpdate a LaunchDarkly holdout using semantic patch operations to change its name or description, end it, or remove an experiment. The beta API version header is supplied automatically.

Input Parameters

string
Optional comment describing the update.
string
required
The holdout key identifying the holdout to update.
string
required
The project key identifying the project containing the holdout. Use LIST_PROJECTS to discover available project keys.
array
required
Array of semantic patch instructions to apply to the holdout. Instructions are applied in order.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_MEMBERTool to modify an account member’s information using JSON Patch operations. Use when you need to update member details like name, role, custom roles, or other member attributes.

Input Parameters

string
required
The unique member ID to modify. This is the member’s identifier in LaunchDarkly.
array
required
Array of JSON Patch operations to apply to the member. Each operation modifies a specific field like firstName, lastName, role, or customRoles. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_MEMBERSTool to perform partial updates to multiple LaunchDarkly account members using semantic patch format. Use when you need to bulk update member roles or attributes. Supports updating specific members by ID or all members matching filter criteria.

Input Parameters

string
Optional comment describing the update.
array
required
Array of instruction objects for updating members. Each instruction specifies an operation type (replaceMembersRoles, replaceAllMembersRoles, replaceMembersCustomRoles, replaceAllMembersCustomRoles, or replaceMembersRoleAttributes) and the parameters for that operation.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_METRICTool to update a metric’s settings using JSON Patch operations. Use when you need to modify metric configuration like description, name, tags, or other properties.

Input Parameters

array
required
Array of JSON Patch operations to apply to the metric. Each operation modifies a specific field like description, name, tags, or other metric properties. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The metric key identifying the specific metric to update.
string
required
The project key identifying the project containing the metric. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_METRIC_GROUPTool to update a metric group’s settings using JSON Patch operations. Use when you need to modify metric group configuration like description, name, tags, or other properties.

Input Parameters

array
required
Array of JSON Patch operations to apply to the metric group. Each operation modifies a specific field like description, name, tags, or other metric group properties. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
string
required
The project key identifying the project containing the metric group. Use LIST_PROJECTS to discover available project keys.
string
required
The metric group key identifying the specific metric group to update.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_O_AUTH_CLIENTTool to update an existing OAuth 2.0 client in LaunchDarkly using JSON Patch operations. Use when you need to modify OAuth client details like name, description, or redirect URI. Only ‘name’, ‘description’, and ‘redirectUri’ fields may be patched.

Input Parameters

string
required
The unique client ID of the OAuth 2.0 client to patch. This ID is returned when creating an OAuth client or can be found by listing OAuth clients.
array
required
An array of JSON Patch operations to apply to the OAuth client. Each operation modifies a specific field. Only ‘name’, ‘description’, and ‘redirectUri’ may be patched. Common paths: ‘/name’, ‘/description’, ‘/redirectUri’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_PROJECTTool to update a LaunchDarkly project using JSON Patch operations (RFC 6902). Use when you need to modify specific fields of a project such as name, tags, client-side availability settings, or other project configuration.

Input Parameters

array
required
Array of JSON Patch operations to apply to the project. Operations are applied in order. Common paths: ‘/name’ (project name), ‘/tags’ (project tags), ‘/includeInSnippetByDefault’ (client-side availability), ‘/defaultClientSideAvailability/usingMobileKey’, ‘/defaultClientSideAvailability/usingEnvironmentId’.
string
required
The project key identifying the project to update. Use LIST_PROJECTS to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_RELAY_AUTO_CONFIGTool to update a Relay Proxy auto configuration using JSON Patch operations (RFC 6902). Use when you need to modify specific fields of a relay proxy configuration such as name, policy, or other settings.

Input Parameters

string
required
The relay auto config ID. Use this to uniquely identify the Relay Proxy configuration to update.
array
required
Array of JSON Patch operations to apply to the Relay Proxy configuration. Operations are applied in order.
string
Optional comment describing the reason for this change. Useful for audit trail and team communication.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_REPOSITORYTool to update a code reference repository’s settings using JSON Patch operations. Use when you need to modify repository configuration like default branch, enabled status, or URL templates.

Input Parameters

string
required
The repository name to update. This is the unique identifier for the code reference repository in LaunchDarkly.
array
required
Array of JSON Patch operations to apply to the repository. Each operation modifies a specific field like defaultBranch, enabled, commitUrlTemplate, or hunkUrlTemplate. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_SEGMENTTool to update a segment’s settings using JSON Patch operations. Use when you need to modify segment configuration like description, name, tags, included/excluded targets, or targeting rules.

Input Parameters

array
required
Array of JSON Patch operations to apply to the segment. Each operation modifies a specific field like description, name, tags, included, excluded, or rules. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.
boolean
If true, the patch will be validated but not persisted. Returns a preview of the segment after the patch is applied without making actual changes. Useful for testing patch operations.
string
Optional comment to describe the reason for the change or provide context about the update.
string
required
The project key identifying the LaunchDarkly project containing the segment. Use LIST_PROJECTS to discover available project keys.
string
required
The unique key of the segment to update. This identifies the specific segment within the project and environment.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use GET_ENVIRONMENTS to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_TEAMTool to perform partial updates to a LaunchDarkly team using semantic patch format. Use when you need to update team properties (name, description), manage team members, or modify role attributes. Supports atomic updates with multiple instructions applied together.

Input Parameters

string
Optional comment describing the update for audit purposes.
string
required
The unique key identifying the team to update. Use ‘List Teams’ action to find available team keys.
array
required
Array of instruction objects for updating the team. Each instruction specifies an operation type (e.g., updateDescription, addMembers, removeMembers, updateName) and the parameters for that operation. Multiple instructions can be provided and will be applied atomically.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_TEAMSTool to perform partial updates to multiple LaunchDarkly teams using semantic patch format. Use when you need to bulk add members to multiple teams at once. Supports adding specific members by ID or all members matching filter criteria to teams.

Input Parameters

string
Optional comment describing the update.
array
required
Array of instruction objects for updating teams. Each instruction specifies an operation type (addMembersToTeams or addAllMembersToTeams) and the parameters for that operation.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_TOKENTool to update an access token’s settings using JSON Patch operations. Use when you need to modify token properties like name, description, role, or custom role IDs.

Input Parameters

string
required
The unique identifier (ID) of the access token to update. This ID is returned when creating a token or can be found using the list tokens endpoint.
array
required
Array of JSON Patch operations to apply to the access token. Each operation modifies a specific field like name, description, role, customRoleIds, or defaultApiVersion. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_TRIGGER_WORKFLOWUpdates a flag trigger using semantic patch instruction kinds, such as enabling or disabling the trigger.

Input Parameters

string
required
The unique identifier (ID) of the flag trigger to update. This ID is returned when creating a trigger or can be found using the ‘Get Trigger Workflow by ID’ action.
string
Optional comment describing the reason for this update. Useful for audit trail and team communication.
string
required
The unique key identifying the LaunchDarkly project containing the flag trigger. Use ‘List Projects’ action to find available project keys.
array
required
Array of semantic patch instructions to apply to the trigger. Each instruction specifies an operation like disabling/enabling the trigger or updating its flag actions.
string
required
The environment key where the trigger is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.
string
required
The unique key of the feature flag that has the trigger to update. This is the flag the trigger is associated with.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PATCH_WEBHOOKTool to update a LaunchDarkly webhook using JSON Patch operations (RFC 6902). Use when you need to modify webhook settings such as name, URL, enabled status, tags, or secret.

Input Parameters

string
required
The unique identifier (ID) of the webhook to update. This ID can be obtained from listing webhooks or when creating a webhook.
array
required
Array of JSON Patch operations to apply to the webhook. Operations are applied in order. Common paths: ‘/name’ (webhook name), ‘/url’ (webhook URL), ‘/on’ (enable/disable webhook), ‘/tags’ (webhook tags), ‘/secret’ (webhook secret).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_PUT_FLAG_DEFAULTS_BY_PROJECTTool to create or update flag defaults for a specific project. Use when you need to configure default settings that will be applied to new flags created in the project.

Input Parameters

array
required
A list of default tags for each flag.
boolean
required
Whether the flag should be temporary by default.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
object
required
Default settings for boolean flags.
object
required
Default client-side SDK availability settings for new flags.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_RESET_ENVIRONMENT_MOBILE_KEYTool to reset the mobile SDK key for a specific environment. Use when you need to generate a new mobile key for security purposes or after a key compromise.

Input Parameters

string
required
The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the specific environment whose mobile key should be reset.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_RESET_ENVIRONMENT_SDK_KEYTool to reset the SDK key for a specific environment. Use when you need to rotate keys for security or revoke access. The new SDK key is returned in the response.

Input Parameters

integer
The time at which you want the old SDK key to expire, in UNIX milliseconds. By default, the key expires immediately. During the period between this call and the time when the old SDK key expires, both the old SDK key and the new SDK key will work.
string
required
The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the specific environment whose SDK key should be reset.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_RESET_RELAY_AUTO_CONFIGTool to reset the Relay Proxy configuration key. Use when you need to rotate or regenerate the configuration key for security purposes. The old key will expire immediately by default, or at the time specified in the expiry parameter.

Input Parameters

string
required
The Relay Proxy configuration ID. Use this to uniquely identify the configuration whose key should be reset.
integer
An expiration time for the old Relay Proxy configuration key, expressed as a Unix epoch time in milliseconds. By default, the old key will expire immediately. Provide a future timestamp to allow gradual transition to the new key.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_RESET_TOKENTool to reset a LaunchDarkly access token, generating a new token value. Use when you need to rotate tokens for security or revoke access to the old token.

Input Parameters

string
required
The ID of the access token to update.
integer
An expiration time for the old token key, expressed as a Unix epoch time in milliseconds. By default, the token will expire immediately.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_SEARCH_AUDIT_LOG_ENTRIESSearch audit log entries in LaunchDarkly. Use to find specific actions, changes, or events by filtering with resource specifiers, date ranges, and full-text search. Resource specifiers follow LaunchDarkly’s resource specifier syntax (e.g., ‘proj/*’ for all projects).

Input Parameters

string
Text to search for. You can search for the full or partial name of the resource.
integer
A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries returned occurred after this timestamp.
integer
A limit on the number of audit log entries that return. Set between 1 and 20. The default is 10.
integer
A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries returned occurred before this timestamp.
array
required
Array of resource specifier statements that filter audit log entries by resources and actions. Each statement defines what resources and actions to include or exclude. At least one resource specifier is required.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_SEARCH_CONTEXT_INSTANCESTool to search for context instances within a project and environment. Use when you need to find and retrieve context instances with filtering and pagination support.

Input Parameters

string
Specifies a field by which to sort. LaunchDarkly supports sorting by timestamp in ascending order by specifying ‘ts’ for this value, or descending order by specifying ‘-ts’.
integer
Specifies the maximum number of items in the collection to return (max: 50, default: 20).
string
A comma-separated list of context filters. This endpoint only accepts an ‘applicationId’ filter. To learn more about the filter syntax, read Filtering contexts and context instances.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment within the project.
string
Limits results to context instances with sort values after the value specified. You can use this for pagination, however, we recommend using the ‘next’ link instead.
boolean
Specifies whether to include or omit the total count of matching context instances. Defaults to true.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_SEARCH_CONTEXTSTool to search for contexts in a LaunchDarkly environment with flexible filtering and sorting. Use when you need to find contexts matching specific criteria or patterns.

Input Parameters

string
Specifies a field by which to sort. Use ‘ts’ for ascending order by timestamp, or ‘-ts’ for descending order.
integer
Specifies the maximum number of items in the collection to return. Maximum: 50, default: 20.
string
A comma-separated list of context filters. To learn more about the filter syntax, read Filtering contexts and context instances documentation.
string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
string
required
The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys.
string
Limits results to contexts with sort values after the value specified. You can use this for pagination, however, the ‘next’ link is recommended instead.
boolean
Specifies whether to include or omit the total count of matching contexts. Defaults to true.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_TRIGGER_FLAG_IMPORT_JOBTool to trigger a single flag import run for an existing flag import configuration. Use when you need to manually initiate a flag import from an external feature management system. This action requires the LD-API-Version: beta header.

Input Parameters

string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The unique identifier (ID) of the flag import configuration to trigger.
string
required
The integration key identifying the feature management system from which the import occurs (e.g., ‘split’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_ANNOUNCEMENT_PUBLICTool to update an existing announcement in LaunchDarkly using JSON Patch operations. Use when you need to modify announcement details like title, message, severity, or timing.

Input Parameters

string
required
The unique identifier of the announcement to update. This ID is returned when creating an announcement or can be retrieved by listing announcements.
array
required
An array of JSON Patch operations to apply to the announcement. Each operation modifies a specific field. Common paths: ‘/title’, ‘/message’, ‘/severity’, ‘/startTime’, ‘/endTime’, ‘/isDismissible’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_BIG_SEGMENT_CONTEXT_TARGETSTool to update context targets included or excluded in a big segment. Big segments include larger list-based segments and synced segments. Use this when you need to add or remove specific context targets (users, organizations, etc.) from a big segment’s inclusion or exclusion lists. This operation does not support standard segments.

Input Parameters

object
Context target modification specification for add/remove operations.
object
Context target modification specification for add/remove operations.
string
required
The unique key identifying the LaunchDarkly project containing the segment. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the big segment to update. This operation only supports big segments (larger list-based segments and synced segments), not standard segments.
string
required
The environment key where the segment is configured (e.g., ‘test’, ‘production’). Use ‘Get Environments’ action to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_CONTEXT_FLAG_SETTINGSet a custom feature flag variation for a specific context in a project and environment. The setting must match the flag’s variation type; omitting it sends a null setting.

Input Parameters

string
Optional comment describing the reason for this change.
string
The variation value to set for the context. Must match the flag’s variation type (boolean, string, number, JSON, etc.). For boolean flags, use true or false. For string flags, use the exact variation value string. Omit this field or set to null to erase the context’s custom setting and revert to default targeting behavior.
string
required
The context key identifying the specific context instance (e.g., user ID, organization ID).
string
required
The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys.
string
required
The context kind (e.g., ‘user’, ‘organization’, ‘device’). Context kinds define the type of entity you’re targeting.
string
required
The feature flag key identifying the flag to configure for this context.
string
required
The environment key where the flag is configured (e.g., ‘test’, ‘production’). Use GET_ENVIRONMENTS to list available environments.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_CONTEXT_KINDTool to create or update a context kind in a LaunchDarkly project. Use this to define custom context types for feature flag targeting beyond the default user context.

Input Parameters

string
required
The context kind key to create or update.
string
required
The context kind name. This is the display name for the context kind.
integer
The context kind version. If not specified when the context kind is created, defaults to 1.
boolean
Whether the context kind is archived. Archived context kinds are unavailable for targeting.
string
required
The project key. Use LIST_PROJECTS to discover available project keys.
string
The context kind description. Provides additional context about the purpose of this context kind.
boolean
Alias for archived. Whether to hide this context kind in targeting.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_EXPERIMENTATION_SETTINGSTool to update experimentation settings for a project. Use when you need to configure randomization units for experiments in a project.

Input Parameters

string
required
The project key identifying the project. Use LIST_PROJECTS to discover available project keys.
array
required
An array of randomization units allowed for this project. At least one unit must be specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_INTEGRATION_CONFIGURATIONTool to update an existing integration configuration in LaunchDarkly using JSON Patch operations. Use when you need to modify integration details like name, enabled status, tags, or configuration values.

Input Parameters

array
required
An array of JSON Patch operations to apply to the integration configuration. Each operation modifies a specific field. Common paths: ‘/name’, ‘/enabled’, ‘/tags’, ‘/configValues’, ‘/capabilityConfig’.
string
required
The unique ID of the integration configuration to update. This is returned when creating an integration configuration or can be found by listing existing integration configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_LAYERTool to update a layer using semantic patch instructions. Use when you need to modify layer properties like name, description, or experiment reservations.

Input Parameters

string
Optional comment describing the purpose of the update.
string
required
The layer key identifying the specific layer to update.
string
required
The project key identifying the LaunchDarkly project containing the layer. Use LIST_PROJECTS to discover available project keys.
array
required
Array of semantic patch instructions to apply to the layer. Each instruction specifies a modification to perform. Common instructions: updateName (updates the layer name), updateDescription (updates the layer description), updateExperimentReservation (modifies experiment reservations), removeExperiment (removes an experiment from the layer).
string
The environment key for making environment-specific updates. For example, updating the reservation of an experiment.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_PHASE_STATUSTool to update the execution status of a phase in a feature flag release. Use when you need to start, complete, or pause a release phase in LaunchDarkly.

Input Parameters

string ("active" | "completed" | "paused")
Valid phase status values for release phases.
string
required
The unique key of the feature flag associated with the release.
string
required
The unique identifier of the release phase to update.
array
Extra configuration for audiences required upon phase initialization. Specify audience configurations when starting a phase.
string
required
The unique key identifying the LaunchDarkly project containing the flag. Use ‘List Projects’ action to find available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_RELEASE_PIPELINEUpdate an existing LaunchDarkly release pipeline using its name and complete list of phases and audiences, with optional description and tags.

Input Parameters

string
required
The name of the release pipeline.
array
A list of tags for this release pipeline.
array
required
An ordered list of release pipeline phases. Each phase is a logical grouping of one or more environments that share attributes for rolling out changes.
string
A description of the release pipeline.
string
required
The unique key identifying the LaunchDarkly project. Use ‘List Projects’ action to find available project keys.
string
required
The unique key of the release pipeline to update.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_RELEASE_POLICIES_ORDERTool to update the order of existing release policies for a project. Use when you need to change the priority order in which release policies are applied. The first policy in the list has the highest priority.

Input Parameters

array
required
Ordered list of release policy keys. The order in this array determines the priority order of the policies, with the first item having the highest priority.
string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_RELEASE_POLICYUpdate a project’s release policy for progressive or guarded rollouts using its name and release method, with optional scope and release configuration. The request uses the beta API version.

Input Parameters

string
required
A human-friendly name for the release policy.
object
Target environments and flag tags for a release policy.
string
required
The human-readable key of the release policy to update.
string
required
The project key identifying the project. Use LIST_PROJECTS action to discover available project keys.
string ("guarded-release" | "progressive-release")
required
The release method for this policy: ‘guarded-release’ monitors metrics during rollout, ‘progressive-release’ follows staged rollout without metric monitoring.
object
Configuration for guarded release policies.
object
Configuration for progressive release policies.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPDATE_SUBSCRIPTIONTool to update an audit log subscription configuration using JSON Patch operations. Use when you need to modify subscription settings like name, configuration, enable/disable status, tags, or policy statements.

Input Parameters

string
required
The unique identifier (ID) of the audit log subscription to update. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration.
string
required
The integration key identifying the type of audit log subscription (e.g., ‘datadog’, ‘msteams’, ‘splunk’). This key determines which integration service the subscription belongs to.
array
required
An array of JSON Patch operations to apply to the subscription. Each operation modifies a specific field. Common paths include: ‘/name’ (subscription name), ‘/on’ (enable/disable), ‘/config’ (configuration settings), ‘/tags’ (array of tags), ‘/statements’ (policy statements).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: LAUNCH_DARKLY_UPSERT_BRANCHTool to upsert (create or update) a branch in a LaunchDarkly code reference repository. Use this to sync branch information including HEAD commit, sync time, and flag references. If the branch exists it will be updated, otherwise it will be created.

Input Parameters

string
required
An ID representing the branch HEAD. For example, a commit SHA.
string
required
The branch name.
string
required
The repository name. This is the name of the code reference repository configured in LaunchDarkly.
string
required
The URL-encoded branch name. For branch names with special characters, ensure they are properly URL-encoded.
integer
required
Unix timestamp in milliseconds when the branch is being synced. Use the current time when syncing.
integer
Unix timestamp in milliseconds when the commit was made.
array
An array of flag references found on the branch. Each reference includes the file path and code hunks containing flag keys.
integer
An optional ID used to prevent older data from overwriting newer data. If no sequence ID is included, the newly submitted data will always be saved.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not

Triggers

Slug: LAUNCH_DARKLY_ACCOUNT_MEMBER_EVENTType: webhookTriggers when an account member is invited, removed, or has their role or team membership changed.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The account member to watch, by member id. Use LAUNCH_DARKLY_GET_MEMBERS to list them. Pass * to watch every member.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole account member as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the account member this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole account member as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_ACCOUNT_SETTINGS_EVENTType: webhookTriggers when an account-level setting changes: an announcement is posted, edited or removed, a registered OAuth client is added, edited or removed, or the plan subscription changes.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole account as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the account this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole account as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_CONTEXT_KIND_EVENTType: webhookTriggers when a context kind is created or changed, including when its availability for experiments is switched.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The context kind to watch, by its key. Use LAUNCH_DARKLY_GET_CONTEXT_KINDS_BY_PROJECT_KEY to list them. Pass * to watch every context kind in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole context kind as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the context kind this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole context kind as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_ENVIRONMENT_EVENTType: webhookTriggers when an environment is created or deleted, or when one of its settings changes: name, colour, TTL, tags, criticality, approval settings, required comments, change confirmation, or a rotated SDK or mobile key.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole environment as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the environment this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole environment as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_EXPERIMENT_EVENTType: webhookTriggers when an experiment is created, changed or archived. LaunchDarkly archives experiments rather than deleting them.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The experiment to watch, by experiment key. Use LAUNCH_DARKLY_GET_EXPERIMENTS to list them. Pass * to watch every experiment in the environment.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the experiment this entry refers to.
object
The resource that contains the one a change was made to.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_EXPERIMENT_LAYER_EVENTType: webhookTriggers when an experiment layer is created or changed. LaunchDarkly has no delete operation for a layer.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The experiment layer to watch, by layer key. Use LAUNCH_DARKLY_GET_LAYERS to list them. Pass * to watch every layer in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole experiment layer as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the experiment layer this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole experiment layer as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_FEATURE_FLAG_EVENTType: webhookTriggers when a feature flag changes: created, toggled on or off, its targeting rules, variations, prerequisites or fallthrough edited, renamed, retagged, archived, deleted, a flag link added or removed, or an approval request on it raised, reviewed or applied.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The feature flag to watch, by flag key (e.g. new-checkout). Use LAUNCH_DARKLY_GET_FEATURE_FLAGS to list them. Pass * to watch every flag in the environment.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole feature flag as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the feature flag this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole feature flag as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_HOLDOUT_EVENTType: webhookTriggers when a holdout is created, renamed or has its description changed. LaunchDarkly has no delete operation for a holdout.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The holdout to watch, by holdout key. Use LAUNCH_DARKLY_GET_ALL_HOLDOUTS to list them. Pass * to watch every holdout in the environment.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the holdout this entry refers to.
object
The resource that contains the one a change was made to.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_INTEGRATION_EVENTType: webhookTriggers when an integration is configured on the account, reconfigured, renamed or removed.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The integration to watch, by its configuration id. Use LAUNCH_DARKLY_GET_ALL_INTEGRATION_CONFIGURATIONS to list them. Pass * to watch every integration on the account.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the integration this entry refers to.
object
The resource that contains the one a change was made to.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_METRIC_EVENTType: webhookTriggers when a metric is created, renamed, re-described, retagged or deleted.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The metric to watch, by metric key. Use LAUNCH_DARKLY_LIST_METRICS to list them. Pass * to watch every metric in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole metric as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the metric this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole metric as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_METRIC_GROUP_EVENTType: webhookTriggers when a metric group is created, renamed or deleted.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The metric group to watch, by its key. Use LAUNCH_DARKLY_LIST_METRIC_GROUPS to list them. Pass * to watch every metric group in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole metric group as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the metric group this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole metric group as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_PROJECT_EVENTType: webhookTriggers when a project is created or deleted, or when its name, tags, flag defaults or client-side snippet default change.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole project as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the project this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole project as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_SDK_KEY_EVENTType: webhookTriggers when an environment’s SDK key is created, rotated or deleted. The key itself is never sent.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.
string
required
The SDK key to watch, by its id. The id is the _id of the key as it appears on the environment. Pass * to watch every SDK key in the environment.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the SDK key this entry refers to.
object
The resource that contains the one a change was made to.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_SEGMENT_EVENTType: webhookTriggers when a segment changes: created, deleted, renamed, re-described, retagged, its rules or included / excluded membership edited, its expiring targets changed, or a big-segment export started.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly environment to watch, by environment key (e.g. production). Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list them. Pass * to watch every environment in the project.
string
required
The LaunchDarkly project to watch, by project key (e.g. default). Use LAUNCH_DARKLY_LIST_PROJECTS to list them. Pass * to watch every project.
string
required
The segment to watch, by segment key. Use LAUNCH_DARKLY_GET_SEGMENTS to list them. Pass * to watch every segment in the environment.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole segment as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the segment this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole segment as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_SERVICE_TOKEN_EVENTType: webhookTriggers when a service token is created, renamed, reset or deleted. Only the token’s last four characters are ever sent.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The service token to watch, by token id. Use LAUNCH_DARKLY_GET_TOKENS to list them. Pass * to watch every service token on the account.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole service token as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the service token this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole service token as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.
Slug: LAUNCH_DARKLY_WEBHOOK_EVENTType: webhookTriggers when a LaunchDarkly webhook is created, renamed, retagged, switched on or off, has its statements rewritten, or is deleted.

Configuration

array
The LaunchDarkly role actions to receive — for example updateOn for a flag toggle, or createFlag for new flags only. The full vocabulary is at https://launchdarkly.com/docs/home/account/roles/role-actions. Leave unset to receive every action on the resource.
string
required
The LaunchDarkly webhook to watch, by its id. Use LAUNCH_DARKLY_GET_ALL_WEBHOOKS to list them. Pass * to watch every webhook on the account.

Payload

array
required
Every action performed in this change, and the resource specifier it was performed on. One entry can carry several distinct actions, and repeats an action per environment for a change made across environments.
object
The authorized OAuth application that made a change.
string
Comment supplied with the change. Present on semantic-patch and approval-flow changes, absent on plain JSON-patch calls.
object
The whole webhook as it stands after the change, forwarded as LaunchDarkly sends it.
integer
required
When the change happened, as epoch MILLISECONDS. LaunchDarkly does not guarantee chronological delivery and recommends ordering on this field.
string
What changed, as LaunchDarkly’s own diff, forwarded as-is. The shape varies by the kind of change — a JSON Patch array, a wrapper object around one, or a per-collection added/removed diff — so read it defensively. Absent on changes that carry a comment instead.
string
required
Markdown description of the change. Can be the empty string for API-driven changes.
object
The person who made a change.
string
required
Name of the webhook this entry refers to.
object
The resource that contains the one a change was made to.
object
The whole webhook as it stood before the change, forwarded as LaunchDarkly sends it.
An AI Config a change also touched.
An experiment a change came from.
A feature flag a change also touched.
string
required
Shorter markdown description of the change. Can be the empty string.
object
A non-member that initiated a change.
object
The resource a change was made to.
string
Full markdown sentence “<actor> <titleVerb> <target>”, with links.
string
The action in words, e.g. “turned on the flag” / “turned off the flag” — the only place a toggle’s DIRECTION is spelled out, since both arrive as action updateOn.
object
The access token a change was made with.
object
Body of the external trigger that caused this change, when it came from a LaunchDarkly flag trigger.