Page Comparison

Application requirements

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

Using the JSON interface

Section

Column

width	20%

Panel

borderColor	#BF9900
bgColor	#FFFFFF
titleBGColor	#E5D699
borderStyle	solid
title	In this Section

Table of Contents

indent	15px
style	none

Column

Overview

Application Requirements

Include Page

	API 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.

NOTE: Details about each API and the available commands are available in separate documents for each individual API. See links above.

Requests

Code Block

title	Sample JSON

Attach this curl command to the beginning of any of the below sample requests:

Request

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

PPS Departments API

https://iet-ws

-test

.ucdavis.edu/api/iam/orginfo/

ppsdepts/{deptcode}?key=myKeyv&v=1.0 PPS Titles API https://iet-ws-test.ucdavis.edu/api/iam/orginfo/ppstitles/{titlecode}?key=myKeyv&v=1.0 https://iet-ws-test.ucdavis.edu/api/iam/orginfo/ppstitles/search?deptDisplayName=Information*&key=myKeyv

pps/depts/search?deptCode=061419&key=myKey&v=1.0

The response to all of the above requests have a Content-Type of text/javascript. An example response for the

...

above request is shown below:

curl -i -H "Accept: application/json" <INSERT URL HERE>

Code Block

lang	xml
title	Sample JSON Response

responseData

reponseData"

:
{

"results"

:
[

""

orgOId:

 "F80B657CA1F923A0E0340003BA8A560D",

""

deptCode:

 "929879",
deptOfficialName: "

"

MARKET

:

RESEARCH"

"

,
deptDisplayName: "

"

UCDHS:MARKET RESEARCH"

"

""

deptAbbrev:

 "UCDMC",

""

isUCDHS: true,
bouOrgOId: "F80B657C9EF423A0E0340003BA8A560D",

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

createDate: "2010-07-13 12:59:02",
modifyDate: "2013-01-28 15:37:27"
}]},
"responseDetails":"",
"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:

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.

Request

...

Format

URL

...

Base Addresses

The

...

following URL patterns are supported by the IAM Identity Store

...

Core People API:

Code Block

lang	xml
title	Supported URL Patterns

https://iet-ws.ucdavis.edu/api/

...

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.

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 1.0.

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 Block

title	Search for anyone with first name of 'Curtis' and last name starting with 'B'

/api/orginfo/ppstitles/search?titleDisplayName=Programmer*&key=myKeyv&v=1.0

Code Block

title	Search for anyone with a displayName that starts with 'J' and ends with 'Jones'

/api/orginfo/search?deptDisplayName=___*_____key=myKey&v=1.0

Response format

Each response follow this general format:

Code Block

lang	xml


{
  "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.

Trouble shooting

If you encounter problems with your code:

...

iam/orginfo/pps/depts
https://iet-ws.ucdavis.edu/api/iam/orginfo/pps/depts/search

URL Arguments

Include Page

	URL Arguments
	URL Arguments

Required URL Arguments

Include Page

	Required URL Arguments
	Required URL Arguments

Supported URL arguments

Include Page

	Supported URL Arguments
	Supported URL Arguments

URL	Supported Arguments
https://iet-ws.ucdavis.edu/api/iam/orginfo/pps/depts/search	orgOId deptCode

Response Format

Include Page

	Response Format for IET-WS APIs
	Response Format for IET-WS APIs

Results Array: Guaranteed Fields

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

Property	Description
orgOId	Unique IAM guid for this PPS department
deptCode	PPS unique deptcode
deptOfficialName	The official name for this department
deptDisplayName	The display name for this department
deptAbbrev	The abbreviation for this department
isUCDHS	true/false, is the department an UCDHS department
bouOrgOId	Unique IAM guid for the parent BOU department
createDate	The date this record was created in the IAM system.
modifyDate	The last date this record was modified in the IAM system.
results[]	results[] contains an array of bulk load result objects, one for each result. Each time the API executes, this property is cleared, and each time a API completes, the array is populated. If there are no results to report, the .length property of this array will be set to 0. Therefore, results will never be null, and you can always safely check for results.length == 0.

Response Codes and Messages

Include Page

	Response Codes and Messages
	Response Codes and Messages

Troubleshooting

Include Page

	Troubleshooting IET-WS APIs
	Troubleshooting IET-WS APIs

Column

Section

Versions Compared

Old Version 1

New Version Current

Key

Application requirements

Overview

Application Requirements

Getting Started

JSON

Reference

Request

Format

URL

Base Addresses

URL arguments

Required URL arguments

Search URL arguments

Response format

Trouble shooting

URL Arguments

Required URL Arguments

Supported URL arguments

Response Format

Results Array: Guaranteed Fields

Response Codes and Messages

Troubleshooting