# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand. overlay: 1.0.0 info: title: API Evangelist conversational phrasing for Flagsmith Other API version: 1.0.0 extends: openapi/flagsmith-other-api-openapi.yml actions: - target: $.info update: x-apievangelist-phrasing: method: generated generated: '2026-09-26' generator: build-phrasing.py label: Generated by API Evangelist operations: 6 - target: $.paths['/api/v1/cohort-sync/amplitude/lists/'].post update: x-apievangelist-phrasing: intent: Create a cohort list for an Amplitude cohort sync effect: write questions: - How does an Amplitude cohort sync get a list ID in Flagsmith when it is first set up? - What happens on the Flagsmith side when a new Amplitude cohort sync is configured? instructions: - text: Create a backing cohort list named {name} for the Amplitude cohort sync. slots: name: requestBody.name - text: Set up a new Amplitude cohort sync list called {name} and return its list ID. slots: name: requestBody.name method: generated generated: '2026-09-26' - target: $.paths['/api/v1/cohort-sync/amplitude/lists/{id}/add/'].post update: x-apievangelist-phrasing: intent: Add users to a synced Amplitude cohort list effect: write questions: - How do users get added to a cohort that is synced from Amplitude? - Can I push a batch of user IDs into an existing Amplitude cohort list? instructions: - text: Add users {user_ids} to Amplitude cohort list {id}. slots: user_ids: requestBody.user_ids id: path.id - text: Put these user IDs {user_ids} into the synced cohort {id}. slots: user_ids: requestBody.user_ids id: path.id method: generated generated: '2026-09-26' - target: $.paths['/api/v1/cohort-sync/amplitude/lists/{id}/remove/'].post update: x-apievangelist-phrasing: intent: Remove users from a synced Amplitude cohort list effect: write questions: - How are users taken out of a cohort that is synced from Amplitude? - Can I drop specific user IDs from an Amplitude cohort list? instructions: - text: Remove users {user_ids} from Amplitude cohort list {id}. slots: user_ids: requestBody.user_ids id: path.id - text: Take these user IDs {user_ids} out of the synced cohort {id}. slots: user_ids: requestBody.user_ids id: path.id method: generated generated: '2026-09-26' - target: $.paths['/api/v1/gitlab-webhook/{webhook_uuid}/'].post update: x-apievangelist-phrasing: intent: Receive a GitLab webhook event effect: write questions: - Where does GitLab send webhook events for the Flagsmith GitLab integration? - What URL receives incoming GitLab webhook deliveries for a configured integration? instructions: - text: Deliver a GitLab webhook event to the Flagsmith webhook {webhook_uuid}. slots: webhook_uuid: path.webhook_uuid - text: Post this GitLab event payload to webhook receiver {webhook_uuid}. slots: webhook_uuid: path.webhook_uuid method: generated generated: '2026-09-26' - target: $.paths['/api/v1/oauth/authorize/'].get update: x-apievangelist-phrasing: intent: Validate an OAuth authorisation request effect: read questions: - How do I check that an OAuth authorisation request is valid before showing a consent screen? - Which application is asking for access in an OAuth authorisation request? instructions: - text: Validate the incoming OAuth authorisation request and show me the requesting application's details. - text: Look up the app info for the pending OAuth authorisation request. method: generated generated: '2026-09-26' - target: $.paths['/api/v1/oauth/authorize/'].post update: x-apievangelist-phrasing: intent: Submit an OAuth consent decision effect: write questions: - How do I record a user's approval or denial on the OAuth consent screen? - What redirect URI comes back after an OAuth consent decision is submitted? instructions: - text: Submit the user's OAuth consent decision and return the redirect URI. - text: Process the consent choice for this OAuth authorisation and give me where to redirect. method: generated generated: '2026-09-26'