Run report
POST/reports/run_report
Run a report and get the output.
In order to run a report, you must either be the owner of the report,
or have the the Authority - Administrator ability, or have
certain other conditions apply such as Timekeeping or Approver
authority over the user.
In addition, the actual data you see in the report can vary depending on the report settings and your current access permissions such as group memberships.
This endpoint does not necessarily follow the
standard REST conventions. In particular, it uses the POST
method for operations that would typically use GET, PUT or DELETE in a
RESTful API endpoint.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
- 503
The response object for a report run.
Note that not all of these keys will be present in all responses, depending on the report type.
The core data of the report is usually under the following key:
results > data > report_desc > items
This will be an array of objects, either subtotal objects or individual data objects (rows), depending on the report type and options. The base row objects usually have keys that correspond to the fields listed in:
results > data > report_desc > fields
A 400 Bad Request is returned when the client request was malformed,
invalid, or otherwise could not be processed as-is. Usually, the cause for
the error is included in the error.message field of the response, and the
client should correct the request and try again.
See also Core Concepts#Error Responses.
Not authenticated - you must be signed in to access this resource. Please check the section of the documentation on authentication.
A 403 Forbidden response means that you are not authorized to perform
this action or access this object, or the object does not exist at all.
The client request may have been valid but the client does not have permission to access the requested resource or perform the requested action.
:::tip 403 Forbidden also used when objects don't exist
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
:::
See also Core Concepts#Error Responses.
Not found - the requested resource could not be found or does not exist. This may also include cases where the resource does exist, but the client does not have permission to access that resource.
:::tip 403 Forbidden also used when objects don't exist
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
:::
See also Core Concepts#Error Responses.
Internal server error; an unexpected error occurred on the server. This could be due to a temporary condition or might be the result of a bug in the server software. Also, in some cases, an incorrect client input can trigger this error, and can be resolved by correcting the input.
If the error persists, please contact support along along with the following details when possible:
- any error messages received from the server
- the full request and response details (full headers and body)
- a description of the steps that led to the error
- the time range when it occurred.
Service unavailable - the server is currently unable to handle the request, usually due to maintenance activity on the server. Check if the server's web interface is currently available, or try again later.