Export of saved report views

You use the GET operation on the api/reports/report_ID element to export a saved report view which can be then imported to another instance of BigFix Inventory.

Table 1. Operation descriptions
Operation details Description
Operation GET /api/reports/report_ID
Purpose Returns the saved report view with the specified ID.
HTTP method GET
Resource URI https://server_host_name:port_number/api/reports/report_ID
URL link relation n/a
URI query parameters For a list of applicable query parameters, see: Query parameters.
Request headers
Accept-Language (optional)
en-US (only English is supported)

Used to negotiate the language of the response. If this header is not specified, the content is returned in the server language.

Request payload n/a
Request Content-Type
  • Application/json
Response headers

Specifies the content type of the response.

en-US, …

Specifies the language of the response content. If this header is not specified, the content is returned in the server language.

Response payload Saved reports element
Response Content-Type
  • Application/json
Normal HTTP response codes
  • 200 – OK
Error HTTP response codes
  • 401- There is no match for the provided user name and password
  • 401 - You are not assigned a Computer Group. You will not be able to access the system until you are assigned a valid Computer Group. Contact your administrator for assistance
  • 404 - Sequel::RecordNotFound

For more details about each error code, check the tema.log log file in the install_dir/wlp/usr/servers/server1/logs/ directory.

Query parameters

You can use query parameters to narrow down the results of your search. The following table presents query parameters that you can use for the api/reports element.
Table 2. Query parameters for retrieving saved report views
Parameter Description Required Value
token A unique user authentication identifier. Yes Alphanumeric
id An identifier of the saved report. To find the report identifier, open the saved report and check the last number in the report URL. In the following example, the report ID is 3.
No Numeric

Example HTTP conversation

Response header
HTTP/1.1 200 OK
Content-Type: Application/json
Content-Language: en-US
Response body (JSON)