Common Elements in Service Operations Requests

The following guidelines apply across all QAS requests:

• All SOAP based requests should contain a SOAP header containing user ID and password.

  All RESTful based requests should contain HTTP Authorization Header for basic authentication. For example, Authorization: Basic"dXNlcjpwYXNzd29yZA==" , where sequence of characters following Basic is the Base64 encoded form of string "username:password".

• All search strings use the Begins with criterion.

• Parameters are case-insensitive, unless specifically noted or specific enumeration values are listed.

• All elements are required, unless specifically noted. Even if no value is necessary, the element must be included in the request.

• Values are required in the element, unless specifically noted.

• Leading and trailing blanks are not allowed in XML values.

Note:

All examples are shown without the SOAP header. For information about the SOAP header, refer to “Accessing PeopleSoft Application Tables.”

Note:

RESTful Get requests made from an Internet browser will generate a prompt for PeopleSoft logon credentials. Requests made from a client application however,(including Delete and Post requests), will need to provide the "Authorization" HTTP header for basic authentication.