Query parameters
The Pinned UI version of the Configuration resource to fetch.
Response
OK
Changes
Changed in 9 of the 51 revisions of this API.4916
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
/response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
/response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
/response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
/response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
the
response's property type changed fromobjectto no type for statusresponse-property-type-changed
- ▲
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
/response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
/response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
/response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
/response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
the
response's property type changed from no type toobjectfor statusresponse-property-type-changed
- ▲
- ▲
the
response's property format changed fromurito no format for statusresponse-property-type-changed
- ▲
the
response's property format changed fromurito no format for statusresponse-property-type-changed
- ▲
the
response's property format changed fromurito no format for statusresponse-property-type-changed
- ▲
the
response's property format changed fromurito no format for statusresponse-property-type-changed
- ▲
the
response's property format changed fromurito no format for statusresponse-property-type-changed
- ▲
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
- ○
api tag
FlexV1Configurationaddedapi-tag-added
- ○