Page Comparison

This documentation is intended for developers who wish to perform a basic search on the public data within the IAM system from within their application via the REST with JSON interface.

].






h2. Application requirements

Each request must provide a valid application key. You may sign up for your own application key here <INSERT LINK>.

{color:#002666}{*}Using the JSON interface{*}{color}

The easiest way to start learning about this interface is to try it out. This section shows how to use the&nbsp;curl&nbsp;command line tool to execute sample queries.
{code:title=Sample JSON Requests}{code} Attach this curl command to the beginning of any of the below sample requests:

	curl -i -H "Accept: application/json"



 People API

	https://iet-ws-test.ucdavis.edu/api/iam/people/search?firstName=Gary&lastName=Sharpe&key=myKeyv&v=1.0


 DisplayName API

	https://iet-ws-test.ucdavis.edu/api/iam/people/displayname/{iamid}?key=myKeyv&v=1.0


 SystemIds API

	https://iet-ws-test.ucdavis.edu/api/iam/people/systemids/{iamid}?key=myKeyv&v=1.0
	https://iet-ws-test.ucdavis.edu/api/iam/people/systemids/search?mothraId=1111111&key=myKeyv&v=1.0


 Affiliations API

	https://iet-ws-test.ucdavis.edu/api/iam/people/affiliations/{iamid}?key=myKeyv&v=1.0
	https://iet-ws-test.ucdavis.edu/api/iam/people/affiliations/isfaculty?key=myKeyv&v=1.0



 PriKerberosAccount

	https://iet-ws-test.ucdavis.edu/api/iam/people/prikerbacct/{iamid}&key=myKeyv&v=1.0



The response to all of the above requests

{code}


h3. JSON reference


h2.

{color:#000000}Unlike the core JavaScript interface, the JSON interface is exposed through a uniform URL that contains CGI arguments. Your application can use an HTTP stack of its choosing. In order to use the JSON interface:{color}
* You must construct a properly formatted URL with all necessary CGI arguments.
* You must send an HTTP referer header that accurately identifies your application.
* You must process the JSON-encoded response.

h3. Request format

h4. {color:#003366}{*}URL base address{*}{color}

The standard URLs for the IAM Identity Store People APIs varies based on exactly which API is invoked.  The details are provided in documentation about each individual API.

h4. URL arguments

This section provides examples of the kinds of arguments that can be used with the People APIs

The value of a CGI argument must always be properly escaped. This can be done via the functional equivalent of JavaScript's encodeURIComponent() method.

h5. Required URL arguments

The following table lists the required URL arguments.
|| *Argument* || *Example* || *Description* ||
| key | key=your-key | This argument supplies the application's key. You can sign up for an API key <INSERT LINK HERE>. \\
It must be a valid key associated with your application. The key is required for this API to implement quality of service rules for this API. If your application is making too many requests it will be throttled to ensure resources are not overloaded during times of peak usage. Also, by supplying a key we can identify and contact you should something go wrong with your application. |
| v | v=1.0 | This argument supplies protocol version number. The only valid value at this point in time is&nbsp;1.0. |

h5. Search URL arguments

The following table lists the possible search query URL arguments. At least one argument should be provided to perform a search. If multiple search criteria are provided an *'AND'* search will be performed to match on all arguments.

*Wildcard Searches*: Any argument may use a wildcard within the query value. You may use multiple wildcards in any position in the search criteria. See examples below.\*

Example search arguments:

{code:title=Search for anyone with last name of 'Bray'}/api/directory/search?sn=Bray&key=myKeyv&v=1.0

{code}

{code:title=Search for anyone with first name of 'Curtis' and last name starting with 'B'

}/api/directory/search?givenName=Curtis&sn=B*&key=myKeyv&v=1.0

{code}

{code:title=Search for anyone with a displayName that starts with 'J' and ends with 'Jones'}/api/directory/search?displayName=J*Jones&key=myKey&v=1.0

{code}


h5. Response format

Each response follow this general format:
{code:lang=xml}
{
  "responseData" : {
    "results" : []
  },
  "responseDetails" : null | string-on-error,
  "responseStatus" : 0 | error-code
}
{code}


In the JSON fragment above, note