Featureflip User Segments API
User segments within a resolved organization + project — mirrorsEnvironmentsController's resolve-then-dispatch shape one level deeper.`{project}` is resolved key-or-guid, scoped to the resolved org (with the service-tokenproject allowlist forwarded), via ResolveProjectIdAsyncfor every action. `{segment}` (get/update/delete) is then resolved key-or-guid, scoped tothe resolved project, via ResolveSegmentIdAsync.Dispatched commands/queries always use the resolved GUIDs, never the raw route strings. Writes(create/update/delete) require at least Member(RequireRole); a Viewer attempting one gets a 403`forbidden` envelope.There is no `GetUserSegmentQuery` — Get resolves `{segment}` thendispatches ListUserSegmentsQuery and finds the match in-memory, throwingNotFoundException if absent. This keeps the task scoped to the public layer withno new Application handler: the resolver has already validated the id exists within theproject, and a project's segment set is bounded (unlike flags/environments' own list, thisnever needs true server-side pagination for the lookup).Operator is a bare string on the wire; write actionsparse it to OperatorType via TryParse``1(ReadOnlySpan{Char},Boolean,``0@)(case-insensitive). An unrecognized value throws the customValidationException BEFORE any command is dispatched — mapped to a 400`validation_failed` envelope by PublicApiExceptionFilterAttribute, same asevery other handler-thrown validation failure on this surface.
Featureflip User Segments API is one of 10 APIs that Featureflip publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include User Segments. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 5 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://api.featureflip.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Featureflip User Segments API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (Bearer).
By default, every request must be authenticated.
Bearer— JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token in the text input below.
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
User segments within a resolved organization + project — mirrors EnvironmentsController's resolve-then-dispatch shape one level deeper.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PublicSegmentResponse (8 properties), PublicApiErrorEnvelope (7 properties), PublicCreateSegmentRequest (4 properties), PublicSegmentConditionDto (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Featureflip 9
Other APIs Featureflip publishes across the network.
This is an independent, third-party profile of Featureflip User Segments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.