The IRWS v2 documentation is not exhaustive. Please contact  iam-support@uw.edu  if you have questions about v2 usage.

Overview

This guide describes the Identity Registration Web Service (IRWS) API V2.  IRWS v2 is deprecated and all new customers should use  IRWS v3  instead IRWS can be used to to register an identity with the Identity Registry.  IRWS offers a "RESTful" programmatic interface. It exposes Identity Registry source information as addressable resources via the uniform HTTP interface; authorized clients may retrieve (GET), create (PUT), update (POST) and delete (DELETE) representations of these resources through the REST API.

Request IRWS Access

IRWS v2 Swagger Documentation

Swagger documentation for IRWS v2 can be found at: Identity Registration Web Service REST API v2.

Requirements

The application that uses this service must support:

Base URL 

All interactions with IRWS are through the following base URLs. Customer testing is generally done in the Eval environment. The Dev environment is reserved for the IAM development team. 

Supported HTTP Request Headers

IRWS supports a set of standard and custom HTTP headers that can be used by a client to express options. All the listed request headers are optional and all can be combined.

Accept: [content type1,content type2, ...]

Act-As: application name

Application-Name: application/userid

Attribute-List: [attribute1 attribute2 attribute3 ...]

If-Match: [etag]

Option-List: [imprecise pretend pretty reflect]

Supported URI Parameters

HTTP headers are the preferred way for an application to express the IRWS options it needs. For convenience, some of the options described above can be communicated via parameters in the URI. This may be useful for user interactive testing with a browser or the curl utility. All parameters are optional and different options may be combined in one URI. Definitions are provided in the previous section. 

Resources

Identity records are associated with a resource. A GET on the base URL will return a list of all top-level resources for which your client is authorized. Documentation is provided for the resources listed in the table below.  

Return Codes

IRWS uses standard HTTP return codes, as well as a few special ones. Most errors will return a JSON payload with the error class containing the code and message properties.