The list of Reports service links.
Reports
Loading...
You can use the Reports API to create, read, and update reports. This API enables basic tasks such as moving or renaming reports, as well as editorial tasks such as reading, writing, and updating report content.
head
Internal-Use OnlyRetrieves header information for the service. It can also be used to verify that the service is available.Get header information for the service
get
Internal-Use OnlyReturns a collection of links to the top-level collections surfaced through this API.Get a collection of top-level links
The operations for the report resource.
get
Internal-Use OnlyReturns a collection of reports with standard paging, filtering, and sorting options.Get a collection of reports
post
Internal-Use OnlyCreates a new report and adds it to a folder as a child.Create report
head
Internal-Use OnlyReturns the headers for a report, including ETag. See Conditional Operations.Check report status
get
Internal-Use OnlyReturns the specified report, including ETag header. See Conditional Operations.Get a report
head
Internal-Use OnlyReturns the headers for a report resource summary, including modifiedTimeStamp.Check report resource summary status
get
Internal-Use OnlyReturns the specified report in resource summary format.Get resource summary report
delete
Internal-Use OnlyDeletes the specified report and its content. Remove the report from the parent folder.Delete a report
put
Internal-Use OnlyUpdates the specified report. Requires an If-Match or If-Unmodified-Since request header. See Conditional Operations.Update a report
post
Internal-Use OnlyEnsures that the name does not exceed the maximum length and, if parentFolderUri is provided, that a report with the name can be added as a member without conflict. The validation does not check whether or not the user can actually add a report with the given name to the folder.Validate report name
The operations for the report content resource.
head
Internal-Use OnlyReturns the headers for report content, including the ETag. See Conditional Operations.Check status of report content
get
Internal-Use OnlyReturns the report content, including ETag. See Conditional Operations.Get report content
put
Internal-Use OnlySaves the report content. Does not return the stored content. An ETag is not required for the initial save, but is required for all subsequent saves. In some situations, where an Accept type header is automatically generated, setting it to '*/*' will achieve the same effect as omitting it. See Conditional Operations.Save report content
put
Internal-Use OnlyAn ETag is not required for the initial save, but is required for all subsequent saves. See Conditional Operations. A different response code is returned depending on whether the request is for the initial save or a subsequent save.Save and return report content
head
Internal-Use OnlyReturns whether the persisted report content version existsCheck persisted report content version
get
Internal-Use OnlyReturns the persisted report content version.Get persisted report content version
post
Internal-Use OnlyValidates the report content against a schema. The schema specified in the report content is used for validation.Validate the persisted report content schema
get
Internal-Use OnlyReturn all available versions of report content.Get available versions of report content
get
Internal-Use OnlyReturn the current default versions of report content.Get the default version of report content
get
Internal-Use OnlyReturn the report content version for the given semantic version.Get the report content version for the given semantic version
head
Internal-Use OnlyReturns the headers for a report content elements, including ETag. See Conditional Operations.Check report content elements status
get
Internal-Use OnlyReturns the collection of elements.Get report content elements
post
Internal-Use OnlyReturns the converted report content.Convert content from XML to JSON
post
Internal-Use OnlyReturns the converted report content.Convert content from JSON to XML
post
Internal-Use OnlyValidates the report content against a schema. The schema specified in the report content is used for validation.Validate report content schema
The operations for the report state resource.
head
Internal-Use OnlyReturns the headers for a collection of report states of the current user associated with a report with standard paging, filtering, and sorting options.Check a collection of report states
get
Internal-Use OnlyReturns a collection of report states of the current user associated with a report with standard paging, filtering, and sorting options.Get a collection of report states
post
Internal-Use OnlyCreates a new report state.Create report state
head
Internal-Use OnlyReturns the headers for a report state, including ETag.Check report state status
get
Internal-Use OnlyReturns the specified report state, including ETag header. See Conditional Operations.Get report state
delete
Internal-Use OnlyDeletes the specified report state.Delete report state
put
Internal-Use OnlyUpdates the specified report state. Either an If-Match or If-Unmodified-Since request header is required. See Conditional Operations.Update report state
The operations for the report state content resource.
head
Internal-Use OnlyReturns the headers for a report state content, including ETag. See Conditional Operations.Check report state content status
get
Internal-Use OnlyReturns the report state content, including ETag. See Conditional Operations.Get report state content
put
Internal-Use OnlySaves the report state content. Does not return the stored state content. An ETag is not required for the initial save, but is required for all subsequent saves. In some situations where Accept type header is automatically generated, setting it to '*/*' will achieve the same effect as not including it. See Conditional Operations.Save report state content
put
Internal-Use OnlySaves and returns the report state content. An ETag is not required for the initial save, but required for all subsequent saves. See Conditional Operations. A different response code is returned depending on whether the request is for the initial save or a subsequent save.