Enhanced feature flag revisions

Enhanced feature flag revisions aren't available in this API version.

An enhanced feature flag revision defines the historical representation of an enhanced feature flag resource. Revisions expire after 7 days for Free and Developer tier stores, or 30 days for Standard and Premium tier stores. Revisions support the List operation.

For all operations, name is an optional parameter. If omitted, it implies any feature flag name.

For all operations, label is an optional parameter. If omitted, it implies any label.

Prerequisites

• All HTTP requests must be authenticated. See the authentication section.
• All HTTP requests must provide explicit api-version. See the versioning section.

List revisions

Optional: name (If not specified, it implies any feature flag name.)

Optional: label (If not specified, it implies any label.)

Optional: tags (If not specified, it implies any tags.)

Optional request header: Sync-Token (Used to guarantee real-time consistency between requests.)

GET /ff-revisions?name={name}&label={label}&tags={tagFilter1}&tags={tagFilter2}&api-version={api-version} HTTP/1.1

Responses:

HTTP/1.1 200 OK
Content-Type: application/json; profile="https://azconfig.io/mime-profiles/ffset"; charset=utf-8
ETag: "1PlB48ET4VAlB9068ft6fKMyA3m"
Sync-Token: zAJw6V16=NjotMSM3ODk3NjM=;sn=789763

{
  "items": [
    {
      "etag": "0BGYCoQ6iNdp5NtQ7N8shrobo6s",
      "name": "{name}",
      "enabled": false,
      "label": "{label}",
      "tags": {
        "t1": "value1"
      },
      "last_modified": "2026-04-30T16:52:32Z"
    },
    ...
  ],
  "@nextLink": "{relative uri}"
}

List revisions (conditionally)

To improve client caching, use If-Match or If-None-Match request headers. The etag argument is part of the list response body and header. If both headers are omitted, the operation is unconditional.

The following request gets revisions only if the current representation matches the specified etag:

GET /ff-revisions?name={name}&label={label}&api-version={api-version} HTTP/1.1
If-Match: "{etag}"

Responses:

HTTP/1.1 412 Precondition Failed

or

HTTP/1.1 200 OK

The following request gets revisions only if the current representation doesn't match the specified etag:

GET /ff-revisions?name={name}&label={label}&api-version={api-version} HTTP/1.1
If-None-Match: "{etag}"

Responses:

HTTP/1.1 304 Not Modified

or

HTTP/1.1 200 OK

Pagination

The result is paginated if the number of items returned exceeds the response limit. Follow the URI in the @nextLink property to request the next page. The linked URI includes the After continuation token and the api-version argument. Don't decode or construct the After token.

GET /ff-revisions?api-version={api-version} HTTP/1.1

Response:

HTTP/1.1 200 OK
Content-Type: application/json; profile="https://azconfig.io/mime-profiles/ffset"; charset=utf-8

{
  "items": [
    ...
  ],
  "@nextLink": "{relative uri}"
}

Filtering

A combination of name, label, and tags filtering is supported. Use the optional name, label, and tags query string parameters. Multiple tag filters can be provided as query string parameters in the tagName=tagValue format. Tag filters must be an exact match.

GET /ff-revisions?name={name}&label={label}&tags={tagFilter1}&tags={tagFilter2}&api-version={api-version}

Supported filters

Reserved characters

The reserved characters are:

*, \, ,

If a reserved character is part of the value, then it must be escaped by using \{Reserved Character}. Non-reserved characters can also be escaped.

Filter validation

If a filter validation error occurs, the response is HTTP 400 with error details:

HTTP/1.1 400 Bad Request
Content-Type: application/problem+json; charset=utf-8

{
  "type": "https://azconfig.io/errors/invalid-argument",
  "title": "Invalid request parameter '{filter}'",
  "name": "{filter}",
  "detail": "{filter}(2): Invalid character",
  "status": 400
}

Examples

• All revisions

  GET /ff-revisions?api-version={api-version}
  

• Revisions where the feature flag name starts with abc

  GET /ff-revisions?name=abc*&api-version={api-version}
  

• Revisions where the feature flag name is either abc or xyz, and labels contain prod

  GET /ff-revisions?name=abc,xyz&label=*prod*&api-version={api-version}
  

Request specific fields

Use the optional $select query string parameter and provide a comma-separated list of requested fields. If the $select parameter is omitted, the response contains the default set. Supported fields are name, enabled, label, description, conditions, variants, allocation, telemetry, tags, last_modified, and etag.

GET /ff-revisions?$select=enabled,label,last_modified&api-version={api-version} HTTP/1.1

For information about request and response headers shared by App Configuration data-plane operations, see Common headers.