launchdarkly_api 8.0.0 → 10.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +151 -150
- data/docs/AccountMembersApi.md +12 -12
- data/docs/ActionInputRep.md +2 -2
- data/docs/ApprovalConditionInputRep.md +3 -1
- data/docs/ApprovalsApi.md +10 -10
- data/docs/AuditLogApi.md +1 -1
- data/docs/Client.md +32 -0
- data/docs/ClientCollection.md +20 -0
- data/docs/ClientSideAvailabilityPost.md +4 -4
- data/docs/CodeReferencesApi.md +15 -15
- data/docs/ConditionInputRep.md +6 -4
- data/docs/CreateCopyFlagConfigApprovalRequestRequest.md +12 -10
- data/docs/CreateFlagConfigApprovalRequestRequest.md +10 -8
- data/docs/CredibleIntervalRep.md +20 -0
- data/docs/CustomProperty.md +4 -4
- data/docs/CustomRolePost.md +3 -3
- data/docs/CustomRolePostData.md +3 -3
- data/docs/CustomRolesApi.md +1 -1
- data/docs/CustomWorkflowInputRep.md +7 -5
- data/docs/DataExportDestinationsApi.md +7 -7
- data/docs/DefaultClientSideAvailabilityPost.md +4 -4
- data/docs/Defaults.md +4 -4
- data/docs/Destination.md +8 -8
- data/docs/DestinationPost.md +8 -8
- data/docs/Destinations.md +2 -2
- data/docs/Environments.md +22 -0
- data/docs/EnvironmentsApi.md +83 -1
- data/docs/EvaluationReason.md +28 -0
- data/docs/Experiment.md +36 -0
- data/docs/ExperimentBayesianResultsRep.md +22 -0
- data/docs/ExperimentCollectionRep.md +22 -0
- data/docs/ExperimentExpandableProperties.md +20 -0
- data/docs/ExperimentInfoRep.md +1 -1
- data/docs/ExperimentPatchInput.md +20 -0
- data/docs/ExperimentPost.md +26 -0
- data/docs/{ExperimentResultsRep.md → ExperimentResults.md} +2 -2
- data/docs/ExperimentsBetaApi.md +484 -14
- data/docs/FeatureFlag.md +5 -7
- data/docs/FeatureFlagBody.md +9 -11
- data/docs/FeatureFlagConfig.md +4 -4
- data/docs/FeatureFlagScheduledChange.md +6 -6
- data/docs/FeatureFlagScheduledChanges.md +2 -2
- data/docs/FeatureFlagsApi.md +14 -14
- data/docs/FeatureFlagsBetaApi.md +2 -2
- data/docs/FlagConfigApprovalRequestResponse.md +18 -18
- data/docs/FlagCopyConfigEnvironment.md +2 -2
- data/docs/FlagCopyConfigPost.md +5 -5
- data/docs/FlagFollowersByProjEnvGetRep.md +20 -0
- data/docs/FlagFollowersGetRep.md +20 -0
- data/docs/FlagGlobalAttributesRep.md +5 -7
- data/docs/FlagInput.md +20 -0
- data/docs/FlagLinkPost.md +10 -10
- data/docs/FlagLinksBetaApi.md +1 -1
- data/docs/FlagRep.md +22 -0
- data/docs/FlagScheduledChangesInput.md +2 -2
- data/docs/FlagSummary.md +2 -0
- data/docs/FlagTriggerInput.md +4 -4
- data/docs/FlagTriggersApi.md +3 -3
- data/docs/FollowFlagMember.md +28 -0
- data/docs/FollowFlagsApi.md +311 -0
- data/docs/FollowersPerFlag.md +20 -0
- data/docs/ForbiddenErrorRep.md +3 -3
- data/docs/InstructionUserRequest.md +26 -0
- data/docs/Integration.md +15 -15
- data/docs/IntegrationAuditLogSubscriptionsApi.md +2 -2
- data/docs/IntegrationDeliveryConfigurationPost.md +6 -6
- data/docs/IntegrationDeliveryConfigurationsBetaApi.md +1 -1
- data/docs/InvalidRequestErrorRep.md +3 -3
- data/docs/IterationExpandableProperties.md +20 -0
- data/docs/IterationInput.md +26 -0
- data/docs/IterationRep.md +42 -0
- data/docs/{ExperimentRep.md → LegacyExperimentRep.md} +2 -2
- data/docs/Member.md +4 -2
- data/docs/MemberTeamsPostInput.md +1 -1
- data/docs/MethodNotAllowedErrorRep.md +3 -3
- data/docs/MetricInput.md +20 -0
- data/docs/MetricPost.md +24 -24
- data/docs/MetricRep.md +1 -1
- data/docs/MetricV2Rep.md +24 -0
- data/docs/MetricsApi.md +2 -2
- data/docs/NewMemberForm.md +7 -7
- data/docs/NotFoundErrorRep.md +3 -3
- data/docs/OAuth2ClientsBetaApi.md +365 -0
- data/docs/OauthClientPost.md +22 -0
- data/docs/OtherApi.md +3 -3
- data/docs/ParameterDefault.md +22 -0
- data/docs/ParameterRep.md +20 -0
- data/docs/ParentResourceRep.md +1 -1
- data/docs/PatchFailedErrorRep.md +3 -3
- data/docs/PatchFlagsRequest.md +20 -0
- data/docs/PatchSegmentInstruction.md +7 -7
- data/docs/PatchSegmentRequest.md +1 -1
- data/docs/PatchUsersRequest.md +20 -0
- data/docs/PatchWithComment.md +1 -1
- data/docs/PermissionGrantInput.md +6 -6
- data/docs/PostApprovalRequestApplyRequest.md +2 -2
- data/docs/PostApprovalRequestReviewRequest.md +4 -4
- data/docs/PostFlagScheduledChangesInput.md +2 -2
- data/docs/Project.md +1 -1
- data/docs/ProjectPost.md +1 -1
- data/docs/ProjectRep.md +32 -0
- data/docs/ProjectSummary.md +3 -3
- data/docs/Projects.md +3 -1
- data/docs/ProjectsApi.md +37 -22
- data/docs/RateLimitedErrorRep.md +2 -2
- data/docs/RelativeDifferenceRep.md +22 -0
- data/docs/RelayAutoConfigPost.md +1 -1
- data/docs/RelayAutoConfigRep.md +1 -1
- data/docs/RelayProxyConfigurationsApi.md +5 -5
- data/docs/RepositoryPost.md +4 -4
- data/docs/ResourceAccess.md +1 -1
- data/docs/ReviewResponse.md +6 -6
- data/docs/RuleClause.md +22 -0
- data/docs/ScheduleConditionInputRep.md +4 -4
- data/docs/ScheduledChangesApi.md +8 -8
- data/docs/SegmentBody.md +6 -6
- data/docs/SegmentsApi.md +9 -9
- data/docs/SegmentsBetaApi.md +12 -6
- data/docs/SourceFlag.md +4 -4
- data/docs/StageInputRep.md +6 -4
- data/docs/StatementPost.md +4 -4
- data/docs/StatementPostData.md +4 -4
- data/docs/StatisticCollectionRep.md +2 -2
- data/docs/StatisticRep.md +14 -12
- data/docs/StatisticsRep.md +20 -0
- data/docs/StatusConflictErrorRep.md +3 -3
- data/docs/SubscriptionPost.md +7 -7
- data/docs/TargetResourceRep.md +1 -1
- data/docs/Team.md +13 -5
- data/docs/TeamCustomRole.md +2 -2
- data/docs/TeamCustomRoles.md +2 -2
- data/docs/TeamMaintainers.md +3 -3
- data/docs/TeamMembers.md +18 -0
- data/docs/TeamPatchInput.md +3 -3
- data/docs/TeamPostInput.md +7 -7
- data/docs/TeamProjects.md +1 -1
- data/docs/TeamRepExpandableProperties.md +24 -0
- data/docs/Teams.md +2 -2
- data/docs/TeamsApi.md +620 -0
- data/docs/Token.md +1 -1
- data/docs/TreatmentInput.md +24 -0
- data/docs/TreatmentParameterInput.md +20 -0
- data/docs/TreatmentRep.md +26 -0
- data/docs/TreatmentResultRep.md +30 -0
- data/docs/TriggerPost.md +6 -6
- data/docs/UnauthorizedErrorRep.md +3 -3
- data/docs/UserFlagSetting.md +6 -4
- data/docs/UserFlagSettings.md +1 -1
- data/docs/UserRecord.md +1 -1
- data/docs/UserSegment.md +24 -24
- data/docs/UserSegments.md +2 -2
- data/docs/UserSettingsApi.md +10 -10
- data/docs/Users.md +1 -1
- data/docs/UsersApi.md +6 -6
- data/docs/UsersRep.md +22 -0
- data/docs/ValuePut.md +4 -4
- data/docs/Variation.md +1 -1
- data/docs/Webhook.md +9 -9
- data/docs/Webhooks.md +2 -2
- data/docs/WebhooksApi.md +1 -1
- data/docs/WorkflowTemplateMetadata.md +18 -0
- data/docs/WorkflowTemplateParameter.md +24 -0
- data/docs/WorkflowsBetaApi.md +5 -5
- data/launchdarkly_api.gemspec +3 -3
- data/lib/launchdarkly_api/api/access_tokens_api.rb +2 -2
- data/lib/launchdarkly_api/api/account_members_api.rb +14 -14
- data/lib/launchdarkly_api/api/account_usage_beta_api.rb +2 -2
- data/lib/launchdarkly_api/api/approvals_api.rb +16 -16
- data/lib/launchdarkly_api/api/audit_log_api.rb +4 -4
- data/lib/launchdarkly_api/api/code_references_api.rb +22 -22
- data/lib/launchdarkly_api/api/custom_roles_api.rb +2 -2
- data/lib/launchdarkly_api/api/data_export_destinations_api.rb +10 -10
- data/lib/launchdarkly_api/api/environments_api.rb +79 -4
- data/lib/launchdarkly_api/api/experiments_beta_api.rb +509 -20
- data/lib/launchdarkly_api/api/feature_flags_api.rb +23 -23
- data/lib/launchdarkly_api/api/feature_flags_beta_api.rb +6 -6
- data/lib/launchdarkly_api/api/flag_links_beta_api.rb +4 -4
- data/lib/launchdarkly_api/api/flag_triggers_api.rb +6 -6
- data/lib/launchdarkly_api/api/follow_flags_api.rb +328 -0
- data/lib/launchdarkly_api/api/integration_audit_log_subscriptions_api.rb +4 -4
- data/lib/launchdarkly_api/api/integration_delivery_configurations_beta_api.rb +4 -4
- data/lib/launchdarkly_api/api/metrics_api.rb +4 -4
- data/lib/launchdarkly_api/api/o_auth2_clients_beta_api.rb +347 -0
- data/lib/launchdarkly_api/api/other_api.rb +8 -8
- data/lib/launchdarkly_api/api/projects_api.rb +31 -16
- data/lib/launchdarkly_api/api/relay_proxy_configurations_api.rb +10 -10
- data/lib/launchdarkly_api/api/scheduled_changes_api.rb +14 -14
- data/lib/launchdarkly_api/api/segments_api.rb +18 -18
- data/lib/launchdarkly_api/api/segments_beta_api.rb +15 -4
- data/lib/launchdarkly_api/api/tags_api.rb +2 -2
- data/lib/launchdarkly_api/api/teams_api.rb +577 -0
- data/lib/launchdarkly_api/api/user_settings_api.rb +19 -19
- data/lib/launchdarkly_api/api/users_api.rb +9 -9
- data/lib/launchdarkly_api/api/users_beta_api.rb +2 -2
- data/lib/launchdarkly_api/api/webhooks_api.rb +4 -4
- data/lib/launchdarkly_api/api/workflows_beta_api.rb +10 -10
- data/lib/launchdarkly_api/api_client.rb +5 -3
- data/lib/launchdarkly_api/api_error.rb +2 -2
- data/lib/launchdarkly_api/configuration.rb +9 -4
- data/lib/launchdarkly_api/models/access.rb +3 -2
- data/lib/launchdarkly_api/models/access_allowed_reason.rb +3 -2
- data/lib/launchdarkly_api/models/access_allowed_rep.rb +3 -2
- data/lib/launchdarkly_api/models/access_denied.rb +3 -2
- data/lib/launchdarkly_api/models/access_denied_reason.rb +3 -2
- data/lib/launchdarkly_api/models/access_token_post.rb +3 -2
- data/lib/launchdarkly_api/models/action_input_rep.rb +4 -2
- data/lib/launchdarkly_api/models/action_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/approval_condition_input_rep.rb +18 -6
- data/lib/launchdarkly_api/models/approval_condition_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/approval_settings.rb +3 -2
- data/lib/launchdarkly_api/models/audit_log_entry_listing_rep.rb +3 -2
- data/lib/launchdarkly_api/models/audit_log_entry_listing_rep_collection.rb +3 -2
- data/lib/launchdarkly_api/models/audit_log_entry_rep.rb +3 -2
- data/lib/launchdarkly_api/models/authorized_app_data_rep.rb +3 -2
- data/lib/launchdarkly_api/models/big_segment_target.rb +3 -2
- data/lib/launchdarkly_api/models/branch_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/branch_rep.rb +3 -2
- data/lib/launchdarkly_api/models/clause.rb +3 -2
- data/lib/launchdarkly_api/models/client.rb +321 -0
- data/lib/launchdarkly_api/models/client_collection.rb +243 -0
- data/lib/launchdarkly_api/models/client_side_availability.rb +3 -2
- data/lib/launchdarkly_api/models/client_side_availability_post.rb +5 -2
- data/lib/launchdarkly_api/models/condition_base_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/condition_input_rep.rb +17 -3
- data/lib/launchdarkly_api/models/condition_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/confidence_interval_rep.rb +3 -2
- data/lib/launchdarkly_api/models/conflict.rb +3 -2
- data/lib/launchdarkly_api/models/conflict_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/copied_from_env.rb +3 -2
- data/lib/launchdarkly_api/models/create_copy_flag_config_approval_request_request.rb +42 -9
- data/lib/launchdarkly_api/models/create_flag_config_approval_request_request.rb +20 -12
- data/lib/launchdarkly_api/models/credible_interval_rep.rb +228 -0
- data/lib/launchdarkly_api/models/custom_property.rb +5 -2
- data/lib/launchdarkly_api/models/custom_role.rb +3 -2
- data/lib/launchdarkly_api/models/custom_role_post.rb +3 -2
- data/lib/launchdarkly_api/models/custom_role_post_data.rb +3 -2
- data/lib/launchdarkly_api/models/custom_roles.rb +3 -2
- data/lib/launchdarkly_api/models/custom_workflow_input_rep.rb +19 -6
- data/lib/launchdarkly_api/models/custom_workflow_meta.rb +3 -2
- data/lib/launchdarkly_api/models/custom_workflow_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/custom_workflow_stage_meta.rb +3 -2
- data/lib/launchdarkly_api/models/custom_workflows_listing_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/default_client_side_availability_post.rb +5 -2
- data/lib/launchdarkly_api/models/defaults.rb +5 -2
- data/lib/launchdarkly_api/models/dependent_flag.rb +3 -2
- data/lib/launchdarkly_api/models/dependent_flag_environment.rb +3 -2
- data/lib/launchdarkly_api/models/dependent_flags_by_environment.rb +3 -2
- data/lib/launchdarkly_api/models/destination.rb +9 -2
- data/lib/launchdarkly_api/models/destination_post.rb +7 -3
- data/lib/launchdarkly_api/models/destinations.rb +5 -2
- data/lib/launchdarkly_api/models/environment.rb +3 -2
- data/lib/launchdarkly_api/models/environment_post.rb +3 -2
- data/lib/launchdarkly_api/models/environments.rb +241 -0
- data/lib/launchdarkly_api/models/evaluation_reason.rb +275 -0
- data/lib/launchdarkly_api/models/execution_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment.rb +329 -0
- data/lib/launchdarkly_api/models/experiment_allocation_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_bayesian_results_rep.rb +241 -0
- data/lib/launchdarkly_api/models/experiment_collection_rep.rb +241 -0
- data/lib/launchdarkly_api/models/experiment_enabled_period_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_environment_setting_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_expandable_properties.rb +230 -0
- data/lib/launchdarkly_api/models/experiment_info_rep.rb +4 -3
- data/lib/launchdarkly_api/models/experiment_metadata_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_patch_input.rb +236 -0
- data/lib/launchdarkly_api/models/experiment_post.rb +275 -0
- data/lib/launchdarkly_api/models/experiment_results.rb +281 -0
- data/lib/launchdarkly_api/models/experiment_stats_rep.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_time_series_slice.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_time_series_variation_slice.rb +3 -2
- data/lib/launchdarkly_api/models/experiment_totals_rep.rb +3 -2
- data/lib/launchdarkly_api/models/expiring_user_target_error.rb +3 -2
- data/lib/launchdarkly_api/models/expiring_user_target_get_response.rb +3 -2
- data/lib/launchdarkly_api/models/expiring_user_target_item.rb +3 -2
- data/lib/launchdarkly_api/models/expiring_user_target_patch_response.rb +3 -2
- data/lib/launchdarkly_api/models/export.rb +3 -2
- data/lib/launchdarkly_api/models/extinction.rb +3 -2
- data/lib/launchdarkly_api/models/extinction_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/feature_flag.rb +6 -15
- data/lib/launchdarkly_api/models/feature_flag_body.rb +7 -16
- data/lib/launchdarkly_api/models/feature_flag_config.rb +3 -22
- data/lib/launchdarkly_api/models/feature_flag_scheduled_change.rb +7 -2
- data/lib/launchdarkly_api/models/feature_flag_scheduled_changes.rb +5 -2
- data/lib/launchdarkly_api/models/feature_flag_status.rb +3 -2
- data/lib/launchdarkly_api/models/feature_flag_status_across_environments.rb +3 -2
- data/lib/launchdarkly_api/models/feature_flag_statuses.rb +3 -2
- data/lib/launchdarkly_api/models/feature_flags.rb +3 -2
- data/lib/launchdarkly_api/models/file_rep.rb +3 -2
- data/lib/launchdarkly_api/models/flag_config_approval_request_response.rb +58 -2
- data/lib/launchdarkly_api/models/flag_config_approval_requests_response.rb +3 -2
- data/lib/launchdarkly_api/models/flag_copy_config_environment.rb +5 -2
- data/lib/launchdarkly_api/models/flag_copy_config_post.rb +6 -2
- data/lib/launchdarkly_api/models/flag_followers_by_proj_env_get_rep.rb +237 -0
- data/lib/launchdarkly_api/models/flag_followers_get_rep.rb +237 -0
- data/lib/launchdarkly_api/models/flag_global_attributes_rep.rb +6 -15
- data/lib/launchdarkly_api/models/flag_input.rb +238 -0
- data/lib/launchdarkly_api/models/flag_link_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/flag_link_member.rb +3 -2
- data/lib/launchdarkly_api/models/flag_link_post.rb +9 -2
- data/lib/launchdarkly_api/models/flag_link_rep.rb +3 -2
- data/lib/launchdarkly_api/models/flag_listing_rep.rb +3 -2
- data/lib/launchdarkly_api/models/flag_rep.rb +244 -0
- data/lib/launchdarkly_api/models/flag_scheduled_changes_input.rb +4 -2
- data/lib/launchdarkly_api/models/flag_status_rep.rb +3 -2
- data/lib/launchdarkly_api/models/flag_summary.rb +20 -3
- data/lib/launchdarkly_api/models/flag_trigger_input.rb +5 -3
- data/lib/launchdarkly_api/models/follow_flag_member.rb +286 -0
- data/lib/launchdarkly_api/models/followers_per_flag.rb +230 -0
- data/lib/launchdarkly_api/models/forbidden_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/hunk_rep.rb +3 -2
- data/lib/launchdarkly_api/models/import.rb +3 -2
- data/lib/launchdarkly_api/models/initiator_rep.rb +3 -2
- data/lib/launchdarkly_api/models/instruction_user_request.rb +309 -0
- data/lib/launchdarkly_api/models/integration.rb +14 -3
- data/lib/launchdarkly_api/models/integration_delivery_configuration.rb +3 -2
- data/lib/launchdarkly_api/models/integration_delivery_configuration_collection.rb +3 -2
- data/lib/launchdarkly_api/models/integration_delivery_configuration_collection_links.rb +3 -2
- data/lib/launchdarkly_api/models/integration_delivery_configuration_links.rb +3 -2
- data/lib/launchdarkly_api/models/integration_delivery_configuration_post.rb +6 -5
- data/lib/launchdarkly_api/models/integration_delivery_configuration_response.rb +3 -2
- data/lib/launchdarkly_api/models/integration_metadata.rb +3 -2
- data/lib/launchdarkly_api/models/integration_status.rb +3 -2
- data/lib/launchdarkly_api/models/integration_status_rep.rb +3 -2
- data/lib/launchdarkly_api/models/integration_subscription_status_rep.rb +3 -2
- data/lib/launchdarkly_api/models/integrations.rb +3 -2
- data/lib/launchdarkly_api/models/invalid_request_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/ip_list.rb +3 -2
- data/lib/launchdarkly_api/models/iteration_expandable_properties.rb +232 -0
- data/lib/launchdarkly_api/models/iteration_input.rb +281 -0
- data/lib/launchdarkly_api/models/iteration_rep.rb +348 -0
- data/lib/launchdarkly_api/models/last_seen_metadata.rb +3 -2
- data/lib/launchdarkly_api/models/legacy_experiment_rep.rb +250 -0
- data/lib/launchdarkly_api/models/link.rb +3 -2
- data/lib/launchdarkly_api/models/member.rb +18 -11
- data/lib/launchdarkly_api/models/member_data_rep.rb +3 -2
- data/lib/launchdarkly_api/models/member_import_item.rb +3 -2
- data/lib/launchdarkly_api/models/member_permission_grant_summary_rep.rb +3 -2
- data/lib/launchdarkly_api/models/member_summary.rb +3 -2
- data/lib/launchdarkly_api/models/member_team_summary_rep.rb +3 -2
- data/lib/launchdarkly_api/models/member_teams_post_input.rb +3 -2
- data/lib/launchdarkly_api/models/members.rb +3 -2
- data/lib/launchdarkly_api/models/method_not_allowed_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/metric_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/metric_input.rb +238 -0
- data/lib/launchdarkly_api/models/metric_listing_rep.rb +3 -2
- data/lib/launchdarkly_api/models/metric_post.rb +15 -5
- data/lib/launchdarkly_api/models/metric_rep.rb +4 -3
- data/lib/launchdarkly_api/models/metric_seen.rb +3 -2
- data/lib/launchdarkly_api/models/metric_v2_rep.rb +268 -0
- data/lib/launchdarkly_api/models/modification.rb +3 -2
- data/lib/launchdarkly_api/models/multi_environment_dependent_flag.rb +3 -2
- data/lib/launchdarkly_api/models/multi_environment_dependent_flags.rb +3 -2
- data/lib/launchdarkly_api/models/new_member_form.rb +38 -3
- data/lib/launchdarkly_api/models/not_found_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/oauth_client_post.rb +240 -0
- data/lib/launchdarkly_api/models/parameter_default.rb +240 -0
- data/lib/launchdarkly_api/models/parameter_rep.rb +228 -0
- data/lib/launchdarkly_api/models/parent_resource_rep.rb +7 -5
- data/lib/launchdarkly_api/models/patch_failed_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/patch_flags_request.rb +237 -0
- data/lib/launchdarkly_api/models/patch_operation.rb +3 -2
- data/lib/launchdarkly_api/models/patch_segment_instruction.rb +53 -5
- data/lib/launchdarkly_api/models/patch_segment_request.rb +3 -2
- data/lib/launchdarkly_api/models/patch_users_request.rb +237 -0
- data/lib/launchdarkly_api/models/patch_with_comment.rb +4 -2
- data/lib/launchdarkly_api/models/permission_grant_input.rb +40 -2
- data/lib/launchdarkly_api/models/post_approval_request_apply_request.rb +4 -2
- data/lib/launchdarkly_api/models/post_approval_request_review_request.rb +39 -2
- data/lib/launchdarkly_api/models/post_flag_scheduled_changes_input.rb +4 -2
- data/lib/launchdarkly_api/models/prerequisite.rb +3 -2
- data/lib/launchdarkly_api/models/project.rb +5 -11
- data/lib/launchdarkly_api/models/project_listing_rep.rb +3 -2
- data/lib/launchdarkly_api/models/project_post.rb +4 -2
- data/lib/launchdarkly_api/models/project_rep.rb +323 -0
- data/lib/launchdarkly_api/models/project_summary.rb +3 -2
- data/lib/launchdarkly_api/models/projects.rb +16 -6
- data/lib/launchdarkly_api/models/pub_nub_detail_rep.rb +3 -2
- data/lib/launchdarkly_api/models/put_branch.rb +3 -2
- data/lib/launchdarkly_api/models/rate_limited_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/recent_trigger_body.rb +3 -2
- data/lib/launchdarkly_api/models/reference_rep.rb +3 -2
- data/lib/launchdarkly_api/models/relative_difference_rep.rb +237 -0
- data/lib/launchdarkly_api/models/relay_auto_config_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/relay_auto_config_post.rb +5 -3
- data/lib/launchdarkly_api/models/relay_auto_config_rep.rb +4 -3
- data/lib/launchdarkly_api/models/repository_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/repository_post.rb +7 -4
- data/lib/launchdarkly_api/models/repository_rep.rb +3 -2
- data/lib/launchdarkly_api/models/resolved_context.rb +3 -2
- data/lib/launchdarkly_api/models/resolved_image.rb +3 -2
- data/lib/launchdarkly_api/models/resolved_title.rb +3 -2
- data/lib/launchdarkly_api/models/resolved_ui_block_element.rb +3 -2
- data/lib/launchdarkly_api/models/resolved_ui_blocks.rb +3 -2
- data/lib/launchdarkly_api/models/resource_access.rb +7 -5
- data/lib/launchdarkly_api/models/resource_id_response.rb +3 -2
- data/lib/launchdarkly_api/models/review_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/review_response.rb +5 -4
- data/lib/launchdarkly_api/models/rollout.rb +3 -2
- data/lib/launchdarkly_api/models/rule.rb +3 -2
- data/lib/launchdarkly_api/models/rule_clause.rb +274 -0
- data/lib/launchdarkly_api/models/schedule_condition_input_rep.rb +5 -2
- data/lib/launchdarkly_api/models/schedule_condition_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/sdk_list_rep.rb +3 -2
- data/lib/launchdarkly_api/models/sdk_version_list_rep.rb +3 -2
- data/lib/launchdarkly_api/models/sdk_version_rep.rb +3 -2
- data/lib/launchdarkly_api/models/segment_body.rb +4 -2
- data/lib/launchdarkly_api/models/segment_metadata.rb +3 -2
- data/lib/launchdarkly_api/models/segment_user_list.rb +3 -2
- data/lib/launchdarkly_api/models/segment_user_state.rb +3 -2
- data/lib/launchdarkly_api/models/series_list_rep.rb +3 -2
- data/lib/launchdarkly_api/models/source_env.rb +3 -2
- data/lib/launchdarkly_api/models/source_flag.rb +5 -3
- data/lib/launchdarkly_api/models/stage_input_rep.rb +16 -3
- data/lib/launchdarkly_api/models/stage_output_rep.rb +3 -2
- data/lib/launchdarkly_api/models/statement.rb +3 -2
- data/lib/launchdarkly_api/models/statement_post.rb +5 -4
- data/lib/launchdarkly_api/models/statement_post_data.rb +5 -4
- data/lib/launchdarkly_api/models/statistic_collection_rep.rb +5 -2
- data/lib/launchdarkly_api/models/statistic_rep.rb +26 -3
- data/lib/launchdarkly_api/models/statistics_rep.rb +234 -0
- data/lib/launchdarkly_api/models/statistics_root.rb +3 -2
- data/lib/launchdarkly_api/models/status_conflict_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/subject_data_rep.rb +3 -2
- data/lib/launchdarkly_api/models/subscription_post.rb +6 -4
- data/lib/launchdarkly_api/models/tag_collection.rb +3 -2
- data/lib/launchdarkly_api/models/target.rb +3 -2
- data/lib/launchdarkly_api/models/target_resource_rep.rb +4 -3
- data/lib/launchdarkly_api/models/team.rb +43 -6
- data/lib/launchdarkly_api/models/team_custom_role.rb +3 -2
- data/lib/launchdarkly_api/models/team_custom_roles.rb +3 -2
- data/lib/launchdarkly_api/models/team_imports_rep.rb +3 -2
- data/lib/launchdarkly_api/models/team_maintainers.rb +3 -2
- data/lib/launchdarkly_api/models/team_members.rb +219 -0
- data/lib/launchdarkly_api/models/team_patch_input.rb +11 -4
- data/lib/launchdarkly_api/models/team_post_input.rb +5 -4
- data/lib/launchdarkly_api/models/team_projects.rb +3 -2
- data/lib/launchdarkly_api/models/team_rep_expandable_properties.rb +246 -0
- data/lib/launchdarkly_api/models/teams.rb +3 -2
- data/lib/launchdarkly_api/models/timestamp_rep.rb +3 -2
- data/lib/launchdarkly_api/models/title_rep.rb +3 -2
- data/lib/launchdarkly_api/models/token.rb +4 -3
- data/lib/launchdarkly_api/models/token_data_rep.rb +3 -2
- data/lib/launchdarkly_api/models/tokens.rb +3 -2
- data/lib/launchdarkly_api/models/treatment_input.rb +268 -0
- data/lib/launchdarkly_api/models/treatment_parameter_input.rb +238 -0
- data/lib/launchdarkly_api/models/treatment_rep.rb +267 -0
- data/lib/launchdarkly_api/models/treatment_result_rep.rb +275 -0
- data/lib/launchdarkly_api/models/trigger_post.rb +6 -4
- data/lib/launchdarkly_api/models/trigger_workflow_collection_rep.rb +3 -2
- data/lib/launchdarkly_api/models/trigger_workflow_rep.rb +3 -2
- data/lib/launchdarkly_api/models/unauthorized_error_rep.rb +5 -2
- data/lib/launchdarkly_api/models/url_post.rb +3 -2
- data/lib/launchdarkly_api/models/user.rb +3 -2
- data/lib/launchdarkly_api/models/user_attribute_names_rep.rb +3 -2
- data/lib/launchdarkly_api/models/user_flag_setting.rb +20 -7
- data/lib/launchdarkly_api/models/user_flag_settings.rb +4 -2
- data/lib/launchdarkly_api/models/user_record.rb +3 -2
- data/lib/launchdarkly_api/models/user_record_rep.rb +3 -2
- data/lib/launchdarkly_api/models/user_segment.rb +14 -4
- data/lib/launchdarkly_api/models/user_segment_rule.rb +3 -2
- data/lib/launchdarkly_api/models/user_segments.rb +5 -2
- data/lib/launchdarkly_api/models/users.rb +3 -2
- data/lib/launchdarkly_api/models/users_rep.rb +251 -0
- data/lib/launchdarkly_api/models/value_put.rb +5 -3
- data/lib/launchdarkly_api/models/variation.rb +4 -2
- data/lib/launchdarkly_api/models/variation_or_rollout_rep.rb +3 -2
- data/lib/launchdarkly_api/models/variation_summary.rb +3 -2
- data/lib/launchdarkly_api/models/versions_rep.rb +3 -2
- data/lib/launchdarkly_api/models/webhook.rb +12 -3
- data/lib/launchdarkly_api/models/webhook_post.rb +3 -2
- data/lib/launchdarkly_api/models/webhooks.rb +5 -2
- data/lib/launchdarkly_api/models/weighted_variation.rb +3 -2
- data/lib/launchdarkly_api/models/workflow_template_metadata.rb +221 -0
- data/lib/launchdarkly_api/models/workflow_template_parameter.rb +248 -0
- data/lib/launchdarkly_api/version.rb +3 -3
- data/lib/launchdarkly_api.rb +48 -6
- data/spec/api/access_tokens_api_spec.rb +2 -2
- data/spec/api/account_members_api_spec.rb +8 -8
- data/spec/api/account_usage_beta_api_spec.rb +2 -2
- data/spec/api/approvals_api_spec.rb +9 -9
- data/spec/api/audit_log_api_spec.rb +3 -3
- data/spec/api/code_references_api_spec.rb +12 -12
- data/spec/api/custom_roles_api_spec.rb +2 -2
- data/spec/api/data_export_destinations_api_spec.rb +6 -6
- data/spec/api/environments_api_spec.rb +19 -3
- data/spec/api/experiments_beta_api_spec.rb +96 -6
- data/spec/api/feature_flags_api_spec.rb +9 -9
- data/spec/api/feature_flags_beta_api_spec.rb +4 -4
- data/spec/api/flag_links_beta_api_spec.rb +3 -3
- data/spec/api/flag_triggers_api_spec.rb +4 -4
- data/spec/api/follow_flags_api_spec.rb +92 -0
- data/spec/api/integration_audit_log_subscriptions_api_spec.rb +3 -3
- data/spec/api/integration_delivery_configurations_beta_api_spec.rb +3 -3
- data/spec/api/metrics_api_spec.rb +3 -3
- data/spec/api/o_auth2_clients_beta_api_spec.rb +95 -0
- data/spec/api/other_api_spec.rb +5 -5
- data/spec/api/projects_api_spec.rb +13 -8
- data/spec/api/relay_proxy_configurations_api_spec.rb +6 -6
- data/spec/api/scheduled_changes_api_spec.rb +8 -8
- data/spec/api/segments_api_spec.rb +10 -10
- data/spec/api/segments_beta_api_spec.rb +5 -3
- data/spec/api/tags_api_spec.rb +2 -2
- data/spec/api/teams_api_spec.rb +143 -0
- data/spec/api/user_settings_api_spec.rb +7 -7
- data/spec/api/users_api_spec.rb +5 -5
- data/spec/api/users_beta_api_spec.rb +2 -2
- data/spec/api/webhooks_api_spec.rb +3 -3
- data/spec/api/workflows_beta_api_spec.rb +6 -6
- data/spec/api_client_spec.rb +2 -2
- data/spec/configuration_spec.rb +2 -2
- data/spec/models/access_allowed_reason_spec.rb +2 -2
- data/spec/models/access_allowed_rep_spec.rb +2 -2
- data/spec/models/access_denied_reason_spec.rb +2 -2
- data/spec/models/access_denied_spec.rb +2 -2
- data/spec/models/access_spec.rb +2 -2
- data/spec/models/access_token_post_spec.rb +2 -2
- data/spec/models/action_input_rep_spec.rb +2 -2
- data/spec/models/action_output_rep_spec.rb +2 -2
- data/spec/models/approval_condition_input_rep_spec.rb +8 -2
- data/spec/models/approval_condition_output_rep_spec.rb +2 -2
- data/spec/models/approval_settings_spec.rb +2 -2
- data/spec/models/audit_log_entry_listing_rep_collection_spec.rb +2 -2
- data/spec/models/audit_log_entry_listing_rep_spec.rb +2 -2
- data/spec/models/audit_log_entry_rep_spec.rb +2 -2
- data/spec/models/authorized_app_data_rep_spec.rb +2 -2
- data/spec/models/big_segment_target_spec.rb +2 -2
- data/spec/models/branch_collection_rep_spec.rb +2 -2
- data/spec/models/branch_rep_spec.rb +2 -2
- data/spec/models/clause_spec.rb +2 -2
- data/spec/models/client_collection_spec.rb +40 -0
- data/spec/models/client_side_availability_post_spec.rb +2 -2
- data/spec/models/client_side_availability_spec.rb +2 -2
- data/spec/models/client_spec.rb +76 -0
- data/spec/models/condition_base_output_rep_spec.rb +2 -2
- data/spec/models/condition_input_rep_spec.rb +8 -2
- data/spec/models/condition_output_rep_spec.rb +2 -2
- data/spec/models/confidence_interval_rep_spec.rb +2 -2
- data/spec/models/conflict_output_rep_spec.rb +2 -2
- data/spec/models/conflict_spec.rb +2 -2
- data/spec/models/copied_from_env_spec.rb +2 -2
- data/spec/models/create_copy_flag_config_approval_request_request_spec.rb +16 -2
- data/spec/models/create_flag_config_approval_request_request_spec.rb +8 -2
- data/spec/models/credible_interval_rep_spec.rb +40 -0
- data/spec/models/custom_property_spec.rb +2 -2
- data/spec/models/custom_role_post_data_spec.rb +2 -2
- data/spec/models/custom_role_post_spec.rb +2 -2
- data/spec/models/custom_role_spec.rb +2 -2
- data/spec/models/custom_roles_spec.rb +2 -2
- data/spec/models/custom_workflow_input_rep_spec.rb +8 -2
- data/spec/models/custom_workflow_meta_spec.rb +2 -2
- data/spec/models/custom_workflow_output_rep_spec.rb +2 -2
- data/spec/models/custom_workflow_stage_meta_spec.rb +2 -2
- data/spec/models/custom_workflows_listing_output_rep_spec.rb +2 -2
- data/spec/models/default_client_side_availability_post_spec.rb +2 -2
- data/spec/models/defaults_spec.rb +2 -2
- data/spec/models/dependent_flag_environment_spec.rb +2 -2
- data/spec/models/dependent_flag_spec.rb +2 -2
- data/spec/models/dependent_flags_by_environment_spec.rb +2 -2
- data/spec/models/destination_post_spec.rb +2 -2
- data/spec/models/destination_spec.rb +2 -2
- data/spec/models/destinations_spec.rb +2 -2
- data/spec/models/environment_post_spec.rb +2 -2
- data/spec/models/environment_spec.rb +2 -2
- data/spec/models/environments_spec.rb +46 -0
- data/spec/models/evaluation_reason_spec.rb +64 -0
- data/spec/models/execution_output_rep_spec.rb +2 -2
- data/spec/models/experiment_allocation_rep_spec.rb +2 -2
- data/spec/models/experiment_bayesian_results_rep_spec.rb +46 -0
- data/spec/models/experiment_collection_rep_spec.rb +46 -0
- data/spec/models/experiment_enabled_period_rep_spec.rb +2 -2
- data/spec/models/experiment_environment_setting_rep_spec.rb +2 -2
- data/spec/models/experiment_expandable_properties_spec.rb +40 -0
- data/spec/models/experiment_info_rep_spec.rb +2 -2
- data/spec/models/experiment_metadata_rep_spec.rb +2 -2
- data/spec/models/experiment_patch_input_spec.rb +40 -0
- data/spec/models/experiment_post_spec.rb +58 -0
- data/spec/models/experiment_results_spec.rb +70 -0
- data/spec/models/experiment_spec.rb +88 -0
- data/spec/models/experiment_stats_rep_spec.rb +2 -2
- data/spec/models/experiment_time_series_slice_spec.rb +2 -2
- data/spec/models/experiment_time_series_variation_slice_spec.rb +2 -2
- data/spec/models/experiment_totals_rep_spec.rb +2 -2
- data/spec/models/expiring_user_target_error_spec.rb +2 -2
- data/spec/models/expiring_user_target_get_response_spec.rb +2 -2
- data/spec/models/expiring_user_target_item_spec.rb +2 -2
- data/spec/models/expiring_user_target_patch_response_spec.rb +2 -2
- data/spec/models/export_spec.rb +2 -2
- data/spec/models/extinction_collection_rep_spec.rb +2 -2
- data/spec/models/extinction_spec.rb +2 -2
- data/spec/models/feature_flag_body_spec.rb +2 -8
- data/spec/models/feature_flag_config_spec.rb +2 -2
- data/spec/models/feature_flag_scheduled_change_spec.rb +2 -2
- data/spec/models/feature_flag_scheduled_changes_spec.rb +2 -2
- data/spec/models/feature_flag_spec.rb +2 -8
- data/spec/models/feature_flag_status_across_environments_spec.rb +2 -2
- data/spec/models/feature_flag_status_spec.rb +2 -2
- data/spec/models/feature_flag_statuses_spec.rb +2 -2
- data/spec/models/feature_flags_spec.rb +2 -2
- data/spec/models/file_rep_spec.rb +2 -2
- data/spec/models/flag_config_approval_request_response_spec.rb +10 -2
- data/spec/models/flag_config_approval_requests_response_spec.rb +2 -2
- data/spec/models/flag_copy_config_environment_spec.rb +2 -2
- data/spec/models/flag_copy_config_post_spec.rb +2 -2
- data/spec/models/flag_followers_by_proj_env_get_rep_spec.rb +40 -0
- data/spec/models/flag_followers_get_rep_spec.rb +40 -0
- data/spec/models/flag_global_attributes_rep_spec.rb +2 -8
- data/spec/models/flag_input_spec.rb +40 -0
- data/spec/models/flag_link_collection_rep_spec.rb +2 -2
- data/spec/models/flag_link_member_spec.rb +2 -2
- data/spec/models/flag_link_post_spec.rb +2 -2
- data/spec/models/flag_link_rep_spec.rb +2 -2
- data/spec/models/flag_listing_rep_spec.rb +2 -2
- data/spec/models/flag_rep_spec.rb +46 -0
- data/spec/models/flag_scheduled_changes_input_spec.rb +2 -2
- data/spec/models/flag_status_rep_spec.rb +2 -2
- data/spec/models/flag_summary_spec.rb +8 -2
- data/spec/models/flag_trigger_input_spec.rb +2 -2
- data/spec/models/follow_flag_member_spec.rb +64 -0
- data/spec/models/followers_per_flag_spec.rb +40 -0
- data/spec/models/forbidden_error_rep_spec.rb +2 -2
- data/spec/models/hunk_rep_spec.rb +2 -2
- data/spec/models/import_spec.rb +2 -2
- data/spec/models/initiator_rep_spec.rb +2 -2
- data/spec/models/instruction_user_request_spec.rb +62 -0
- data/spec/models/integration_delivery_configuration_collection_links_spec.rb +2 -2
- data/spec/models/integration_delivery_configuration_collection_spec.rb +2 -2
- data/spec/models/integration_delivery_configuration_links_spec.rb +2 -2
- data/spec/models/integration_delivery_configuration_post_spec.rb +2 -2
- data/spec/models/integration_delivery_configuration_response_spec.rb +2 -2
- data/spec/models/integration_delivery_configuration_spec.rb +2 -2
- data/spec/models/integration_metadata_spec.rb +2 -2
- data/spec/models/integration_spec.rb +2 -2
- data/spec/models/integration_status_rep_spec.rb +2 -2
- data/spec/models/integration_status_spec.rb +2 -2
- data/spec/models/integration_subscription_status_rep_spec.rb +2 -2
- data/spec/models/integrations_spec.rb +2 -2
- data/spec/models/invalid_request_error_rep_spec.rb +2 -2
- data/spec/models/ip_list_spec.rb +2 -2
- data/spec/models/iteration_expandable_properties_spec.rb +40 -0
- data/spec/models/iteration_input_spec.rb +58 -0
- data/spec/models/iteration_rep_spec.rb +106 -0
- data/spec/models/last_seen_metadata_spec.rb +2 -2
- data/spec/models/legacy_experiment_rep_spec.rb +52 -0
- data/spec/models/link_spec.rb +2 -2
- data/spec/models/member_data_rep_spec.rb +2 -2
- data/spec/models/member_import_item_spec.rb +2 -2
- data/spec/models/member_permission_grant_summary_rep_spec.rb +2 -2
- data/spec/models/member_spec.rb +8 -2
- data/spec/models/member_summary_spec.rb +2 -2
- data/spec/models/member_team_summary_rep_spec.rb +2 -2
- data/spec/models/member_teams_post_input_spec.rb +2 -2
- data/spec/models/members_spec.rb +2 -2
- data/spec/models/method_not_allowed_error_rep_spec.rb +2 -2
- data/spec/models/metric_collection_rep_spec.rb +2 -2
- data/spec/models/metric_input_spec.rb +40 -0
- data/spec/models/metric_listing_rep_spec.rb +2 -2
- data/spec/models/metric_post_spec.rb +2 -2
- data/spec/models/metric_rep_spec.rb +2 -2
- data/spec/models/metric_seen_spec.rb +2 -2
- data/spec/models/metric_v2_rep_spec.rb +52 -0
- data/spec/models/modification_spec.rb +2 -2
- data/spec/models/multi_environment_dependent_flag_spec.rb +2 -2
- data/spec/models/multi_environment_dependent_flags_spec.rb +2 -2
- data/spec/models/new_member_form_spec.rb +6 -2
- data/spec/models/not_found_error_rep_spec.rb +2 -2
- data/spec/models/oauth_client_post_spec.rb +46 -0
- data/spec/models/parameter_default_spec.rb +46 -0
- data/spec/models/parameter_rep_spec.rb +40 -0
- data/spec/models/parent_resource_rep_spec.rb +2 -2
- data/spec/models/patch_failed_error_rep_spec.rb +2 -2
- data/spec/models/patch_flags_request_spec.rb +40 -0
- data/spec/models/patch_operation_spec.rb +2 -2
- data/spec/models/patch_segment_instruction_spec.rb +10 -2
- data/spec/models/patch_segment_request_spec.rb +2 -2
- data/spec/models/patch_users_request_spec.rb +40 -0
- data/spec/models/patch_with_comment_spec.rb +2 -2
- data/spec/models/permission_grant_input_spec.rb +6 -2
- data/spec/models/post_approval_request_apply_request_spec.rb +2 -2
- data/spec/models/post_approval_request_review_request_spec.rb +6 -2
- data/spec/models/post_flag_scheduled_changes_input_spec.rb +2 -2
- data/spec/models/prerequisite_spec.rb +2 -2
- data/spec/models/project_listing_rep_spec.rb +2 -2
- data/spec/models/project_post_spec.rb +2 -2
- data/spec/models/project_rep_spec.rb +76 -0
- data/spec/models/project_spec.rb +2 -2
- data/spec/models/project_summary_spec.rb +2 -2
- data/spec/models/projects_spec.rb +8 -2
- data/spec/models/pub_nub_detail_rep_spec.rb +2 -2
- data/spec/models/put_branch_spec.rb +2 -2
- data/spec/models/rate_limited_error_rep_spec.rb +2 -2
- data/spec/models/recent_trigger_body_spec.rb +2 -2
- data/spec/models/reference_rep_spec.rb +2 -2
- data/spec/models/relative_difference_rep_spec.rb +46 -0
- data/spec/models/relay_auto_config_collection_rep_spec.rb +2 -2
- data/spec/models/relay_auto_config_post_spec.rb +2 -2
- data/spec/models/relay_auto_config_rep_spec.rb +2 -2
- data/spec/models/repository_collection_rep_spec.rb +2 -2
- data/spec/models/repository_post_spec.rb +2 -2
- data/spec/models/repository_rep_spec.rb +2 -2
- data/spec/models/resolved_context_spec.rb +2 -2
- data/spec/models/resolved_image_spec.rb +2 -2
- data/spec/models/resolved_title_spec.rb +2 -2
- data/spec/models/resolved_ui_block_element_spec.rb +2 -2
- data/spec/models/resolved_ui_blocks_spec.rb +2 -2
- data/spec/models/resource_access_spec.rb +2 -2
- data/spec/models/resource_id_response_spec.rb +2 -2
- data/spec/models/review_output_rep_spec.rb +2 -2
- data/spec/models/review_response_spec.rb +2 -2
- data/spec/models/rollout_spec.rb +2 -2
- data/spec/models/rule_clause_spec.rb +50 -0
- data/spec/models/rule_spec.rb +2 -2
- data/spec/models/schedule_condition_input_rep_spec.rb +2 -2
- data/spec/models/schedule_condition_output_rep_spec.rb +2 -2
- data/spec/models/sdk_list_rep_spec.rb +2 -2
- data/spec/models/sdk_version_list_rep_spec.rb +2 -2
- data/spec/models/sdk_version_rep_spec.rb +2 -2
- data/spec/models/segment_body_spec.rb +2 -2
- data/spec/models/segment_metadata_spec.rb +2 -2
- data/spec/models/segment_user_list_spec.rb +2 -2
- data/spec/models/segment_user_state_spec.rb +2 -2
- data/spec/models/series_list_rep_spec.rb +2 -2
- data/spec/models/source_env_spec.rb +2 -2
- data/spec/models/source_flag_spec.rb +2 -2
- data/spec/models/stage_input_rep_spec.rb +8 -2
- data/spec/models/stage_output_rep_spec.rb +2 -2
- data/spec/models/statement_post_data_spec.rb +2 -2
- data/spec/models/statement_post_spec.rb +2 -2
- data/spec/models/statement_spec.rb +2 -2
- data/spec/models/statistic_collection_rep_spec.rb +2 -2
- data/spec/models/statistic_rep_spec.rb +8 -2
- data/spec/models/statistics_rep_spec.rb +40 -0
- data/spec/models/statistics_root_spec.rb +2 -2
- data/spec/models/status_conflict_error_rep_spec.rb +2 -2
- data/spec/models/subject_data_rep_spec.rb +2 -2
- data/spec/models/subscription_post_spec.rb +2 -2
- data/spec/models/tag_collection_spec.rb +2 -2
- data/spec/models/target_resource_rep_spec.rb +2 -2
- data/spec/models/target_spec.rb +2 -2
- data/spec/models/team_custom_role_spec.rb +2 -2
- data/spec/models/team_custom_roles_spec.rb +2 -2
- data/spec/models/team_imports_rep_spec.rb +2 -2
- data/spec/models/team_maintainers_spec.rb +2 -2
- data/spec/models/team_members_spec.rb +34 -0
- data/spec/models/team_patch_input_spec.rb +2 -2
- data/spec/models/team_post_input_spec.rb +2 -2
- data/spec/models/team_projects_spec.rb +2 -2
- data/spec/models/team_rep_expandable_properties_spec.rb +52 -0
- data/spec/models/team_spec.rb +26 -2
- data/spec/models/teams_spec.rb +2 -2
- data/spec/models/timestamp_rep_spec.rb +2 -2
- data/spec/models/title_rep_spec.rb +2 -2
- data/spec/models/token_data_rep_spec.rb +2 -2
- data/spec/models/token_spec.rb +2 -2
- data/spec/models/tokens_spec.rb +2 -2
- data/spec/models/treatment_input_spec.rb +52 -0
- data/spec/models/treatment_parameter_input_spec.rb +40 -0
- data/spec/models/treatment_rep_spec.rb +58 -0
- data/spec/models/treatment_result_rep_spec.rb +70 -0
- data/spec/models/trigger_post_spec.rb +2 -2
- data/spec/models/trigger_workflow_collection_rep_spec.rb +2 -2
- data/spec/models/trigger_workflow_rep_spec.rb +2 -2
- data/spec/models/unauthorized_error_rep_spec.rb +2 -2
- data/spec/models/url_post_spec.rb +2 -2
- data/spec/models/user_attribute_names_rep_spec.rb +2 -2
- data/spec/models/user_flag_setting_spec.rb +8 -2
- data/spec/models/user_flag_settings_spec.rb +2 -2
- data/spec/models/user_record_rep_spec.rb +2 -2
- data/spec/models/user_record_spec.rb +2 -2
- data/spec/models/user_segment_rule_spec.rb +2 -2
- data/spec/models/user_segment_spec.rb +2 -2
- data/spec/models/user_segments_spec.rb +2 -2
- data/spec/models/user_spec.rb +2 -2
- data/spec/models/users_rep_spec.rb +46 -0
- data/spec/models/users_spec.rb +2 -2
- data/spec/models/value_put_spec.rb +2 -2
- data/spec/models/variation_or_rollout_rep_spec.rb +2 -2
- data/spec/models/variation_spec.rb +2 -2
- data/spec/models/variation_summary_spec.rb +2 -2
- data/spec/models/versions_rep_spec.rb +2 -2
- data/spec/models/webhook_post_spec.rb +2 -2
- data/spec/models/webhook_spec.rb +2 -2
- data/spec/models/webhooks_spec.rb +2 -2
- data/spec/models/weighted_variation_spec.rb +2 -2
- data/spec/models/workflow_template_metadata_spec.rb +34 -0
- data/spec/models/workflow_template_parameter_spec.rb +52 -0
- data/spec/spec_helper.rb +2 -2
- metadata +320 -134
- data/docs/StatementRep.md +0 -26
- data/docs/TeamsBetaApi.md +0 -606
- data/lib/launchdarkly_api/api/teams_beta_api.rb +0 -565
- data/lib/launchdarkly_api/models/experiment_rep.rb +0 -249
- data/lib/launchdarkly_api/models/experiment_results_rep.rb +0 -280
- data/lib/launchdarkly_api/models/statement_rep.rb +0 -271
- data/spec/api/teams_beta_api_spec.rb +0 -139
- data/spec/models/experiment_rep_spec.rb +0 -52
- data/spec/models/experiment_results_rep_spec.rb +0 -70
- data/spec/models/statement_rep_spec.rb +0 -58
@@ -1,12 +1,12 @@
|
|
1
1
|
=begin
|
2
2
|
#LaunchDarkly REST API
|
3
3
|
|
4
|
-
## Overview ## Authentication All REST API resources are authenticated with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens), or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens on your [Account settings](https://app.launchdarkly.com/settings/tokens) page. LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are used by our server-side SDKs, mobile SDKs, and client-side SDKs, respectively. **These keys cannot be used to access our REST API**. These keys are environment-specific, and can only perform read-only operations (fetching feature flag settings). | Auth mechanism | Allowed resources | Use cases | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | [Personal access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens) | Can be customized on a per-token basis | Building scripts, custom integrations, data export | | SDK keys | Can only access read-only SDK-specific resources and the firehose, restricted to a single environment | Server-side SDKs, Firehose API | | Mobile keys | Can only access read-only mobile SDK-specific resources, restricted to a single environment | Mobile SDKs | | Client-side ID | Single environment, only flags marked available to client-side | Client-side JavaScript | > #### Keep your access tokens and SDK keys private > > Access tokens should _never_ be exposed in untrusted contexts. Never put an access token in client-side JavaScript, or embed it in a mobile application. LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally expose an access token or SDK key, you can reset it from your [Account Settings](https://app.launchdarkly.com/settings#/tokens) page. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Via request header The preferred way to authenticate with the API is by adding an `Authorization` header containing your access token to your requests. The value of the `Authorization` header must be your access token. Manage personal access tokens from the [Account Settings](https://app.launchdarkly.com/settings/tokens) page. ### Via session cookie For testing purposes, you can make API calls directly from your web browser. If you're logged in to the application, the API will use your existing session to authenticate calls. If you have a [role](https://docs.launchdarkly.com/home/team/built-in-roles) other than Admin, or have a [custom role](https://docs.launchdarkly.com/home/team/custom-roles) defined, you may not have permission to perform some API calls. You will receive a `401` response code in that case. > ### Modifying the Origin header causes an error > > LaunchDarkly validates that the Origin header for any API request authenticated by a session cookie matches the expected Origin header. The expected Origin header is `https://app.launchdarkly.com`. > > If the Origin header does not match what's expected, LaunchDarkly returns an error. This error can prevent the LaunchDarkly app from working correctly. > > Any browser extension that intentionally changes the Origin header can cause this problem. For example, the `Allow-Control-Allow-Origin: *` Chrome extension changes the Origin header to `http://evil.com` and causes the app to fail. > > To prevent this error, do not modify your Origin header. > > LaunchDarkly does not require origin matching when authenticating with an access token, so this issue does not affect normal API usage. ## Representations All resources expect and return JSON response bodies. Error responses will also send a JSON body. Read [Errors](#section/Errors) for a more detailed description of the error format used by the API. In practice this means that you always get a response with a `Content-Type` header set to `application/json`. In addition, request bodies for `PUT`, `POST`, `REPORT` and `PATCH` requests must be encoded as JSON with a `Content-Type` header set to `application/json`. ### Summary and detailed representations When you fetch a list of resources, the response includes only the most important attributes of each resource. This is a _summary representation_ of the resource. When you fetch an individual resource (for example, a single feature flag), you receive a _detailed representation_ containing all of the attributes of the resource. The best way to find a detailed representation is to follow links. Every summary representation includes a link to its detailed representation. ### Links and addressability The best way to navigate the API is by following links. These are attributes in representations that link to other resources. The API always uses the same format for links: - Links to other resources within the API are encapsulated in a `_links` object. - If the resource has a corresponding link to HTML content on the site, it is stored in a special `_site` link. Each link has two attributes: an href (the URL) and a type (the content type). For example, a feature resource might return the following: ```json { \"_links\": { \"parent\": { \"href\": \"/api/features\", \"type\": \"application/json\" }, \"self\": { \"href\": \"/api/features/sort.order\", \"type\": \"application/json\" } }, \"_site\": { \"href\": \"/features/sort.order\", \"type\": \"text/html\" } } ``` From this, you can navigate to the parent collection of features by following the `parent` link, or navigate to the site page for the feature by following the `_site` link. Collections are always represented as a JSON object with an `items` attribute containing an array of representations. Like all other representations, collections have `_links` defined at the top level. Paginated collections include `first`, `last`, `next`, and `prev` links containing a URL with the respective set of elements in the collection. ## Updates Resources that accept partial updates use the `PATCH` verb, and support the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) format. Some resources also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format. In addition, some resources support optional comments that can be submitted with updates. Comments appear in outgoing webhooks, the audit log, and other integrations. ### Updates via JSON Patch [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) is a way to specify the modifications to perform on a resource. For example, in this feature flag representation: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"description\": \"This is the description\", ... } ``` You can change the feature flag's description with the following patch document: ```json [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"This is the new description\" }] ``` JSON Patch documents are always arrays. You can specify multiple modifications to perform in a single request. You can also test that certain preconditions are met before applying the patch: ```json [ { \"op\": \"test\", \"path\": \"/version\", \"value\": 10 }, { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" } ] ``` The above patch request tests whether the feature flag's `version` is `10`, and if so, changes the feature flag's description. Attributes that aren't editable, like a resource's `_links`, have names that start with an underscore. ### Updates via JSON Merge Patch The API also supports the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format, as well as the [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) resource. JSON Merge Patch is less expressive than JSON Patch but in many cases, it is simpler to construct a merge patch document. For example, you can change a feature flag's description with the following merge patch document: ```json { \"description\": \"New flag description\" } ``` ### Updates with comments You can submit optional comments with `PATCH` changes. The [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) resource supports comments. To submit a comment along with a JSON Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"patch\": [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }] } ``` To submit a comment along with a JSON Merge Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"merge\": { \"description\": \"New flag description\" } } ``` ### Updates via semantic patches The API also supports the Semantic patch format. A semantic `PATCH` is a way to specify the modifications to perform on a resource as a set of executable instructions. JSON Patch uses paths and a limited set of operations to describe how to transform the current state of the resource into a new state. Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, semantic patch instructions can also be defined independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date. For example, in this feature flag configuration in environment Production: ```json { \"name\": \"Alternate sort order\", \"kind\": \"boolean\", \"key\": \"sort.order\", ... \"environments\": { \"production\": { \"on\": true, \"archived\": false, \"salt\": \"c29ydC5vcmRlcg==\", \"sel\": \"8de1085cb7354b0ab41c0e778376dfd3\", \"lastModified\": 1469131558260, \"version\": 81, \"targets\": [ { \"values\": [ \"Gerhard.Little@yahoo.com\" ], \"variation\": 0 }, { \"values\": [ \"1461797806429-33-861961230\", \"438580d8-02ee-418d-9eec-0085cab2bdf0\" ], \"variation\": 1 } ], \"rules\": [], \"fallthrough\": { \"variation\": 0 }, \"offVariation\": 1, \"prerequisites\": [], \"_site\": { \"href\": \"/default/production/features/sort.order\", \"type\": \"text/html\" } } } } ``` You can add a date you want a user to be removed from the feature flag's user targets. For example, “remove user 1461797806429-33-861961230 from the user target for variation 0 on the Alternate sort order flag in the production environment on Wed Jul 08 2020 at 15:27:41 pm”. This is done using the following: ```json { \"comment\": \"update expiring user targets\", \"instructions\": [ { \"kind\": \"removeExpireUserTargetDate\", \"userKey\": \"userKey\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\" }, { \"kind\": \"updateExpireUserTargetDate\", \"userKey\": \"userKey2\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\", \"value\": 1587582000000 }, { \"kind\": \"addExpireUserTargetDate\", \"userKey\": \"userKey3\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\", \"value\": 1594247266386 } ] } ``` Here is another example. In this feature flag configuration: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"environments\": { \"test\": { \"on\": true } } } ``` You can change the feature flag's description with the following patch document as a set of executable instructions. For example, “add user X to targets for variation Y and remove user A from targets for variation B for test flag”: ```json { \"comment\": \"\", \"instructions\": [ { \"kind\": \"removeUserTargets\", \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"], \"variationId\": \"852cb784-54ff-46b9-8c35-5498d2e4f270\" }, { \"kind\": \"addUserTargets\", \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"], \"variationId\": \"1bb18465-33b6-49aa-a3bd-eeb6650b33ad\" } ] } ``` > ### Supported semantic patch API endpoints > > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) > - [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets) > - [Update expiring user target for flags](/tag/User-settings#operation/patchExpiringFlagsForUser) > - [Update expiring user targets on segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment) ## Errors The API always returns errors in a common format. Here's an example: ```json { \"code\": \"invalid_request\", \"message\": \"A feature with that key already exists\", \"id\": \"30ce6058-87da-11e4-b116-123b93f75cba\" } ``` The general class of error is indicated by the `code`. The `message` is a human-readable explanation of what went wrong. The `id` is a unique identifier. Use it when you're working with LaunchDarkly support to debug a problem with a specific API call. ### HTTP Status - Error Response Codes | Code | Definition | Desc. | Possible Solution | | ---- | ----------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | 400 | Bad Request | A request that fails may return this HTTP response code. | Ensure JSON syntax in request body is correct. | | 401 | Unauthorized | User doesn't have permission to an API call. | Ensure your SDK key is good. | | 403 | Forbidden | User does not have permission for operation. | Ensure that the user or access token has proper permissions set. | | 409 | Conflict | The API request could not be completed because it conflicted with a concurrent API request. | Retry your request. | | 429 | Too many requests | See [Rate limiting](/#section/Rate-limiting). | Wait and try again later. | ## CORS The LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. If an `Origin` header is given in a request, it will be echoed as an explicitly allowed origin. Otherwise, a wildcard is returned: `Access-Control-Allow-Origin: *`. For more information on CORS, see the [CORS W3C Recommendation](http://www.w3.org/TR/cors). Example CORS headers might look like: ```http Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization Access-Control-Allow-Methods: OPTIONS, GET, DELETE, PATCH Access-Control-Allow-Origin: * Access-Control-Max-Age: 300 ``` You can make authenticated CORS calls just as you would make same-origin calls, using either [token or session-based authentication](#section/Authentication). If you’re using session auth, you should set the `withCredentials` property for your `xhr` request to `true`. You should never expose your access tokens to untrusted users. ## Rate limiting We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs will return a `429` status code. Calls to our APIs will include headers indicating the current rate limit status. The specific headers returned depend on the API route being called. The limits differ based on the route, authentication mechanism, and other factors. Routes that are not rate limited may not contain any of the headers described below. > ### Rate limiting and SDKs > > LaunchDarkly SDKs are never rate limited and do not use the API endpoints defined here. LaunchDarkly uses a different set of approaches, including streaming/server-sent events and a global CDN, to ensure availability to the routes used by LaunchDarkly SDKs. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Global rate limits Authenticated requests are subject to a global limit. This is the maximum number of calls that can be made to the API per ten seconds. All personal access tokens on the account share this limit, so exceeding the limit with one access token will impact other tokens. Calls that are subject to global rate limits will return the headers below: | Header name | Description | | ------------------------------ | -------------------------------------------------------------------------------- | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | We do not publicly document the specific number of calls that can be made globally. This limit may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limit. ### Route-level rate limits Some authenticated routes have custom rate limits. These also reset every ten seconds. Any access tokens hitting the same route share this limit, so exceeding the limit with one access token may impact other tokens. Calls that are subject to route-level rate limits will return the headers below: | Header name | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------- | | `X-Ratelimit-Route-Remaining` | The maximum number of requests to the current route the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | A _route_ represents a specific URL pattern and verb. For example, the [Delete environment](/tag/Environments#operation/deleteEnvironment) endpoint is considered a single route, and each call to delete an environment counts against your route-level rate limit for that route. We do not publicly document the specific number of calls that can be made to each endpoint per ten seconds. These limits may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limits. ### IP-based rate limiting We also employ IP-based rate limiting on some API routes. If you hit an IP-based rate limit, your API response will include a `Retry-After` header indicating how long to wait before re-trying the call. Clients must wait at least `Retry-After` seconds before making additional calls to our API, and should employ jitter and backoff strategies to avoid triggering rate limits again. ## OpenAPI (Swagger) We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json) for our API. You can use this specification to generate client libraries to interact with our REST API in your language of choice. This specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to ease use in navigating the APIs in the tooling. ## Client libraries We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories). ## Method Overriding Some firewalls and HTTP clients restrict the use of verbs other than `GET` and `POST`. In those environments, our API endpoints that use `PUT`, `PATCH`, and `DELETE` verbs will be inaccessible. To avoid this issue, our API supports the `X-HTTP-Method-Override` header, allowing clients to \"tunnel\" `PUT`, `PATCH`, and `DELETE` requests via a `POST` request. For example, if you wish to call one of our `PATCH` resources via a `POST` request, you can include `X-HTTP-Method-Override:PATCH` as a header. ## Beta resources We sometimes release new API resources in **beta** status before we release them with general availability. Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible. We try to promote resources into general availability as quickly as possible. This happens after sufficient testing and when we're satisfied that we no longer need to make backwards-incompatible changes. We mark beta resources with a \"Beta\" callout in our documentation, pictured below: > ### This feature is in beta > > To use this feature, pass in a header including the `LD-API-Version` key with value set to `beta`. Use this header with each call. To learn more, read [Beta resources](/#section/Beta-resources). ### Using beta resources To use a beta resource, you must include a header in the request. If you call a beta resource without this header, you'll receive a `403` response. Use this header: ``` LD-API-Version: beta ``` ## Versioning We try hard to keep our REST API backwards compatible, but we occasionally have to make backwards-incompatible changes in the process of shipping new features. These breaking changes can cause unexpected behavior if you don't prepare for them accordingly. Updates to our REST API include support for the latest features in LaunchDarkly. We also release a new version of our REST API every time we make a breaking change. We provide simultaneous support for multiple API versions so you can migrate from your current API version to a new version at your own pace. ### Setting the API version per request You can set the API version on a specific request by sending an `LD-API-Version` header, as shown in the example below: ``` LD-API-Version: 20210729 ``` The header value is the version number of the API version you'd like to request. The number for each version corresponds to the date the version was released in yyyymmdd format. In the example above the version `20210729` corresponds to July 29, 2021. ### Setting the API version per access token When creating an access token, you must specify a specific version of the API to use. This ensures that integrations using this token cannot be broken by version changes. Tokens created before versioning was released have their version set to `20160426` (the version of the API that existed before versioning) so that they continue working the same way they did before versioning. If you would like to upgrade your integration to use a new API version, you can explicitly set the header described above. > ### Best practice: Set the header for every client or integration > > We recommend that you set the API version header explicitly in any client or integration you build. > > Only rely on the access token API version during manual testing. ### API version changelog | Version | Changes | |---|---| | `20210729` | <ul><li>Changed the [create approval request](/tag/Approvals#operation/postApprovalRequest) return value. It now returns HTTP Status Code `201` instead of `200`.</li><li> Changed the [get users](/tag/Users#operation/getUser) return value. It now returns a user record, not a user. </li><li> Added additional optional fields to environment, segments, flags, members, and segments, including the ability to create Big Segments. </li><li> Added default values for flag variations when new environments are created. </li><li> Added filtering and pagination for getting flags and members, including `limit`, `number`, `filter`, and `sort` query parameters. </li><li> Added endpoints for expiring user targets for flags and segments, scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions, and approvals. </li></ul> | | `20191212` | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags) now defaults to sending summaries of feature flag configurations, equivalent to setting the query parameter `summary=true`. Summaries omit flag targeting rules and individual user targets from the payload. </li><li> Added endpoints for flags, flag status, projects, environments, users, audit logs, members, users, custom roles, segments, usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial versioning of API. Tokens created before versioning have their version set to this.</li></ul> |
|
4
|
+
## Overview ## Authentication All REST API resources are authenticated with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens), or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens on your [Account settings](https://app.launchdarkly.com/settings/tokens) page. LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are used by our server-side SDKs, mobile SDKs, and client-side SDKs, respectively. **These keys cannot be used to access our REST API**. These keys are environment-specific, and can only perform read-only operations (fetching feature flag settings). | Auth mechanism | Allowed resources | Use cases | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | [Personal access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens) | Can be customized on a per-token basis | Building scripts, custom integrations, data export | | SDK keys | Can only access read-only SDK-specific resources and the firehose, restricted to a single environment | Server-side SDKs, Firehose API | | Mobile keys | Can only access read-only mobile SDK-specific resources, restricted to a single environment | Mobile SDKs | | Client-side ID | Single environment, only flags marked available to client-side | Client-side JavaScript | > #### Keep your access tokens and SDK keys private > > Access tokens should _never_ be exposed in untrusted contexts. Never put an access token in client-side JavaScript, or embed it in a mobile application. LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally expose an access token or SDK key, you can reset it from your [Account Settings](https://app.launchdarkly.com/settings#/tokens) page. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Via request header The preferred way to authenticate with the API is by adding an `Authorization` header containing your access token to your requests. The value of the `Authorization` header must be your access token. Manage personal access tokens from the [Account Settings](https://app.launchdarkly.com/settings/tokens) page. ### Via session cookie For testing purposes, you can make API calls directly from your web browser. If you're logged in to the application, the API will use your existing session to authenticate calls. If you have a [role](https://docs.launchdarkly.com/home/team/built-in-roles) other than Admin, or have a [custom role](https://docs.launchdarkly.com/home/team/custom-roles) defined, you may not have permission to perform some API calls. You will receive a `401` response code in that case. > ### Modifying the Origin header causes an error > > LaunchDarkly validates that the Origin header for any API request authenticated by a session cookie matches the expected Origin header. The expected Origin header is `https://app.launchdarkly.com`. > > If the Origin header does not match what's expected, LaunchDarkly returns an error. This error can prevent the LaunchDarkly app from working correctly. > > Any browser extension that intentionally changes the Origin header can cause this problem. For example, the `Allow-Control-Allow-Origin: *` Chrome extension changes the Origin header to `http://evil.com` and causes the app to fail. > > To prevent this error, do not modify your Origin header. > > LaunchDarkly does not require origin matching when authenticating with an access token, so this issue does not affect normal API usage. ## Representations All resources expect and return JSON response bodies. Error responses will also send a JSON body. Read [Errors](#section/Errors) for a more detailed description of the error format used by the API. In practice this means that you always get a response with a `Content-Type` header set to `application/json`. In addition, request bodies for `PUT`, `POST`, `REPORT` and `PATCH` requests must be encoded as JSON with a `Content-Type` header set to `application/json`. ### Summary and detailed representations When you fetch a list of resources, the response includes only the most important attributes of each resource. This is a _summary representation_ of the resource. When you fetch an individual resource, such as a single feature flag, you receive a _detailed representation_ of the resource. The best way to find a detailed representation is to follow links. Every summary representation includes a link to its detailed representation. In most cases, the detailed representation contains all of the attributes of the resource. In a few cases, the detailed representation contains many, but not all, of the attributes of the resource. Typically this happens when an attribute of the requested resource is itself paginated. You can request that the response include a particular attribute by using the `expand` request parameter. ### Links and addressability The best way to navigate the API is by following links. These are attributes in representations that link to other resources. The API always uses the same format for links: - Links to other resources within the API are encapsulated in a `_links` object. - If the resource has a corresponding link to HTML content on the site, it is stored in a special `_site` link. Each link has two attributes: an href (the URL) and a type (the content type). For example, a feature resource might return the following: ```json { \"_links\": { \"parent\": { \"href\": \"/api/features\", \"type\": \"application/json\" }, \"self\": { \"href\": \"/api/features/sort.order\", \"type\": \"application/json\" } }, \"_site\": { \"href\": \"/features/sort.order\", \"type\": \"text/html\" } } ``` From this, you can navigate to the parent collection of features by following the `parent` link, or navigate to the site page for the feature by following the `_site` link. Collections are always represented as a JSON object with an `items` attribute containing an array of representations. Like all other representations, collections have `_links` defined at the top level. Paginated collections include `first`, `last`, `next`, and `prev` links containing a URL with the respective set of elements in the collection. ### Expanding responses Sometimes the detailed representation of a resource does not include all of the attributes of the resource by default. If this is the case, the request method will clearly document this and describe which attributes you can include in an expanded response. To include the additional attributes, append the `expand` request parameter to your request and add a comma-separated list of the attributes to include. For example, when you append `?expand=members,roles` to the [Get team](/tag/Teams-(beta)#operation/getTeam) endpoint, the expanded response includes both of these attributes. ## Updates Resources that accept partial updates use the `PATCH` verb. Most resources support the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) format. Some resources also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format, and some resources support the [semantic patch](/reference#updates-using-semantic-patch) format, which is a way to specify the modifications to perform as a set of executable instructions. Each resource supports optional [comments](/reference#updates-with-comments) that you can submit with updates. Comments appear in outgoing webhooks, the audit log, and other integrations. ### Updates using JSON patch [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) is a way to specify the modifications to perform on a resource. JSON patch uses paths and a limited set of operations to describe how to transform the current state of the resource into a new state. JSON patch documents are always arrays, where each element contains an operation, a path to the field to update, and the new value. For example, in this feature flag representation: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"description\": \"This is the description\", ... } ``` You can change the feature flag's description with the following patch document: ```json [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"This is the new description\" }] ``` You can specify multiple modifications to perform in a single request. You can also test that certain preconditions are met before applying the patch: ```json [ { \"op\": \"test\", \"path\": \"/version\", \"value\": 10 }, { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" } ] ``` The above patch request tests whether the feature flag's `version` is `10`, and if so, changes the feature flag's description. Attributes that aren't editable, like a resource's `_links`, have names that start with an underscore. ### Updates using JSON merge patch [JSON merge patch](https://datatracker.ietf.org/doc/html/rfc7386) is another format for specifying the modifications to perform on a resource. JSON merge patch is less expressive than JSON patch but in many cases, it is simpler to construct a merge patch document. For example, you can change a feature flag's description with the following merge patch document: ```json { \"description\": \"New flag description\" } ``` ### Updates using semantic patch The API also supports the semantic patch format. A semantic `PATCH` is a way to specify the modifications to perform on a resource as a set of executable instructions. Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, you can define semantic patch instructions independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. Here's how: ``` Content-Type: application/json; domain-model=launchdarkly.semanticpatch ``` If you call a semantic patch resource without this header, you will receive a `400` response because your semantic patch will be interpreted as a JSON patch. The body of a semantic patch request takes the following properties: * `comment` (string): (Optional) A description of the update. * `environmentKey` (string): (Required for some resources only) The environment key. * `instructions` (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a `kind` property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object. The documentation for each resource that supports semantic patch includes the available instructions and any additional parameters. For example: ```json { \"comment\": \"optional comment\", \"instructions\": [ {\"kind\": \"turnFlagOn\"} ] } ``` If any instruction in the patch encounters an error, the endpoint returns an error and will not change the resource. In general, each instruction silently does nothing if the resource is already in the state you request. > ### Supported semantic patch API endpoints > > - [Patch experiment](/tag/Experiments-(beta)#operation/patchExperiment) > - [Patch segment](/tag/Segments#operation/patchSegment) > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) > - [Update flag trigger](/tag/Flag-triggers#operation/patchTriggerWorkflow) > - [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets) > - [Update expiring user target for flags](/tag/User-settings#operation/patchExpiringFlagsForUser) > - [Update expiring user targets for segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment) > - [Update scheduled changes workflow](/tag/Scheduled-changes#operation/patchFlagConfigScheduledChange) > - [Update team](/tag/Teams-(beta)#operation/patchTeam) ### Updates with comments You can submit optional comments with `PATCH` changes. To submit a comment along with a JSON Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"patch\": [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }] } ``` To submit a comment along with a JSON merge patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"merge\": { \"description\": \"New flag description\" } } ``` To submit a comment along with a semantic patch, use the following format: ```json { \"comment\": \"This is a comment string\", \"instructions\": [ {\"kind\": \"turnFlagOn\"} ] } ``` ## Errors The API always returns errors in a common format. Here's an example: ```json { \"code\": \"invalid_request\", \"message\": \"A feature with that key already exists\", \"id\": \"30ce6058-87da-11e4-b116-123b93f75cba\" } ``` The general class of error is indicated by the `code`. The `message` is a human-readable explanation of what went wrong. The `id` is a unique identifier. Use it when you're working with LaunchDarkly support to debug a problem with a specific API call. ### HTTP Status - Error Response Codes | Code | Definition | Description | Possible Solution | | ---- | ----------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | 400 | Invalid request | The request cannot be understood. | Ensure JSON syntax in request body is correct. | | 401 | Invalid access token | User is unauthorized or does not have permission for this API call. | Ensure your API access token is valid and has the appropriate permissions. | | 403 | Forbidden | User does not have access to this resource. | Ensure that the user or access token has proper permissions set. | | 404 | Invalid resource identifier | The requested resource is not valid. | Ensure that the resource is correctly identified by id or key. | | 405 | Method not allowed | The request method is not allowed on this resource. | Ensure that the HTTP verb is correct. | | 409 | Conflict | The API request can not be completed because it conflicted with a concurrent API request. | Retry your request. | | 422 | Unprocessable entity | The API request can not be completed because the update description can not be understood. | Ensure that the request body is correct for the type of patch you are using (JSON patch or semantic patch). | 429 | Too many requests | Read [Rate limiting](/#section/Rate-limiting). | Wait and try again later. | ## CORS The LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. If an `Origin` header is given in a request, it will be echoed as an explicitly allowed origin. Otherwise, a wildcard is returned: `Access-Control-Allow-Origin: *`. For more information on CORS, see the [CORS W3C Recommendation](http://www.w3.org/TR/cors). Example CORS headers might look like: ```http Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization Access-Control-Allow-Methods: OPTIONS, GET, DELETE, PATCH Access-Control-Allow-Origin: * Access-Control-Max-Age: 300 ``` You can make authenticated CORS calls just as you would make same-origin calls, using either [token or session-based authentication](#section/Authentication). If you’re using session auth, you should set the `withCredentials` property for your `xhr` request to `true`. You should never expose your access tokens to untrusted users. ## Rate limiting We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs will return a `429` status code. Calls to our APIs will include headers indicating the current rate limit status. The specific headers returned depend on the API route being called. The limits differ based on the route, authentication mechanism, and other factors. Routes that are not rate limited may not contain any of the headers described below. > ### Rate limiting and SDKs > > LaunchDarkly SDKs are never rate limited and do not use the API endpoints defined here. LaunchDarkly uses a different set of approaches, including streaming/server-sent events and a global CDN, to ensure availability to the routes used by LaunchDarkly SDKs. ### Global rate limits Authenticated requests are subject to a global limit. This is the maximum number of calls that can be made to the API per ten seconds. All personal access tokens on the account share this limit, so exceeding the limit with one access token will impact other tokens. Calls that are subject to global rate limits will return the headers below: | Header name | Description | | ------------------------------ | -------------------------------------------------------------------------------- | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | We do not publicly document the specific number of calls that can be made globally. This limit may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limit. ### Route-level rate limits Some authenticated routes have custom rate limits. These also reset every ten seconds. Any access tokens hitting the same route share this limit, so exceeding the limit with one access token may impact other tokens. Calls that are subject to route-level rate limits will return the headers below: | Header name | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------- | | `X-Ratelimit-Route-Remaining` | The maximum number of requests to the current route the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | A _route_ represents a specific URL pattern and verb. For example, the [Delete environment](/tag/Environments#operation/deleteEnvironment) endpoint is considered a single route, and each call to delete an environment counts against your route-level rate limit for that route. We do not publicly document the specific number of calls that can be made to each endpoint per ten seconds. These limits may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limits. ### IP-based rate limiting We also employ IP-based rate limiting on some API routes. If you hit an IP-based rate limit, your API response will include a `Retry-After` header indicating how long to wait before re-trying the call. Clients must wait at least `Retry-After` seconds before making additional calls to our API, and should employ jitter and backoff strategies to avoid triggering rate limits again. ## OpenAPI (Swagger) We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json) for our API. You can use this specification to generate client libraries to interact with our REST API in your language of choice. This specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to ease use in navigating the APIs in the tooling. ## Client libraries We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories). ## Method Overriding Some firewalls and HTTP clients restrict the use of verbs other than `GET` and `POST`. In those environments, our API endpoints that use `PUT`, `PATCH`, and `DELETE` verbs will be inaccessible. To avoid this issue, our API supports the `X-HTTP-Method-Override` header, allowing clients to \"tunnel\" `PUT`, `PATCH`, and `DELETE` requests via a `POST` request. For example, if you wish to call one of our `PATCH` resources via a `POST` request, you can include `X-HTTP-Method-Override:PATCH` as a header. ## Beta resources We sometimes release new API resources in **beta** status before we release them with general availability. Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible. We try to promote resources into general availability as quickly as possible. This happens after sufficient testing and when we're satisfied that we no longer need to make backwards-incompatible changes. We mark beta resources with a \"Beta\" callout in our documentation, pictured below: > ### This feature is in beta > > To use this feature, pass in a header including the `LD-API-Version` key with value set to `beta`. Use this header with each call. To learn more, read [Beta resources](/#section/Overview/Beta-resources). ### Using beta resources To use a beta resource, you must include a header in the request. If you call a beta resource without this header, you'll receive a `403` response. Use this header: ``` LD-API-Version: beta ``` ## Versioning We try hard to keep our REST API backwards compatible, but we occasionally have to make backwards-incompatible changes in the process of shipping new features. These breaking changes can cause unexpected behavior if you don't prepare for them accordingly. Updates to our REST API include support for the latest features in LaunchDarkly. We also release a new version of our REST API every time we make a breaking change. We provide simultaneous support for multiple API versions so you can migrate from your current API version to a new version at your own pace. ### Setting the API version per request You can set the API version on a specific request by sending an `LD-API-Version` header, as shown in the example below: ``` LD-API-Version: 20220603 ``` The header value is the version number of the API version you'd like to request. The number for each version corresponds to the date the version was released in yyyymmdd format. In the example above the version `20220603` corresponds to June 03, 2022. ### Setting the API version per access token When creating an access token, you must specify a specific version of the API to use. This ensures that integrations using this token cannot be broken by version changes. Tokens created before versioning was released have their version set to `20160426` (the version of the API that existed before versioning) so that they continue working the same way they did before versioning. If you would like to upgrade your integration to use a new API version, you can explicitly set the header described above. > ### Best practice: Set the header for every client or integration > > We recommend that you set the API version header explicitly in any client or integration you build. > > Only rely on the access token API version during manual testing. ### API version changelog |<div style=\"width:75px\">Version</div> | Changes | |---|---| | `20220603` | <ul><li>Changed the [list projects](tag/Projects#operation/getProjects) return value:<ul><li>Response is now paginated with a default limit of `20`.</li><li>Added support for filter and sort.</li><li>The project `environments` field is now expandable. This field is omitted by default.</li></ul></li><li>Changed the [get project](tag/Projects#operation/getProject) return value:<ul><li>The `environments` field is now expandable. This field is omitted by default.</li></ul></li></ul> | | `20210729` | <ul><li>Changed the [create approval request](/tag/Approvals#operation/postApprovalRequest) return value. It now returns HTTP Status Code `201` instead of `200`.</li><li> Changed the [get users](/tag/Users#operation/getUser) return value. It now returns a user record, not a user. </li><li> Added additional optional fields to environment, segments, flags, members, and segments, including the ability to create Big Segments. </li><li> Added default values for flag variations when new environments are created. </li><li> Added filtering and pagination for getting flags and members, including `limit`, `number`, `filter`, and `sort` query parameters. </li><li> Added endpoints for expiring user targets for flags and segments, scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions, and approvals. </li></ul> | | `20191212` | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags) now defaults to sending summaries of feature flag configurations, equivalent to setting the query parameter `summary=true`. Summaries omit flag targeting rules and individual user targets from the payload. </li><li> Added endpoints for flags, flag status, projects, environments, users, audit logs, members, users, custom roles, segments, usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial versioning of API. Tokens created before versioning have their version set to this.</li></ul> |
|
5
5
|
|
6
6
|
The version of the OpenAPI document: 2.0
|
7
7
|
Contact: support@launchdarkly.com
|
8
8
|
Generated by: https://openapi-generator.tech
|
9
|
-
OpenAPI Generator version:
|
9
|
+
OpenAPI Generator version: 6.0.0
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
@@ -20,7 +20,7 @@ module LaunchDarklyApi
|
|
20
20
|
@api_client = api_client
|
21
21
|
end
|
22
22
|
# Delete scheduled changes workflow
|
23
|
-
# Delete a scheduled changes workflow
|
23
|
+
# Delete a scheduled changes workflow.
|
24
24
|
# @param project_key [String] The project key
|
25
25
|
# @param feature_flag_key [String] The feature flag key
|
26
26
|
# @param environment_key [String] The environment key
|
@@ -33,7 +33,7 @@ module LaunchDarklyApi
|
|
33
33
|
end
|
34
34
|
|
35
35
|
# Delete scheduled changes workflow
|
36
|
-
# Delete a scheduled changes workflow
|
36
|
+
# Delete a scheduled changes workflow.
|
37
37
|
# @param project_key [String] The project key
|
38
38
|
# @param feature_flag_key [String] The feature flag key
|
39
39
|
# @param environment_key [String] The environment key
|
@@ -101,7 +101,7 @@ module LaunchDarklyApi
|
|
101
101
|
end
|
102
102
|
|
103
103
|
# Get a scheduled change
|
104
|
-
# Get a scheduled change that will be applied to the feature flag by ID
|
104
|
+
# Get a scheduled change that will be applied to the feature flag by ID.
|
105
105
|
# @param project_key [String] The project key
|
106
106
|
# @param feature_flag_key [String] The feature flag key
|
107
107
|
# @param environment_key [String] The environment key
|
@@ -114,7 +114,7 @@ module LaunchDarklyApi
|
|
114
114
|
end
|
115
115
|
|
116
116
|
# Get a scheduled change
|
117
|
-
# Get a scheduled change that will be applied to the feature flag by ID
|
117
|
+
# Get a scheduled change that will be applied to the feature flag by ID.
|
118
118
|
# @param project_key [String] The project key
|
119
119
|
# @param feature_flag_key [String] The feature flag key
|
120
120
|
# @param environment_key [String] The environment key
|
@@ -257,14 +257,14 @@ module LaunchDarklyApi
|
|
257
257
|
end
|
258
258
|
|
259
259
|
# Update scheduled changes workflow
|
260
|
-
#
|
260
|
+
# Update a scheduled change, overriding existing instructions with the new ones. Updating a scheduled change uses the semantic patch format. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). ### Instructions Semantic patch requests support the following `kind` instructions for updating scheduled changes. #### deleteScheduledChange Removes the scheduled change. #### replaceScheduledChangesInstructions Removes the existing scheduled changes and replaces them with the new instructions. ##### Parameters - `value`: An array of the new actions to perform when the execution date for these scheduled changes arrives. Supported scheduled actions are `turnFlagOn` and `turnFlagOff`. For example, to replace the scheduled changes, use this request body: ```json { \"comment\": \"optional comment\", \"instructions\": [ { \"kind\": \"replaceScheduledChangesInstructions\", \"value\": [ {\"kind\": \"turnFlagOff\"} ] } ] } ``` #### updateScheduledChangesExecutionDate Updates the execution date for the scheduled changes. ##### Parameters - `value`: the new execution date, in Unix milliseconds.
|
261
261
|
# @param project_key [String] The project key
|
262
262
|
# @param feature_flag_key [String] The feature flag key
|
263
263
|
# @param environment_key [String] The environment key
|
264
264
|
# @param id [String] The scheduled change ID
|
265
265
|
# @param flag_scheduled_changes_input [FlagScheduledChangesInput]
|
266
266
|
# @param [Hash] opts the optional parameters
|
267
|
-
# @option opts [Boolean] :ignore_conflicts Whether
|
267
|
+
# @option opts [Boolean] :ignore_conflicts Whether to succeed (`true`) or fail (`false`) when these new instructions conflict with existing scheduled changes
|
268
268
|
# @return [FeatureFlagScheduledChange]
|
269
269
|
def patch_flag_config_scheduled_change(project_key, feature_flag_key, environment_key, id, flag_scheduled_changes_input, opts = {})
|
270
270
|
data, _status_code, _headers = patch_flag_config_scheduled_change_with_http_info(project_key, feature_flag_key, environment_key, id, flag_scheduled_changes_input, opts)
|
@@ -272,14 +272,14 @@ module LaunchDarklyApi
|
|
272
272
|
end
|
273
273
|
|
274
274
|
# Update scheduled changes workflow
|
275
|
-
#
|
275
|
+
# Update a scheduled change, overriding existing instructions with the new ones. Updating a scheduled change uses the semantic patch format. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). ### Instructions Semantic patch requests support the following `kind` instructions for updating scheduled changes. #### deleteScheduledChange Removes the scheduled change. #### replaceScheduledChangesInstructions Removes the existing scheduled changes and replaces them with the new instructions. ##### Parameters - `value`: An array of the new actions to perform when the execution date for these scheduled changes arrives. Supported scheduled actions are `turnFlagOn` and `turnFlagOff`. For example, to replace the scheduled changes, use this request body: ```json { \"comment\": \"optional comment\", \"instructions\": [ { \"kind\": \"replaceScheduledChangesInstructions\", \"value\": [ {\"kind\": \"turnFlagOff\"} ] } ] } ``` #### updateScheduledChangesExecutionDate Updates the execution date for the scheduled changes. ##### Parameters - `value`: the new execution date, in Unix milliseconds.
|
276
276
|
# @param project_key [String] The project key
|
277
277
|
# @param feature_flag_key [String] The feature flag key
|
278
278
|
# @param environment_key [String] The environment key
|
279
279
|
# @param id [String] The scheduled change ID
|
280
280
|
# @param flag_scheduled_changes_input [FlagScheduledChangesInput]
|
281
281
|
# @param [Hash] opts the optional parameters
|
282
|
-
# @option opts [Boolean] :ignore_conflicts Whether
|
282
|
+
# @option opts [Boolean] :ignore_conflicts Whether to succeed (`true`) or fail (`false`) when these new instructions conflict with existing scheduled changes
|
283
283
|
# @return [Array<(FeatureFlagScheduledChange, Integer, Hash)>] FeatureFlagScheduledChange data, response status code and response headers
|
284
284
|
def patch_flag_config_scheduled_change_with_http_info(project_key, feature_flag_key, environment_key, id, flag_scheduled_changes_input, opts = {})
|
285
285
|
if @api_client.config.debugging
|
@@ -352,13 +352,13 @@ module LaunchDarklyApi
|
|
352
352
|
end
|
353
353
|
|
354
354
|
# Create scheduled changes workflow
|
355
|
-
# Create scheduled changes for a feature flag. If the ignoreConficts query parameter is false and
|
355
|
+
# Create scheduled changes for a feature flag. If the `ignoreConficts` query parameter is false and there are conflicts between these instructions and existing scheduled changes, the request will fail. If the parameter is true and there are conflicts, the request will succeed.
|
356
356
|
# @param project_key [String] The project key
|
357
357
|
# @param feature_flag_key [String] The feature flag key
|
358
358
|
# @param environment_key [String] The environment key
|
359
359
|
# @param post_flag_scheduled_changes_input [PostFlagScheduledChangesInput]
|
360
360
|
# @param [Hash] opts the optional parameters
|
361
|
-
# @option opts [Boolean] :ignore_conflicts Whether
|
361
|
+
# @option opts [Boolean] :ignore_conflicts Whether to succeed (`true`) or fail (`false`) when these instructions conflict with existing scheduled changes
|
362
362
|
# @return [FeatureFlagScheduledChange]
|
363
363
|
def post_flag_config_scheduled_changes(project_key, feature_flag_key, environment_key, post_flag_scheduled_changes_input, opts = {})
|
364
364
|
data, _status_code, _headers = post_flag_config_scheduled_changes_with_http_info(project_key, feature_flag_key, environment_key, post_flag_scheduled_changes_input, opts)
|
@@ -366,13 +366,13 @@ module LaunchDarklyApi
|
|
366
366
|
end
|
367
367
|
|
368
368
|
# Create scheduled changes workflow
|
369
|
-
# Create scheduled changes for a feature flag. If the ignoreConficts query parameter is false and
|
369
|
+
# Create scheduled changes for a feature flag. If the `ignoreConficts` query parameter is false and there are conflicts between these instructions and existing scheduled changes, the request will fail. If the parameter is true and there are conflicts, the request will succeed.
|
370
370
|
# @param project_key [String] The project key
|
371
371
|
# @param feature_flag_key [String] The feature flag key
|
372
372
|
# @param environment_key [String] The environment key
|
373
373
|
# @param post_flag_scheduled_changes_input [PostFlagScheduledChangesInput]
|
374
374
|
# @param [Hash] opts the optional parameters
|
375
|
-
# @option opts [Boolean] :ignore_conflicts Whether
|
375
|
+
# @option opts [Boolean] :ignore_conflicts Whether to succeed (`true`) or fail (`false`) when these instructions conflict with existing scheduled changes
|
376
376
|
# @return [Array<(FeatureFlagScheduledChange, Integer, Hash)>] FeatureFlagScheduledChange data, response status code and response headers
|
377
377
|
def post_flag_config_scheduled_changes_with_http_info(project_key, feature_flag_key, environment_key, post_flag_scheduled_changes_input, opts = {})
|
378
378
|
if @api_client.config.debugging
|
@@ -1,12 +1,12 @@
|
|
1
1
|
=begin
|
2
2
|
#LaunchDarkly REST API
|
3
3
|
|
4
|
-
## Overview ## Authentication All REST API resources are authenticated with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens), or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens on your [Account settings](https://app.launchdarkly.com/settings/tokens) page. LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are used by our server-side SDKs, mobile SDKs, and client-side SDKs, respectively. **These keys cannot be used to access our REST API**. These keys are environment-specific, and can only perform read-only operations (fetching feature flag settings). | Auth mechanism | Allowed resources | Use cases | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | [Personal access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens) | Can be customized on a per-token basis | Building scripts, custom integrations, data export | | SDK keys | Can only access read-only SDK-specific resources and the firehose, restricted to a single environment | Server-side SDKs, Firehose API | | Mobile keys | Can only access read-only mobile SDK-specific resources, restricted to a single environment | Mobile SDKs | | Client-side ID | Single environment, only flags marked available to client-side | Client-side JavaScript | > #### Keep your access tokens and SDK keys private > > Access tokens should _never_ be exposed in untrusted contexts. Never put an access token in client-side JavaScript, or embed it in a mobile application. LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally expose an access token or SDK key, you can reset it from your [Account Settings](https://app.launchdarkly.com/settings#/tokens) page. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Via request header The preferred way to authenticate with the API is by adding an `Authorization` header containing your access token to your requests. The value of the `Authorization` header must be your access token. Manage personal access tokens from the [Account Settings](https://app.launchdarkly.com/settings/tokens) page. ### Via session cookie For testing purposes, you can make API calls directly from your web browser. If you're logged in to the application, the API will use your existing session to authenticate calls. If you have a [role](https://docs.launchdarkly.com/home/team/built-in-roles) other than Admin, or have a [custom role](https://docs.launchdarkly.com/home/team/custom-roles) defined, you may not have permission to perform some API calls. You will receive a `401` response code in that case. > ### Modifying the Origin header causes an error > > LaunchDarkly validates that the Origin header for any API request authenticated by a session cookie matches the expected Origin header. The expected Origin header is `https://app.launchdarkly.com`. > > If the Origin header does not match what's expected, LaunchDarkly returns an error. This error can prevent the LaunchDarkly app from working correctly. > > Any browser extension that intentionally changes the Origin header can cause this problem. For example, the `Allow-Control-Allow-Origin: *` Chrome extension changes the Origin header to `http://evil.com` and causes the app to fail. > > To prevent this error, do not modify your Origin header. > > LaunchDarkly does not require origin matching when authenticating with an access token, so this issue does not affect normal API usage. ## Representations All resources expect and return JSON response bodies. Error responses will also send a JSON body. Read [Errors](#section/Errors) for a more detailed description of the error format used by the API. In practice this means that you always get a response with a `Content-Type` header set to `application/json`. In addition, request bodies for `PUT`, `POST`, `REPORT` and `PATCH` requests must be encoded as JSON with a `Content-Type` header set to `application/json`. ### Summary and detailed representations When you fetch a list of resources, the response includes only the most important attributes of each resource. This is a _summary representation_ of the resource. When you fetch an individual resource (for example, a single feature flag), you receive a _detailed representation_ containing all of the attributes of the resource. The best way to find a detailed representation is to follow links. Every summary representation includes a link to its detailed representation. ### Links and addressability The best way to navigate the API is by following links. These are attributes in representations that link to other resources. The API always uses the same format for links: - Links to other resources within the API are encapsulated in a `_links` object. - If the resource has a corresponding link to HTML content on the site, it is stored in a special `_site` link. Each link has two attributes: an href (the URL) and a type (the content type). For example, a feature resource might return the following: ```json { \"_links\": { \"parent\": { \"href\": \"/api/features\", \"type\": \"application/json\" }, \"self\": { \"href\": \"/api/features/sort.order\", \"type\": \"application/json\" } }, \"_site\": { \"href\": \"/features/sort.order\", \"type\": \"text/html\" } } ``` From this, you can navigate to the parent collection of features by following the `parent` link, or navigate to the site page for the feature by following the `_site` link. Collections are always represented as a JSON object with an `items` attribute containing an array of representations. Like all other representations, collections have `_links` defined at the top level. Paginated collections include `first`, `last`, `next`, and `prev` links containing a URL with the respective set of elements in the collection. ## Updates Resources that accept partial updates use the `PATCH` verb, and support the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) format. Some resources also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format. In addition, some resources support optional comments that can be submitted with updates. Comments appear in outgoing webhooks, the audit log, and other integrations. ### Updates via JSON Patch [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) is a way to specify the modifications to perform on a resource. For example, in this feature flag representation: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"description\": \"This is the description\", ... } ``` You can change the feature flag's description with the following patch document: ```json [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"This is the new description\" }] ``` JSON Patch documents are always arrays. You can specify multiple modifications to perform in a single request. You can also test that certain preconditions are met before applying the patch: ```json [ { \"op\": \"test\", \"path\": \"/version\", \"value\": 10 }, { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" } ] ``` The above patch request tests whether the feature flag's `version` is `10`, and if so, changes the feature flag's description. Attributes that aren't editable, like a resource's `_links`, have names that start with an underscore. ### Updates via JSON Merge Patch The API also supports the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format, as well as the [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) resource. JSON Merge Patch is less expressive than JSON Patch but in many cases, it is simpler to construct a merge patch document. For example, you can change a feature flag's description with the following merge patch document: ```json { \"description\": \"New flag description\" } ``` ### Updates with comments You can submit optional comments with `PATCH` changes. The [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) resource supports comments. To submit a comment along with a JSON Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"patch\": [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }] } ``` To submit a comment along with a JSON Merge Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"merge\": { \"description\": \"New flag description\" } } ``` ### Updates via semantic patches The API also supports the Semantic patch format. A semantic `PATCH` is a way to specify the modifications to perform on a resource as a set of executable instructions. JSON Patch uses paths and a limited set of operations to describe how to transform the current state of the resource into a new state. Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, semantic patch instructions can also be defined independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date. For example, in this feature flag configuration in environment Production: ```json { \"name\": \"Alternate sort order\", \"kind\": \"boolean\", \"key\": \"sort.order\", ... \"environments\": { \"production\": { \"on\": true, \"archived\": false, \"salt\": \"c29ydC5vcmRlcg==\", \"sel\": \"8de1085cb7354b0ab41c0e778376dfd3\", \"lastModified\": 1469131558260, \"version\": 81, \"targets\": [ { \"values\": [ \"Gerhard.Little@yahoo.com\" ], \"variation\": 0 }, { \"values\": [ \"1461797806429-33-861961230\", \"438580d8-02ee-418d-9eec-0085cab2bdf0\" ], \"variation\": 1 } ], \"rules\": [], \"fallthrough\": { \"variation\": 0 }, \"offVariation\": 1, \"prerequisites\": [], \"_site\": { \"href\": \"/default/production/features/sort.order\", \"type\": \"text/html\" } } } } ``` You can add a date you want a user to be removed from the feature flag's user targets. For example, “remove user 1461797806429-33-861961230 from the user target for variation 0 on the Alternate sort order flag in the production environment on Wed Jul 08 2020 at 15:27:41 pm”. This is done using the following: ```json { \"comment\": \"update expiring user targets\", \"instructions\": [ { \"kind\": \"removeExpireUserTargetDate\", \"userKey\": \"userKey\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\" }, { \"kind\": \"updateExpireUserTargetDate\", \"userKey\": \"userKey2\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\", \"value\": 1587582000000 }, { \"kind\": \"addExpireUserTargetDate\", \"userKey\": \"userKey3\", \"variationId\": \"978d53f9-7fe3-4a63-992d-97bcb4535dc8\", \"value\": 1594247266386 } ] } ``` Here is another example. In this feature flag configuration: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"environments\": { \"test\": { \"on\": true } } } ``` You can change the feature flag's description with the following patch document as a set of executable instructions. For example, “add user X to targets for variation Y and remove user A from targets for variation B for test flag”: ```json { \"comment\": \"\", \"instructions\": [ { \"kind\": \"removeUserTargets\", \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"], \"variationId\": \"852cb784-54ff-46b9-8c35-5498d2e4f270\" }, { \"kind\": \"addUserTargets\", \"values\": [\"438580d8-02ee-418d-9eec-0085cab2bdf0\"], \"variationId\": \"1bb18465-33b6-49aa-a3bd-eeb6650b33ad\" } ] } ``` > ### Supported semantic patch API endpoints > > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) > - [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets) > - [Update expiring user target for flags](/tag/User-settings#operation/patchExpiringFlagsForUser) > - [Update expiring user targets on segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment) ## Errors The API always returns errors in a common format. Here's an example: ```json { \"code\": \"invalid_request\", \"message\": \"A feature with that key already exists\", \"id\": \"30ce6058-87da-11e4-b116-123b93f75cba\" } ``` The general class of error is indicated by the `code`. The `message` is a human-readable explanation of what went wrong. The `id` is a unique identifier. Use it when you're working with LaunchDarkly support to debug a problem with a specific API call. ### HTTP Status - Error Response Codes | Code | Definition | Desc. | Possible Solution | | ---- | ----------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | 400 | Bad Request | A request that fails may return this HTTP response code. | Ensure JSON syntax in request body is correct. | | 401 | Unauthorized | User doesn't have permission to an API call. | Ensure your SDK key is good. | | 403 | Forbidden | User does not have permission for operation. | Ensure that the user or access token has proper permissions set. | | 409 | Conflict | The API request could not be completed because it conflicted with a concurrent API request. | Retry your request. | | 429 | Too many requests | See [Rate limiting](/#section/Rate-limiting). | Wait and try again later. | ## CORS The LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. If an `Origin` header is given in a request, it will be echoed as an explicitly allowed origin. Otherwise, a wildcard is returned: `Access-Control-Allow-Origin: *`. For more information on CORS, see the [CORS W3C Recommendation](http://www.w3.org/TR/cors). Example CORS headers might look like: ```http Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization Access-Control-Allow-Methods: OPTIONS, GET, DELETE, PATCH Access-Control-Allow-Origin: * Access-Control-Max-Age: 300 ``` You can make authenticated CORS calls just as you would make same-origin calls, using either [token or session-based authentication](#section/Authentication). If you’re using session auth, you should set the `withCredentials` property for your `xhr` request to `true`. You should never expose your access tokens to untrusted users. ## Rate limiting We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs will return a `429` status code. Calls to our APIs will include headers indicating the current rate limit status. The specific headers returned depend on the API route being called. The limits differ based on the route, authentication mechanism, and other factors. Routes that are not rate limited may not contain any of the headers described below. > ### Rate limiting and SDKs > > LaunchDarkly SDKs are never rate limited and do not use the API endpoints defined here. LaunchDarkly uses a different set of approaches, including streaming/server-sent events and a global CDN, to ensure availability to the routes used by LaunchDarkly SDKs. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Global rate limits Authenticated requests are subject to a global limit. This is the maximum number of calls that can be made to the API per ten seconds. All personal access tokens on the account share this limit, so exceeding the limit with one access token will impact other tokens. Calls that are subject to global rate limits will return the headers below: | Header name | Description | | ------------------------------ | -------------------------------------------------------------------------------- | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | We do not publicly document the specific number of calls that can be made globally. This limit may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limit. ### Route-level rate limits Some authenticated routes have custom rate limits. These also reset every ten seconds. Any access tokens hitting the same route share this limit, so exceeding the limit with one access token may impact other tokens. Calls that are subject to route-level rate limits will return the headers below: | Header name | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------- | | `X-Ratelimit-Route-Remaining` | The maximum number of requests to the current route the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | A _route_ represents a specific URL pattern and verb. For example, the [Delete environment](/tag/Environments#operation/deleteEnvironment) endpoint is considered a single route, and each call to delete an environment counts against your route-level rate limit for that route. We do not publicly document the specific number of calls that can be made to each endpoint per ten seconds. These limits may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limits. ### IP-based rate limiting We also employ IP-based rate limiting on some API routes. If you hit an IP-based rate limit, your API response will include a `Retry-After` header indicating how long to wait before re-trying the call. Clients must wait at least `Retry-After` seconds before making additional calls to our API, and should employ jitter and backoff strategies to avoid triggering rate limits again. ## OpenAPI (Swagger) We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json) for our API. You can use this specification to generate client libraries to interact with our REST API in your language of choice. This specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to ease use in navigating the APIs in the tooling. ## Client libraries We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories). ## Method Overriding Some firewalls and HTTP clients restrict the use of verbs other than `GET` and `POST`. In those environments, our API endpoints that use `PUT`, `PATCH`, and `DELETE` verbs will be inaccessible. To avoid this issue, our API supports the `X-HTTP-Method-Override` header, allowing clients to \"tunnel\" `PUT`, `PATCH`, and `DELETE` requests via a `POST` request. For example, if you wish to call one of our `PATCH` resources via a `POST` request, you can include `X-HTTP-Method-Override:PATCH` as a header. ## Beta resources We sometimes release new API resources in **beta** status before we release them with general availability. Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible. We try to promote resources into general availability as quickly as possible. This happens after sufficient testing and when we're satisfied that we no longer need to make backwards-incompatible changes. We mark beta resources with a \"Beta\" callout in our documentation, pictured below: > ### This feature is in beta > > To use this feature, pass in a header including the `LD-API-Version` key with value set to `beta`. Use this header with each call. To learn more, read [Beta resources](/#section/Beta-resources). ### Using beta resources To use a beta resource, you must include a header in the request. If you call a beta resource without this header, you'll receive a `403` response. Use this header: ``` LD-API-Version: beta ``` ## Versioning We try hard to keep our REST API backwards compatible, but we occasionally have to make backwards-incompatible changes in the process of shipping new features. These breaking changes can cause unexpected behavior if you don't prepare for them accordingly. Updates to our REST API include support for the latest features in LaunchDarkly. We also release a new version of our REST API every time we make a breaking change. We provide simultaneous support for multiple API versions so you can migrate from your current API version to a new version at your own pace. ### Setting the API version per request You can set the API version on a specific request by sending an `LD-API-Version` header, as shown in the example below: ``` LD-API-Version: 20210729 ``` The header value is the version number of the API version you'd like to request. The number for each version corresponds to the date the version was released in yyyymmdd format. In the example above the version `20210729` corresponds to July 29, 2021. ### Setting the API version per access token When creating an access token, you must specify a specific version of the API to use. This ensures that integrations using this token cannot be broken by version changes. Tokens created before versioning was released have their version set to `20160426` (the version of the API that existed before versioning) so that they continue working the same way they did before versioning. If you would like to upgrade your integration to use a new API version, you can explicitly set the header described above. > ### Best practice: Set the header for every client or integration > > We recommend that you set the API version header explicitly in any client or integration you build. > > Only rely on the access token API version during manual testing. ### API version changelog | Version | Changes | |---|---| | `20210729` | <ul><li>Changed the [create approval request](/tag/Approvals#operation/postApprovalRequest) return value. It now returns HTTP Status Code `201` instead of `200`.</li><li> Changed the [get users](/tag/Users#operation/getUser) return value. It now returns a user record, not a user. </li><li> Added additional optional fields to environment, segments, flags, members, and segments, including the ability to create Big Segments. </li><li> Added default values for flag variations when new environments are created. </li><li> Added filtering and pagination for getting flags and members, including `limit`, `number`, `filter`, and `sort` query parameters. </li><li> Added endpoints for expiring user targets for flags and segments, scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions, and approvals. </li></ul> | | `20191212` | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags) now defaults to sending summaries of feature flag configurations, equivalent to setting the query parameter `summary=true`. Summaries omit flag targeting rules and individual user targets from the payload. </li><li> Added endpoints for flags, flag status, projects, environments, users, audit logs, members, users, custom roles, segments, usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial versioning of API. Tokens created before versioning have their version set to this.</li></ul> |
|
4
|
+
## Overview ## Authentication All REST API resources are authenticated with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens), or session cookies. Other authentication mechanisms are not supported. You can manage personal access tokens on your [Account settings](https://app.launchdarkly.com/settings/tokens) page. LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are used by our server-side SDKs, mobile SDKs, and client-side SDKs, respectively. **These keys cannot be used to access our REST API**. These keys are environment-specific, and can only perform read-only operations (fetching feature flag settings). | Auth mechanism | Allowed resources | Use cases | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | [Personal access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens) | Can be customized on a per-token basis | Building scripts, custom integrations, data export | | SDK keys | Can only access read-only SDK-specific resources and the firehose, restricted to a single environment | Server-side SDKs, Firehose API | | Mobile keys | Can only access read-only mobile SDK-specific resources, restricted to a single environment | Mobile SDKs | | Client-side ID | Single environment, only flags marked available to client-side | Client-side JavaScript | > #### Keep your access tokens and SDK keys private > > Access tokens should _never_ be exposed in untrusted contexts. Never put an access token in client-side JavaScript, or embed it in a mobile application. LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally expose an access token or SDK key, you can reset it from your [Account Settings](https://app.launchdarkly.com/settings#/tokens) page. > > The client-side ID is safe to embed in untrusted contexts. It's designed for use in client-side JavaScript. ### Via request header The preferred way to authenticate with the API is by adding an `Authorization` header containing your access token to your requests. The value of the `Authorization` header must be your access token. Manage personal access tokens from the [Account Settings](https://app.launchdarkly.com/settings/tokens) page. ### Via session cookie For testing purposes, you can make API calls directly from your web browser. If you're logged in to the application, the API will use your existing session to authenticate calls. If you have a [role](https://docs.launchdarkly.com/home/team/built-in-roles) other than Admin, or have a [custom role](https://docs.launchdarkly.com/home/team/custom-roles) defined, you may not have permission to perform some API calls. You will receive a `401` response code in that case. > ### Modifying the Origin header causes an error > > LaunchDarkly validates that the Origin header for any API request authenticated by a session cookie matches the expected Origin header. The expected Origin header is `https://app.launchdarkly.com`. > > If the Origin header does not match what's expected, LaunchDarkly returns an error. This error can prevent the LaunchDarkly app from working correctly. > > Any browser extension that intentionally changes the Origin header can cause this problem. For example, the `Allow-Control-Allow-Origin: *` Chrome extension changes the Origin header to `http://evil.com` and causes the app to fail. > > To prevent this error, do not modify your Origin header. > > LaunchDarkly does not require origin matching when authenticating with an access token, so this issue does not affect normal API usage. ## Representations All resources expect and return JSON response bodies. Error responses will also send a JSON body. Read [Errors](#section/Errors) for a more detailed description of the error format used by the API. In practice this means that you always get a response with a `Content-Type` header set to `application/json`. In addition, request bodies for `PUT`, `POST`, `REPORT` and `PATCH` requests must be encoded as JSON with a `Content-Type` header set to `application/json`. ### Summary and detailed representations When you fetch a list of resources, the response includes only the most important attributes of each resource. This is a _summary representation_ of the resource. When you fetch an individual resource, such as a single feature flag, you receive a _detailed representation_ of the resource. The best way to find a detailed representation is to follow links. Every summary representation includes a link to its detailed representation. In most cases, the detailed representation contains all of the attributes of the resource. In a few cases, the detailed representation contains many, but not all, of the attributes of the resource. Typically this happens when an attribute of the requested resource is itself paginated. You can request that the response include a particular attribute by using the `expand` request parameter. ### Links and addressability The best way to navigate the API is by following links. These are attributes in representations that link to other resources. The API always uses the same format for links: - Links to other resources within the API are encapsulated in a `_links` object. - If the resource has a corresponding link to HTML content on the site, it is stored in a special `_site` link. Each link has two attributes: an href (the URL) and a type (the content type). For example, a feature resource might return the following: ```json { \"_links\": { \"parent\": { \"href\": \"/api/features\", \"type\": \"application/json\" }, \"self\": { \"href\": \"/api/features/sort.order\", \"type\": \"application/json\" } }, \"_site\": { \"href\": \"/features/sort.order\", \"type\": \"text/html\" } } ``` From this, you can navigate to the parent collection of features by following the `parent` link, or navigate to the site page for the feature by following the `_site` link. Collections are always represented as a JSON object with an `items` attribute containing an array of representations. Like all other representations, collections have `_links` defined at the top level. Paginated collections include `first`, `last`, `next`, and `prev` links containing a URL with the respective set of elements in the collection. ### Expanding responses Sometimes the detailed representation of a resource does not include all of the attributes of the resource by default. If this is the case, the request method will clearly document this and describe which attributes you can include in an expanded response. To include the additional attributes, append the `expand` request parameter to your request and add a comma-separated list of the attributes to include. For example, when you append `?expand=members,roles` to the [Get team](/tag/Teams-(beta)#operation/getTeam) endpoint, the expanded response includes both of these attributes. ## Updates Resources that accept partial updates use the `PATCH` verb. Most resources support the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) format. Some resources also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) format, and some resources support the [semantic patch](/reference#updates-using-semantic-patch) format, which is a way to specify the modifications to perform as a set of executable instructions. Each resource supports optional [comments](/reference#updates-with-comments) that you can submit with updates. Comments appear in outgoing webhooks, the audit log, and other integrations. ### Updates using JSON patch [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) is a way to specify the modifications to perform on a resource. JSON patch uses paths and a limited set of operations to describe how to transform the current state of the resource into a new state. JSON patch documents are always arrays, where each element contains an operation, a path to the field to update, and the new value. For example, in this feature flag representation: ```json { \"name\": \"New recommendations engine\", \"key\": \"engine.enable\", \"description\": \"This is the description\", ... } ``` You can change the feature flag's description with the following patch document: ```json [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"This is the new description\" }] ``` You can specify multiple modifications to perform in a single request. You can also test that certain preconditions are met before applying the patch: ```json [ { \"op\": \"test\", \"path\": \"/version\", \"value\": 10 }, { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" } ] ``` The above patch request tests whether the feature flag's `version` is `10`, and if so, changes the feature flag's description. Attributes that aren't editable, like a resource's `_links`, have names that start with an underscore. ### Updates using JSON merge patch [JSON merge patch](https://datatracker.ietf.org/doc/html/rfc7386) is another format for specifying the modifications to perform on a resource. JSON merge patch is less expressive than JSON patch but in many cases, it is simpler to construct a merge patch document. For example, you can change a feature flag's description with the following merge patch document: ```json { \"description\": \"New flag description\" } ``` ### Updates using semantic patch The API also supports the semantic patch format. A semantic `PATCH` is a way to specify the modifications to perform on a resource as a set of executable instructions. Semantic patch allows you to be explicit about intent using precise, custom instructions. In many cases, you can define semantic patch instructions independently of the current state of the resource. This can be useful when defining a change that may be applied at a future date. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. Here's how: ``` Content-Type: application/json; domain-model=launchdarkly.semanticpatch ``` If you call a semantic patch resource without this header, you will receive a `400` response because your semantic patch will be interpreted as a JSON patch. The body of a semantic patch request takes the following properties: * `comment` (string): (Optional) A description of the update. * `environmentKey` (string): (Required for some resources only) The environment key. * `instructions` (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a `kind` property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object. The documentation for each resource that supports semantic patch includes the available instructions and any additional parameters. For example: ```json { \"comment\": \"optional comment\", \"instructions\": [ {\"kind\": \"turnFlagOn\"} ] } ``` If any instruction in the patch encounters an error, the endpoint returns an error and will not change the resource. In general, each instruction silently does nothing if the resource is already in the state you request. > ### Supported semantic patch API endpoints > > - [Patch experiment](/tag/Experiments-(beta)#operation/patchExperiment) > - [Patch segment](/tag/Segments#operation/patchSegment) > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag) > - [Update flag trigger](/tag/Flag-triggers#operation/patchTriggerWorkflow) > - [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets) > - [Update expiring user target for flags](/tag/User-settings#operation/patchExpiringFlagsForUser) > - [Update expiring user targets for segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment) > - [Update scheduled changes workflow](/tag/Scheduled-changes#operation/patchFlagConfigScheduledChange) > - [Update team](/tag/Teams-(beta)#operation/patchTeam) ### Updates with comments You can submit optional comments with `PATCH` changes. To submit a comment along with a JSON Patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"patch\": [{ \"op\": \"replace\", \"path\": \"/description\", \"value\": \"The new description\" }] } ``` To submit a comment along with a JSON merge patch document, use the following format: ```json { \"comment\": \"This is a comment string\", \"merge\": { \"description\": \"New flag description\" } } ``` To submit a comment along with a semantic patch, use the following format: ```json { \"comment\": \"This is a comment string\", \"instructions\": [ {\"kind\": \"turnFlagOn\"} ] } ``` ## Errors The API always returns errors in a common format. Here's an example: ```json { \"code\": \"invalid_request\", \"message\": \"A feature with that key already exists\", \"id\": \"30ce6058-87da-11e4-b116-123b93f75cba\" } ``` The general class of error is indicated by the `code`. The `message` is a human-readable explanation of what went wrong. The `id` is a unique identifier. Use it when you're working with LaunchDarkly support to debug a problem with a specific API call. ### HTTP Status - Error Response Codes | Code | Definition | Description | Possible Solution | | ---- | ----------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | 400 | Invalid request | The request cannot be understood. | Ensure JSON syntax in request body is correct. | | 401 | Invalid access token | User is unauthorized or does not have permission for this API call. | Ensure your API access token is valid and has the appropriate permissions. | | 403 | Forbidden | User does not have access to this resource. | Ensure that the user or access token has proper permissions set. | | 404 | Invalid resource identifier | The requested resource is not valid. | Ensure that the resource is correctly identified by id or key. | | 405 | Method not allowed | The request method is not allowed on this resource. | Ensure that the HTTP verb is correct. | | 409 | Conflict | The API request can not be completed because it conflicted with a concurrent API request. | Retry your request. | | 422 | Unprocessable entity | The API request can not be completed because the update description can not be understood. | Ensure that the request body is correct for the type of patch you are using (JSON patch or semantic patch). | 429 | Too many requests | Read [Rate limiting](/#section/Rate-limiting). | Wait and try again later. | ## CORS The LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. If an `Origin` header is given in a request, it will be echoed as an explicitly allowed origin. Otherwise, a wildcard is returned: `Access-Control-Allow-Origin: *`. For more information on CORS, see the [CORS W3C Recommendation](http://www.w3.org/TR/cors). Example CORS headers might look like: ```http Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization Access-Control-Allow-Methods: OPTIONS, GET, DELETE, PATCH Access-Control-Allow-Origin: * Access-Control-Max-Age: 300 ``` You can make authenticated CORS calls just as you would make same-origin calls, using either [token or session-based authentication](#section/Authentication). If you’re using session auth, you should set the `withCredentials` property for your `xhr` request to `true`. You should never expose your access tokens to untrusted users. ## Rate limiting We use several rate limiting strategies to ensure the availability of our APIs. Rate-limited calls to our APIs will return a `429` status code. Calls to our APIs will include headers indicating the current rate limit status. The specific headers returned depend on the API route being called. The limits differ based on the route, authentication mechanism, and other factors. Routes that are not rate limited may not contain any of the headers described below. > ### Rate limiting and SDKs > > LaunchDarkly SDKs are never rate limited and do not use the API endpoints defined here. LaunchDarkly uses a different set of approaches, including streaming/server-sent events and a global CDN, to ensure availability to the routes used by LaunchDarkly SDKs. ### Global rate limits Authenticated requests are subject to a global limit. This is the maximum number of calls that can be made to the API per ten seconds. All personal access tokens on the account share this limit, so exceeding the limit with one access token will impact other tokens. Calls that are subject to global rate limits will return the headers below: | Header name | Description | | ------------------------------ | -------------------------------------------------------------------------------- | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | We do not publicly document the specific number of calls that can be made globally. This limit may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limit. ### Route-level rate limits Some authenticated routes have custom rate limits. These also reset every ten seconds. Any access tokens hitting the same route share this limit, so exceeding the limit with one access token may impact other tokens. Calls that are subject to route-level rate limits will return the headers below: | Header name | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------- | | `X-Ratelimit-Route-Remaining` | The maximum number of requests to the current route the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset` | The time at which the current rate limit window resets in epoch milliseconds. | A _route_ represents a specific URL pattern and verb. For example, the [Delete environment](/tag/Environments#operation/deleteEnvironment) endpoint is considered a single route, and each call to delete an environment counts against your route-level rate limit for that route. We do not publicly document the specific number of calls that can be made to each endpoint per ten seconds. These limits may change, and we encourage clients to program against the specification, relying on the two headers defined above, rather than hardcoding to the current limits. ### IP-based rate limiting We also employ IP-based rate limiting on some API routes. If you hit an IP-based rate limit, your API response will include a `Retry-After` header indicating how long to wait before re-trying the call. Clients must wait at least `Retry-After` seconds before making additional calls to our API, and should employ jitter and backoff strategies to avoid triggering rate limits again. ## OpenAPI (Swagger) We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json) for our API. You can use this specification to generate client libraries to interact with our REST API in your language of choice. This specification is supported by several API-based tools such as Postman and Insomnia. In many cases, you can directly import our specification to ease use in navigating the APIs in the tooling. ## Client libraries We auto-generate multiple client libraries based on our OpenAPI specification. To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories). ## Method Overriding Some firewalls and HTTP clients restrict the use of verbs other than `GET` and `POST`. In those environments, our API endpoints that use `PUT`, `PATCH`, and `DELETE` verbs will be inaccessible. To avoid this issue, our API supports the `X-HTTP-Method-Override` header, allowing clients to \"tunnel\" `PUT`, `PATCH`, and `DELETE` requests via a `POST` request. For example, if you wish to call one of our `PATCH` resources via a `POST` request, you can include `X-HTTP-Method-Override:PATCH` as a header. ## Beta resources We sometimes release new API resources in **beta** status before we release them with general availability. Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible. We try to promote resources into general availability as quickly as possible. This happens after sufficient testing and when we're satisfied that we no longer need to make backwards-incompatible changes. We mark beta resources with a \"Beta\" callout in our documentation, pictured below: > ### This feature is in beta > > To use this feature, pass in a header including the `LD-API-Version` key with value set to `beta`. Use this header with each call. To learn more, read [Beta resources](/#section/Overview/Beta-resources). ### Using beta resources To use a beta resource, you must include a header in the request. If you call a beta resource without this header, you'll receive a `403` response. Use this header: ``` LD-API-Version: beta ``` ## Versioning We try hard to keep our REST API backwards compatible, but we occasionally have to make backwards-incompatible changes in the process of shipping new features. These breaking changes can cause unexpected behavior if you don't prepare for them accordingly. Updates to our REST API include support for the latest features in LaunchDarkly. We also release a new version of our REST API every time we make a breaking change. We provide simultaneous support for multiple API versions so you can migrate from your current API version to a new version at your own pace. ### Setting the API version per request You can set the API version on a specific request by sending an `LD-API-Version` header, as shown in the example below: ``` LD-API-Version: 20220603 ``` The header value is the version number of the API version you'd like to request. The number for each version corresponds to the date the version was released in yyyymmdd format. In the example above the version `20220603` corresponds to June 03, 2022. ### Setting the API version per access token When creating an access token, you must specify a specific version of the API to use. This ensures that integrations using this token cannot be broken by version changes. Tokens created before versioning was released have their version set to `20160426` (the version of the API that existed before versioning) so that they continue working the same way they did before versioning. If you would like to upgrade your integration to use a new API version, you can explicitly set the header described above. > ### Best practice: Set the header for every client or integration > > We recommend that you set the API version header explicitly in any client or integration you build. > > Only rely on the access token API version during manual testing. ### API version changelog |<div style=\"width:75px\">Version</div> | Changes | |---|---| | `20220603` | <ul><li>Changed the [list projects](tag/Projects#operation/getProjects) return value:<ul><li>Response is now paginated with a default limit of `20`.</li><li>Added support for filter and sort.</li><li>The project `environments` field is now expandable. This field is omitted by default.</li></ul></li><li>Changed the [get project](tag/Projects#operation/getProject) return value:<ul><li>The `environments` field is now expandable. This field is omitted by default.</li></ul></li></ul> | | `20210729` | <ul><li>Changed the [create approval request](/tag/Approvals#operation/postApprovalRequest) return value. It now returns HTTP Status Code `201` instead of `200`.</li><li> Changed the [get users](/tag/Users#operation/getUser) return value. It now returns a user record, not a user. </li><li> Added additional optional fields to environment, segments, flags, members, and segments, including the ability to create Big Segments. </li><li> Added default values for flag variations when new environments are created. </li><li> Added filtering and pagination for getting flags and members, including `limit`, `number`, `filter`, and `sort` query parameters. </li><li> Added endpoints for expiring user targets for flags and segments, scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions, and approvals. </li></ul> | | `20191212` | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags) now defaults to sending summaries of feature flag configurations, equivalent to setting the query parameter `summary=true`. Summaries omit flag targeting rules and individual user targets from the payload. </li><li> Added endpoints for flags, flag status, projects, environments, users, audit logs, members, users, custom roles, segments, usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial versioning of API. Tokens created before versioning have their version set to this.</li></ul> |
|
5
5
|
|
6
6
|
The version of the OpenAPI document: 2.0
|
7
7
|
Contact: support@launchdarkly.com
|
8
8
|
Generated by: https://openapi-generator.tech
|
9
|
-
OpenAPI Generator version:
|
9
|
+
OpenAPI Generator version: 6.0.0
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
@@ -95,7 +95,7 @@ module LaunchDarklyApi
|
|
95
95
|
end
|
96
96
|
|
97
97
|
# Get expiring user targets for segment
|
98
|
-
# Get a list of a segment's user targets that are scheduled for removal
|
98
|
+
# Get a list of a segment's user targets that are scheduled for removal.
|
99
99
|
# @param project_key [String] The project key
|
100
100
|
# @param environment_key [String] The environment key
|
101
101
|
# @param segment_key [String] The segment key
|
@@ -107,7 +107,7 @@ module LaunchDarklyApi
|
|
107
107
|
end
|
108
108
|
|
109
109
|
# Get expiring user targets for segment
|
110
|
-
# Get a list of a segment's user targets that are scheduled for removal
|
110
|
+
# Get a list of a segment's user targets that are scheduled for removal.
|
111
111
|
# @param project_key [String] The project key
|
112
112
|
# @param environment_key [String] The environment key
|
113
113
|
# @param segment_key [String] The segment key
|
@@ -170,7 +170,7 @@ module LaunchDarklyApi
|
|
170
170
|
end
|
171
171
|
|
172
172
|
# Get segment
|
173
|
-
# Get a single user segment by key
|
173
|
+
# Get a single user segment by key.
|
174
174
|
# @param project_key [String] The project key
|
175
175
|
# @param environment_key [String] The environment key
|
176
176
|
# @param segment_key [String] The segment key
|
@@ -182,7 +182,7 @@ module LaunchDarklyApi
|
|
182
182
|
end
|
183
183
|
|
184
184
|
# Get segment
|
185
|
-
# Get a single user segment by key
|
185
|
+
# Get a single user segment by key.
|
186
186
|
# @param project_key [String] The project key
|
187
187
|
# @param environment_key [String] The environment key
|
188
188
|
# @param segment_key [String] The segment key
|
@@ -245,7 +245,7 @@ module LaunchDarklyApi
|
|
245
245
|
end
|
246
246
|
|
247
247
|
# Get Big Segment membership for user
|
248
|
-
#
|
248
|
+
# Get the membership status (included/excluded) for a given user in this Big Segment. This operation does not support standard segments.
|
249
249
|
# @param project_key [String] The project key
|
250
250
|
# @param environment_key [String] The environment key
|
251
251
|
# @param segment_key [String] The segment key
|
@@ -258,7 +258,7 @@ module LaunchDarklyApi
|
|
258
258
|
end
|
259
259
|
|
260
260
|
# Get Big Segment membership for user
|
261
|
-
#
|
261
|
+
# Get the membership status (included/excluded) for a given user in this Big Segment. This operation does not support standard segments.
|
262
262
|
# @param project_key [String] The project key
|
263
263
|
# @param environment_key [String] The environment key
|
264
264
|
# @param segment_key [String] The segment key
|
@@ -326,7 +326,7 @@ module LaunchDarklyApi
|
|
326
326
|
end
|
327
327
|
|
328
328
|
# List segments
|
329
|
-
# Get a list of all user segments in the given project
|
329
|
+
# Get a list of all user segments in the given project.
|
330
330
|
# @param project_key [String] The project key
|
331
331
|
# @param environment_key [String] The environment key
|
332
332
|
# @param [Hash] opts the optional parameters
|
@@ -337,7 +337,7 @@ module LaunchDarklyApi
|
|
337
337
|
end
|
338
338
|
|
339
339
|
# List segments
|
340
|
-
# Get a list of all user segments in the given project
|
340
|
+
# Get a list of all user segments in the given project.
|
341
341
|
# @param project_key [String] The project key
|
342
342
|
# @param environment_key [String] The environment key
|
343
343
|
# @param [Hash] opts the optional parameters
|
@@ -395,7 +395,7 @@ module LaunchDarklyApi
|
|
395
395
|
end
|
396
396
|
|
397
397
|
# Update expiring user targets for segment
|
398
|
-
#
|
398
|
+
# Update expiring user targets for a segment. Updating a user target expiration uses the semantic patch format. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). If the request is well-formed but any of its instructions failed to process, this operation returns status code `200`. In this case, the response `errors` array will be non-empty. ### Instructions Semantic patch requests support the following `kind` instructions for updating user targets. #### addExpireUserTargetDate Schedules a date and time when LaunchDarkly will remove a user from segment targeting. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The date when the user should expire from the segment targeting, in Unix milliseconds. #### updateExpireUserTargetDate Updates the date and time when LaunchDarkly will remove a user from segment targeting. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The new date when the user should expire from the segment targeting, in Unix milliseconds. - `version`: The segment version. #### removeExpireUserTargetDate Removes the scheduled expiration for the user in the segment. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key.
|
399
399
|
# @param project_key [String] The project key
|
400
400
|
# @param environment_key [String] The environment key
|
401
401
|
# @param segment_key [String] The segment key
|
@@ -408,7 +408,7 @@ module LaunchDarklyApi
|
|
408
408
|
end
|
409
409
|
|
410
410
|
# Update expiring user targets for segment
|
411
|
-
#
|
411
|
+
# Update expiring user targets for a segment. Updating a user target expiration uses the semantic patch format. To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). If the request is well-formed but any of its instructions failed to process, this operation returns status code `200`. In this case, the response `errors` array will be non-empty. ### Instructions Semantic patch requests support the following `kind` instructions for updating user targets. #### addExpireUserTargetDate Schedules a date and time when LaunchDarkly will remove a user from segment targeting. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The date when the user should expire from the segment targeting, in Unix milliseconds. #### updateExpireUserTargetDate Updates the date and time when LaunchDarkly will remove a user from segment targeting. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The new date when the user should expire from the segment targeting, in Unix milliseconds. - `version`: The segment version. #### removeExpireUserTargetDate Removes the scheduled expiration for the user in the segment. ##### Parameters - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key.
|
412
412
|
# @param project_key [String] The project key
|
413
413
|
# @param environment_key [String] The environment key
|
414
414
|
# @param segment_key [String] The segment key
|
@@ -481,7 +481,7 @@ module LaunchDarklyApi
|
|
481
481
|
end
|
482
482
|
|
483
483
|
# Patch segment
|
484
|
-
# Update a user segment. The request body must be a valid
|
484
|
+
# Update a user segment. The request body must be a valid semantic patch, JSON patch, or JSON merge patch. ## Using semantic patches on a segment To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). The body of a semantic patch request for updating segments requires an `environmentKey` in addition to `instructions` and an optional `comment`. The body of the request takes the following properties: * `comment` (string): (Optional) A description of the update. * `environmentKey` (string): (Required) The key of the LaunchDarkly environment. * `instructions` (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a `kind` property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object. ### Instructions Semantic patch requests support the following `kind` instructions for updating segments. #### addIncludedUsers Adds user keys to the individual user targets included in the segment. Returns an error if this causes the same user key to be both included and excluded. ##### Parameters - `values`: List of user keys. #### addExcludedUsers Adds user keys to the individual user targets excluded from the segment. Returns an error if this causes the same user key to be both included and excluded. ##### Parameters - `values`: List of user keys. #### removeIncludedUsers Removes user keys from the individual user targets included in the segment. ##### Parameters - `values`: List of user keys. #### removeExcludedUsers Removes user keys from the individual user targets excluded from the segment. ##### Parameters - `values`: List of user keys. #### updateName Updates the name of the segment. ##### Parameters - `value`: Name of the segment. ## Using JSON patches on a segment You can also use JSON patch. To learn more, read [Updates using JSON patches](/reference#updates-using-json-patch). For example, to update the description for a segment, use the following request body: ```json { \"patch\": [ { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"new description\" } ] } ``` To update fields in the segment that are arrays, set the `path` to the name of the field and then append `/<array index>`. Using `/0` adds the new entry to the beginning of the array. For example, to add a rule to a segment, use the following request body: ```json { \"patch\":[ { \"op\": \"add\", \"path\": \"/rules/0\", \"value\": { \"clauses\": [{ \"attribute\": \"email\", \"op\": \"endsWith\", \"values\": [\".edu\"], \"negate\": false }] } } ] } ``` To add or remove users from segments, we recommend using semantic patch. Semantic patch for segments includes specific `instructions` for adding and removing both included and excluded users.
|
485
485
|
# @param project_key [String] The project key
|
486
486
|
# @param environment_key [String] The environment key
|
487
487
|
# @param segment_key [String] The segment key
|
@@ -494,7 +494,7 @@ module LaunchDarklyApi
|
|
494
494
|
end
|
495
495
|
|
496
496
|
# Patch segment
|
497
|
-
# Update a user segment. The request body must be a valid
|
497
|
+
# Update a user segment. The request body must be a valid semantic patch, JSON patch, or JSON merge patch. ## Using semantic patches on a segment To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch). The body of a semantic patch request for updating segments requires an `environmentKey` in addition to `instructions` and an optional `comment`. The body of the request takes the following properties: * `comment` (string): (Optional) A description of the update. * `environmentKey` (string): (Required) The key of the LaunchDarkly environment. * `instructions` (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a `kind` property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object. ### Instructions Semantic patch requests support the following `kind` instructions for updating segments. #### addIncludedUsers Adds user keys to the individual user targets included in the segment. Returns an error if this causes the same user key to be both included and excluded. ##### Parameters - `values`: List of user keys. #### addExcludedUsers Adds user keys to the individual user targets excluded from the segment. Returns an error if this causes the same user key to be both included and excluded. ##### Parameters - `values`: List of user keys. #### removeIncludedUsers Removes user keys from the individual user targets included in the segment. ##### Parameters - `values`: List of user keys. #### removeExcludedUsers Removes user keys from the individual user targets excluded from the segment. ##### Parameters - `values`: List of user keys. #### updateName Updates the name of the segment. ##### Parameters - `value`: Name of the segment. ## Using JSON patches on a segment You can also use JSON patch. To learn more, read [Updates using JSON patches](/reference#updates-using-json-patch). For example, to update the description for a segment, use the following request body: ```json { \"patch\": [ { \"op\": \"replace\", \"path\": \"/description\", \"value\": \"new description\" } ] } ``` To update fields in the segment that are arrays, set the `path` to the name of the field and then append `/<array index>`. Using `/0` adds the new entry to the beginning of the array. For example, to add a rule to a segment, use the following request body: ```json { \"patch\":[ { \"op\": \"add\", \"path\": \"/rules/0\", \"value\": { \"clauses\": [{ \"attribute\": \"email\", \"op\": \"endsWith\", \"values\": [\".edu\"], \"negate\": false }] } } ] } ``` To add or remove users from segments, we recommend using semantic patch. Semantic patch for segments includes specific `instructions` for adding and removing both included and excluded users.
|
498
498
|
# @param project_key [String] The project key
|
499
499
|
# @param environment_key [String] The environment key
|
500
500
|
# @param segment_key [String] The segment key
|
@@ -567,7 +567,7 @@ module LaunchDarklyApi
|
|
567
567
|
end
|
568
568
|
|
569
569
|
# Create segment
|
570
|
-
# Create a new user segment
|
570
|
+
# Create a new user segment.
|
571
571
|
# @param project_key [String] The project key
|
572
572
|
# @param environment_key [String] The environment key
|
573
573
|
# @param segment_body [SegmentBody]
|
@@ -579,7 +579,7 @@ module LaunchDarklyApi
|
|
579
579
|
end
|
580
580
|
|
581
581
|
# Create segment
|
582
|
-
# Create a new user segment
|
582
|
+
# Create a new user segment.
|
583
583
|
# @param project_key [String] The project key
|
584
584
|
# @param environment_key [String] The environment key
|
585
585
|
# @param segment_body [SegmentBody]
|
@@ -647,7 +647,7 @@ module LaunchDarklyApi
|
|
647
647
|
end
|
648
648
|
|
649
649
|
# Update targets on a Big Segment
|
650
|
-
# Update targets included or excluded in a Big Segment
|
650
|
+
# Update targets included or excluded in a Big Segment.
|
651
651
|
# @param project_key [String] The project key
|
652
652
|
# @param environment_key [String] The environment key
|
653
653
|
# @param segment_key [String] The segment key
|
@@ -660,7 +660,7 @@ module LaunchDarklyApi
|
|
660
660
|
end
|
661
661
|
|
662
662
|
# Update targets on a Big Segment
|
663
|
-
# Update targets included or excluded in a Big Segment
|
663
|
+
# Update targets included or excluded in a Big Segment.
|
664
664
|
# @param project_key [String] The project key
|
665
665
|
# @param environment_key [String] The environment key
|
666
666
|
# @param segment_key [String] The segment key
|