# OpenAM Administration Guide
Chapter 7. Working with Mobile Devices & Applications

Sidebar | Prev | Up | Next

## 7.3. Simplifying Access with REST APIs

Representational State Transfer (REST) is a architectural style designed in parallel with HTTP. REST simplifies integration and deployment while enabling layered, web-scale services. REST APIs in OpenAM implement REST in a way that reuses common HTTP verbs and decouples APIs from the programming languages that developers use to interact with them. OpenAM exposes REST APIs for many capabilities such as those in the following list.

- Authentication (including a callback mechanism so applications can work with all OpenAM authentication modules)

- Logout

- Managing groups

- Managing policy agent profiles

- Managing realms

- Managing user profiles

- OAuth 2.0 authorization

- OpenAM native authorization

- OpenID Connect 1.0 authorization

- Resetting forgotten passwords

- Token validation

- User self-registration

[D]

As OpenAM REST APIs provide language-independent access, they make it easier to build cross-device applications. Developers can use the same APIs to access OpenAM both from web applications and also from native mobile applications.

Furthermore OpenAM REST APIs are built on an underlying common REST framework, designed to provide common access to resource providers. The common REST framework standardizes both how resource providers serve standard requests (create, read, update, delete, query, patch), and also how resource providers offer extended operations in a managed way (using actions). Applications built to interact with OpenAM REST APIs increasingly can interoperate with other products in the Open Identity Platform stack such as OpenIDM for identity management and OpenDJ for highly available data.