One or more exceptions found in the request or while processing the request.
Repeated from the ReportRequest. The service or instance of the service requesting the report.
Repeated from the ReportRequest. The customer whose usage is being reported.
Repeated from the ReportRequest. Defines the report being requested.
Date/time the response was created.
If the ReportRequest had an ID, return in this attribute.
Consumer of the service (client).
Identity of the customer for which data is requested.
Report parameters including report name, version, and filters (e.g., date ranges).
Date/time the request was created.
Identifier may be provided by client application for internal use/diagnostics.
Service consumer(client). Identifies the customer or 3rd party acting on behalf of customer.
Identifier by which the service (server) knows the service consumer (client). For some services this may be the same as the Customer ID.
Name of the requestor organization. (This is not the name of a person.)
Valid e-mail address that service can use to contact a human at the requestor organization.
Input arguments for the report.
Current filters include only the date ranges for the COUNTER usage reports.
The date range for the report. For COUNTER reports statistics are pulled by month; therefore, the date range should cover a range of months.
Report name. See http://www.niso.org/workrooms/sushi/reports for a list of registered report names and releases.
The release number corresponding to the COUNTER Code of Practice when the current definition of the report was introduced.
The Date Range Type made up of Begin and End dates. Note: COUNTER usage is only reported at the month level; therefore, this represents the range of months.
Beginning date of range formatted as "yyyy-mm-dd". Specify 'dd' as the first day of the month for COUNTER reports.
Ending date of range formatted as "yyyy-mm-dd". Specify 'dd' as the last day of the month for COUNTER reports.
A reference to a customer for which data is requested.
The Customer ID (usually proprietary) that the service uses to identify the customer. The value of this ID for a given organization will be different for each service.
Customer name
Service Exceptions
Error Number
Severity of the error.
Text describing the error.
URL describing error details.
Other optional data.
Service exception levels: Info, Debug, Warning, Error.
Info – type of severity that provides more information about the response. Can be included in a chain of other severity levels.
Debug – type of severity that provides debugging information about the response. Can be included in a chain of other severity levels.
Warning – type of severity that does not interrupt the completion of the transaction (defined as: request->data->response) but gives more information about the response. It could be followed by more exceptions (Info, Debug).
Error – type of severity that would return no payload. It could be followed by more exceptions (Info, Debug).
Fatal – type of severity that would return no payload. It could be followed by more exceptions (Info, Debug).