Introduction
REST API v1 JAX-RS resource classes. Each class implements a service endpoint.
REST Resources
This API supports a Representational State Transfer (REST) model for accessing a set of resources through a fixed set of operations. The following resources are accessible through the RESTful model:
- /actions
- /actions/{id}
- /actions/customfilter
- /actions/includes
- /applicationgroups
- /applicationgroups/{id}
- /applicationgroups/applicationgroupsearch
- /applicationgroups/customfilter
- /applicationgroups/includes
- /applications
- /applications/{id}
- /applications/{id}/consents
- /applications/{id}/resetClientSecret
- /applications/customfilter
- /applications/includes
- /authorization
- /brokerstore
- /claimsmaps
- /claimsmaps/{id}
- /claimsmaps/customfilter
- /claimsmaps/includes
- /consents/{ownerCompositeKey}
- /consents/{ownerCompositeKey}/applications/{applicationId}
- /consents/{ownerCompositeKey}/applications/{applicationId}/purpose/{purposeId}
- /consents/{ownerCompositeKey}/applications/{applicationId}/purpose/{purposeId}/resource/{resourceId}
- /consents/{ownerCompositeKey}/applications/{applicationId}/resource/{resourceId}
- /consents/{ownerCompositeKey}/consented/applications
- /consents/{ownerCompositeKey}/consented/resources
- /consents/{ownerCompositeKey}/purpose/{purposeId}
- /consents/{ownerCompositeKey}/resources/{resourceId}
- /consents/self/applications/{applicationId}
- /consents/self/consented/applications
- /consents/self/consented/resources
- /consents/self/resources/{resourceId}
- /dataviews
- /dataviews/{name}
- /dataviewschemas
- /dataviewschemas/{id}
- /dataviewschemas/customfilter
- /dataviewschemas/includes
- /histories/{ownerCompositeKey}
- /histories/{ownerCompositeKey}/accessHistory
- /policies
- /policies/{id}
- /policies/{id}/policysets
- /policies/customfilter
- /policies/includes
- /policysets
- /policysets/{id}
- /policysets/customfilter
- /policysets/includes
- /purposes
- /purposes/{id}
- /purposes/customfilter
- /purposes/includes
- /requests
- /requests/{id}
- /resourceAliases
- /resourceAliases/{id}
- /resourceAliases/aliassearch
- /resourceAliases/customfilter
- /resourceAliases/includes
- /resourcegroups
- /resourcegroups/{id}
- /resourcegroups/customfilter
- /resourcegroups/includes
- /resourcegroups/resourcegroupsearch
- /resourcegroups/urnsearch
- /resources
- /resources/{id}
- /resources/customfilter
- /resources/includes
- /resources/urnsearch
- /sandboxes
- /sandboxes/{id}
- /sandboxes/customfilter
- /sandboxes/includes
- /scopes
- /scopes/{id}
- /scopes/customfilter
- /scopes/includes
- /storeadapterdata
- /storeadapterdata/{id}
- /storeadapterdata/customfilter
- /storeadapterdata/includes
- /tags
- /tags/{id}
- /tags/customfilter
- /tags/includes
- /templates
- /templates/{id}
- /templates/{id}/policies
- /templates/{templateId}/{policyId}
- /templates/customfilter
- /templates/includes
- /tracefilters
- /tracefilters/{id}
- /trustlevels
- /trustlevels/{id}
- /trustlevels/customfilter
- /trustlevels/includes
Data Model
All endpoints act on a common set of data. The data can be represented with difference media (i.e. "MIME") types, depending on the endpoint that consumes and/or produces the data. The data is described by JSON, which definitively describes the representation of the data.
This document will describe the data using terms based on JSON serialization. Data can be grouped by namespace, with a document describing the elements and types of the namespace. Generally speaking, types define the structure of the data and elements are instances of a type. For example, elements are usually produced by (or consumed by) a REST endpoint, and the structure of each element is described by its type.