Automate LaunchDarkly
HumDay reads LaunchDarkly’s own published API description and derives 105 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What LaunchDarkly is
Build custom integrations with the LaunchDarkly REST API
API host: app.launchdarkly.com
What HumDay can do in LaunchDarkly
52 documented operations change something in LaunchDarkly. The 49 most useful are listed here.
- POSTCreate a new integration subscription of a given kind.
/integrations/{integrationKey} - POSTCreate a new custom role.
/roles - POSTCreate a new token.
/tokens - POSTInvite new members.
/members - POSTCreate a new project with the given key and name.
/projects - POSTCreate a webhook.
/webhooks - POSTCreate a new relay proxy config.
/account/relay-auto-configs - POSTCreates a new user segment.
/segments/{projectKey}/{environmentKey} - POSTCreates a new feature flag.
/flags/{projectKey} - POSTCreate a new environment in a specified project with a given name, key, and swatch color.
/projects/{projectKey}/environments - POSTCreate a new data export destination
/destinations/{projectKey}/{environmentKey} - DELETEDelete a webhook by ID.
/webhooks/{resourceId} - PATCHModify a webhook by ID.
/webhooks/{resourceId} - PATCHUpdate, add, or delete expiring user targets for a single user on all flags
/users/{projectKey}/{userKey}/expiring-user-targets/{environmentKey} - DELETEDelete a user by ID.
/users/{projectKey}/{environmentKey}/{userKey} - DELETEDelete an access token by ID.
/tokens/{tokenId} - PATCHModify an access token by ID.
/tokens/{tokenId} - DELETEDelete a team member by ID.
/members/{memberId} - PATCHModify a team member by ID.
/members/{memberId} - DELETEDelete an integration subscription by ID.
/integrations/{integrationKey}/{integrationId} - PATCHModify an integration subscription by ID.
/integrations/{integrationKey}/{integrationId} - DELETEDelete a project by key.
/projects/{projectKey} - PATCHModify a project by ID.
/projects/{projectKey} - DELETEDelete a custom role by key.
/roles/{customRoleKey} - PATCHModify a custom role by key.
/roles/{customRoleKey} - POSTUpdate targets included or excluded in a big segment
/segments/{projectKey}/{environmentKey}/{userSegmentKey}/users - POSTReset an access token's secret key with an optional expiry time for the old key.
/tokens/{tokenId}/reset - PATCHUpdate, add, or delete expiring user targets on feature flag
/flags/{projectKey}/{featureFlagKey}/expiring-user-targets/{environmentKey} - PATCHUpdate, add, or delete expiring user targets on user segment
/segments/{projectKey}/{userSegmentKey}/expiring-user-targets/{environmentKey} - DELETEDelete a relay proxy configuration by ID.
/account/relay-auto-configs/{id} - PATCHModify a relay proxy configuration by ID.
/account/relay-auto-configs/{id} - DELETEDelete a user segment.
/segments/{projectKey}/{environmentKey}/{userSegmentKey} - PATCHPerform a partial update to a user segment.
/segments/{projectKey}/{environmentKey}/{userSegmentKey} - DELETEDelete a feature flag in all environments.
/flags/{projectKey}/{featureFlagKey} - PATCHPerform a partial update to a feature.
/flags/{projectKey}/{featureFlagKey} - PUTSpecifically enable or disable a feature flag for a user based on their key.
/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey} - POSTReset a relay proxy configuration's secret key with an optional expiry time for the old key.
/account/relay-auto-configs/{id}/reset - POSTCopies the feature flag configuration from one environment to the same feature flag in another environment.
/flags/{projectKey}/{featureFlagKey}/copy - POSTCreates a new scheduled change for a feature flag.
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes - DELETEDelete an environment in a specific project.
/projects/{projectKey}/environments/{environmentKey} - PATCHModify an environment by ID.
/projects/{projectKey}/environments/{environmentKey} - DELETEGet a single data export destination by ID
/destinations/{projectKey}/{environmentKey}/{destinationId} - PATCHPerform a partial update to a data export destination.
/destinations/{projectKey}/{environmentKey}/{destinationId} - POSTReset an environment's SDK key with an optional expiry time for the old key.
/projects/{projectKey}/environments/{environmentKey}/apiKey - POSTReset an environment's mobile key.
/projects/{projectKey}/environments/{environmentKey}/mobileKey - POSTCreate an approval request for a feature flag config
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{approvalRequestId} - POSTLists conflicts between the given instructions and any existing scheduled changes for the feature flag.
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes-conflicts - DELETEDelete an approval request for a feature flag config
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests/{approvalRequestId} - DELETEDelete a scheduled change on a feature flag in an environment.
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes/{scheduledChangeId}
What HumDay can read from LaunchDarkly
These are the operations a schedule or a trigger can watch.
- GETSearch users in LaunchDarkly based on their last active date, or a search query.
/user-search/{projectKey}/{environmentKey} - GETGet events usage by event type.
/usage/events/{type} - GETGet monthly active user data.
/usage/mau - GETGet events usage endpoints.
/usage/events - GETReturns a list of all streams.
/usage/streams - GETYou can issue a GET request to the root resource to find all of the resource categories supported by the API.
/ - GETGet monthly active user data by category.
/usage/mau/bycategory - GETReturn a complete list of custom roles.
/roles - GETReturns of the usage endpoints available.
/usage - GETGet events usage by event id and the feature flag key.
/usage/evaluations/{envId}/{flagKey} - GETReturns a list of tokens in the account.
/tokens - GETReturns a list of all members in the account.
/members - GETReturns a list of all projects in the account.
/projects - GETFetch a list of all webhooks.
/webhooks - GETReturns a list of all data export destinations.
/destinations - GETList all users in the environment.
/users/{projectKey}/{environmentKey} - GETReturns a list of relay proxy configurations in the account.
/account/relay-auto-configs - GETGet a list of all user segments in the given project.
/segments/{projectKey}/{environmentKey} - GETGet a list of all features in the given project.
/flags/{projectKey} - GETGet a webhook by ID.
/webhooks/{resourceId} - GETGet a list of all configured integrations of a given kind.
/integrations/{integrationKey} - GETGet a stream endpoint and return timeseries data.
/usage/streams/{source} - GETGet the current team member associated with the token
/members/me - GETGet a user by key.
/users/{projectKey}/{environmentKey}/{userKey} - GETGet a stream timeseries data by source and show all sdk version associated.
/usage/streams/{source}/sdkversions - GETGet a stream timeseries data by source show sdk version metadata.
/usage/streams/{source}/bysdkversion - GETGet a single access token by ID.
/tokens/{tokenId} - GETGet a list of statuses for all feature flags.
/flag-statuses/{projectKey}/{environmentKey} - GETGet a single team member by ID.
/members/{memberId} - GETGet a single integration subscription by ID.
/integrations/{integrationKey}/{integrationId} - GETFetch a single project by key.
/projects/{projectKey} - GETGet one custom role by key.
/roles/{customRoleKey} - GETFetch a single flag setting for a user by key.
/users/{projectKey}/{environmentKey}/{userKey}/flags - GETGet expiring dates on flags for user
/users/{projectKey}/{userKey}/expiring-user-targets/{environmentKey} - GETGet a single relay proxy configuration by ID.
/account/relay-auto-configs/{id} - GETGet a single user segment by key.
/segments/{projectKey}/{environmentKey}/{userSegmentKey} - GETGet a single feature flag by key.
/flags/{projectKey}/{featureFlagKey} - GETFetch a single flag setting for a user by key.
/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey} - GETGet the status for a particular feature flag across environments
/flag-status/{projectKey}/{featureFlagKey} - GETGet a list of all configured audit log event integrations associated with this account.
/integrations - GETGet expiring user targets for feature flag
/flags/{projectKey}/{featureFlagKey}/expiring-user-targets/{environmentKey} - GETGet dependent flags across all environments for the flag specified in the path parameters
/flags/{projectKey}/{featureFlagKey}/dependent-flags - GETGet an environment given a project and key.
/projects/{projectKey}/environments/{environmentKey} - GETGet expiring user targets for user segment
/segments/{projectKey}/{userSegmentKey}/expiring-user-targets/{environmentKey} - GETGet a single data export destination by ID
/destinations/{projectKey}/{environmentKey}/{destinationId} - GETGet the status for a particular feature flag.
/flag-statuses/{projectKey}/{environmentKey}/{featureFlagKey} - GETGet a list of all audit log entries.
/auditlog - GETGet dependent flags for the flag in the environment specified in path parameters
/flags/{projectKey}/{environmentKey}/{featureFlagKey}/dependent-flags - GETGet all approval requests for a feature flag config
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/approval-requests - GETGet all scheduled workflows for a feature flag by key.
/projects/{projectKey}/flags/{featureFlagKey}/environments/{environmentKey}/scheduled-changes - GETUse this endpoint to fetch a single audit log entry by its resouce ID.
/auditlog/{resourceId}
How automating LaunchDarkly works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live LaunchDarkly account.
- Grant access, then go live. You approve the specific LaunchDarkly operations it may use — and only those.
Popular LaunchDarkly integrations
Connect LaunchDarkly to the tools people pair it with most.
- LaunchDarkly and OData for namespace microsoft.graphintegration
- LaunchDarkly and Cloudflareintegration
- LaunchDarkly and NetBoxintegration
- LaunchDarkly and GitHubintegration
- LaunchDarkly and Mistintegration
- LaunchDarkly and Loket.nlintegration
- LaunchDarkly and Atlassian The Jira Cloud platformintegration
- LaunchDarkly and Magento B2Bintegration
- LaunchDarkly and Stripeintegration
- LaunchDarkly and Zuora Reference Billingintegration
- LaunchDarkly and bunqintegration
- LaunchDarkly and DocuSignintegration
Automate LaunchDarkly with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about LaunchDarkly automation
- Can HumDay connect to LaunchDarkly?
- Yes. HumDay reads LaunchDarkly's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 105 operations are documented.
- Do I need to write code to automate LaunchDarkly?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your LaunchDarkly account.
- What can HumDay do in LaunchDarkly?
- 52 of the 105 documented operations change something in LaunchDarkly, and 53 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my LaunchDarkly account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to LaunchDarkly is held behind that approval.
Where this came from
The operations above are read from a published API description for LaunchDarkly at launchdarkly.github.io/ld-openapi/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2021-07-19.