OverviewAPI Requirements| Include Page |
|---|
| IETP:API Requirements |
|---|
| IETP:API Requirements |
|---|
|
Getting StartedThe 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. | Code Block |
|---|
| curl -i -H "Accept: application/json" https://iet-ws-test.ucdavis.edu/api/iam/people/prikerbacct/1000000009?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: | Code Block |
|---|
| lang | xml |
|---|
| title | Sample JSON Response |
|---|
|
{
"responseData" : {
"results" : [
{
"iamId": "",
"userId": "",
"uuId" : "",
"createDate": "",
"claimDate": "",
"expireDate": ""
},
{ ...<More results>.... }
],
"responseDetails" : null,
"responseStatus" : 0
}
|
JSON Reference| Include Page |
|---|
| IETP:JSON Reference |
|---|
| IETP:JSON Reference |
|---|
|
URL Base AddressesThe 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/iam/people/prikerbacct/{iamid}
|
URL ArgumentsThis 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 ArgumentsThe 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. |
Supported URL argumentsThe 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.| Include Page |
|---|
| IETP:URL Arguments |
|---|
| IETP:URL Arguments |
|---|
|
Required URL Arguments| Include Page |
|---|
| IETP:Required URL Arguments |
|---|
| IETP:Required URL Arguments |
|---|
|
Supported URL arguments| Include Page |
|---|
| IETP:Supported URL Arguments |
|---|
| IETP:Supported URL Arguments |
|---|
|
| Include Page |
|---|
| IETP:Response Format for IET-WS APIs |
|---|
| IETP:Response Format for IET-WS APIs |
|---|
|
Results Array: guaranteed fieldsThe results array always contains the parameters listed in this section, even if the value is empty. Property | Description |
|---|
iamId | Unique University ID created by IAM system. Replaces MOTHRAID. | userId | Kerberos loginid
| uuId | UNIX UID
| createDate | Date this account was created | claimDate | Date this account was claimed by the end user | expireDate | Date the account expired or was disabled | 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. |
'responseStatus' Codes and 'responseDetails' Messages| Include Page |
|---|
| IETP:'responseStatus' Codes and 'responseDetails' Messages |
|---|
| IETP:'responseStatus' Codes and 'responseDetails' Messages |
|---|
|
Troubleshooting| Include Page |
|---|
| IETP:Troubleshooting IET-WS APIs |
|---|
| IETP:Troubleshooting IET-WS APIs |
|---|
|
|