Page Comparison

Overview

Audience

Application Requirements

API Requirements

Getting Started

The easiest way to start learning about this interface is to try it out. This section shows how to use the curl command line tool to execute sample queries.

	curl -i -H "Accept: application/json" https://iet-ws-test.ucdavis.edu/api/iam/people/affiliations/1000000009?IAMId=1000000009&key=myKeyvmyKey&v=1.0

The response to all of the above requests have a Content-Type of text/javascript.  An example response for the the following the above request is shown below:

{
  "responseData" : {
    "results" : [
{
 "IAMIdiamId": "1234567890",
"isFacultyisEmployee": true,
"isHSEmployee": false,
"isStudentisFaculty": true,
"isStudent": false,
"isStaff": ""false
"isExternal": ""false



},
{ ...<More results>.... }
 ],
  "responseDetails" : null,
  "responseStatus" : 0
}

JSON Reference

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:

Request Format

URL Base Addresses

The following URL patterns are supported by the IAM Identity Store Core People API:

https://iet-ws.ucdavis.edu/api/iam/people/affiliations/{iamid}

https://iet-ws.ucdavis.edu/api/iam/people/search

URL Arguments

This section describes the arguments that can be used for search requests.

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

Required URL Arguments

The following table lists the required URL arguments.

Supported URL arguments

The following table lists the supported URL arguments for each supported URL pattern.

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 <INSERT LINK HERE>

Example search arguments:

Response Format

Each response follow this general format:

{
  "responseData" : {
    "results" : []
  },
  "responseDetails" : null | string-on-error,
  "responseStatus" : 0 | error-code
}

In the JSON fragment above, note that the responseData property contains a results array and an optional cursor.

Required URL Arguments 

Other Supported URL arguments

None.

Response Format

Results Array: Guaranteed Fields

The results array always contains the parameters listed in this section, even if the value is empty.

The responseStatus property contains a value of 0 on success and a custom error status code on failure. If there is a failure, responseDetails contains a diagnostic string.

Troubleshooting

If you encounter problems with your code:

• Make sure your API key is valid.
• Look for typos. Remember that JavaScript is a case-sensitive language.
• Use a JavaScript debugger. In Firefox, you can use the JavaScript console or the Firebug. In IE, you can use the Microsoft Script Debugger.
• If you need to examine the JSON string returned from the server, you can use JSON Lint to make a single, long string human readable.
• Email middleware-api@ucdavis.edu with a description of your problem and a trace of the request and response.

Response Codes and Messages

Troubleshooting