Generate a global report
post
/ec-auth-svc/rest/v1.0/report/{reportName}
Generates global reports for the specified report type. Clients must provide the report name as a path parameter and can supply filter/query criteria in the request payload.
The response is a paginated list of results based on the applied filter.
Request
Path Parameters
-
reportName(required): string
The name of the report to generate.Example:
USER_ASSIGNMENT
Supported Media Types
- application/json
Root Schema : SearchSpecs
Type:
objectTitle:
SearchSpecsRequest body passing search specs like limit, offset and list of fields
Show Source
-
fieldSpecsList: array
fieldSpecsList
-
limit: integer
(int32)
Minimum Value:
1Maximum Value:5000Maximum number of records to display per page.Example:50 -
offset: integer
(int32)
Minimum Value:
0Maximum Value:2147483647An order number to specify with which object you want to start retrieving result. If provided, you also need to specify a value for the limit parameter. Offset is affected by the value of the order parameterExample:5
Nested Schema : fieldSpecsList
Type:
Show Source
array-
Array of:
object Field
Contains field details.
Nested Schema : Field
Type:
objectContains field details.
Show Source
-
fieldName(required): string
Minimum Length:
0Maximum Length:255Field nameExample:siteIds -
fieldSequence: integer
(int32)
Minimum Value:
0Field sequenceExample:1 -
fieldType(required): string
Minimum Length:
0Maximum Length:50Field typeExample:list -
fieldValueList(required): string
List of values for the FieldExample:
["D5E16DD550CB4AD1B330E0D09B4B8F3F","A5E16DD550CB4AD1B330E0D09B4B8F3F"]
Examples
Back to Top
Response
Supported Media Types
- application/json
200 Response
Successful report generated. The response is wrapped in AuthResponse with result as PaginatedResponseDto.
Root Schema : AuthResponse
Type:
objectGeneric API response wrapper containing result, error data, response version and status.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result data of the API response; actual type depends on the API
-
status: string
(none)
Indicates request success ("success") or failure ("failure").Example:
success -
version: integer
(int32)
Version of the response schema.Example:
1
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult data of the API response; actual type depends on the API
Example:
oracle.doceng.json.BetterJsonNull@3565a0f5Examples
400 Response
Bad request. Failed to generate the report due to validation or business errors.
Root Schema : AuthResponse
Type:
objectGeneric API response wrapper containing result, error data, response version and status.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result data of the API response; actual type depends on the API
-
status: string
(none)
Indicates request success ("success") or failure ("failure").Example:
success -
version: integer
(int32)
Version of the response schema.Example:
1
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult data of the API response; actual type depends on the API
Example:
oracle.doceng.json.BetterJsonNull@3565a0f5Examples