List or find falloutException objects

get

https://serverRoot/fallout/v2.0/falloutException

This operation lists or finds fallout entities.

Request

Query Parameters
  • Retrieves fallout exceptions for a given customer name. Multiple customer names can also be provided. Example: GET /falloutException?customerName=abcd or GET /falloutException?customerName=abcd&customerName=xyz
  • Comma-separated properties to be provided in response. Example: GET /falloutException?fields=customerName,orderId,state,requestedCompletionDate
  • Returns the filtered falloutException objects. Wildcard search supports for customerName and orderType fields only. Any of these contains (field,'searchstring') or startswith(field,'searchstring') or endswith(field,'searchstring') can be provided using filterBy. Multiple wildcard search is also supported. Example: GET /falloutException?filterBy=contains(customerName,'ABC') Example: GET /falloutException?filterBy=contains(customerName,'ABC')&filterBy=contains(orderType,'Service')
  • The start date for the requested completion date. Must be used together with `toRequestedCompletionDate`. Example: GET /falloutException?fromRequestedCompletionDate=2016-11-15&toRequestedCompletionDate=2016-11-20
  • The start date for the report. Must be used together with `tofalloutCreationDate`. Example: GET /falloutException?fromfalloutCreationDate=2016-11-15&tofalloutCreationDate=2016-11-20
  • Returns the aggregated falloutException objects with total fallout exception per order and other aggregated details. Fallout Exceptions can only be grouped based on orderId. Example: GET /falloutException?groupBy=orderId
  • Requested number of resources to be provided in response. Example: GET /falloutException?limit=100 (Returns the first 100 fallout exceptions.) Example: GET /falloutException (Returns the first 50 fallout exceptions. The default limit size is 50.)
  • Requested index for start of resources to be provided in response. Example: GET /falloutException?offset=25&limit=50 (Returns fallout exceptions 26..50.) Example: GET /falloutException?offset=25 (Returns fallout exceptions 26..50. The default limit size is 50.)
  • Returns the fallout exceptions in sorted order. Valid fields when used with groupBy parameter: [orderId,customerName,orderType,requestedCompletionDate,creationDate,externalId,totalFalloutExceptionPerOrder]. Valid fields when used without groupBy parameter: [timestamp,errorId,productNames,taskName]. Example: GET /falloutException?orderBy=errorId&sort=asc Example: GET /falloutException?orderBy=errorId ( Default sort will be descending order.) Example: GET /falloutException?groupBy=orderId&orderBy=creationDate&sort=desc
    Allowed Values: [ "timestamp", "errorId", "productNames", "taskName", "orderId", "customerName", "orderType", "requestedCompletionDate", "creationDate", "externalId", "totalFalloutExceptionPerOrder" ]
  • Retrieves fallout exceptions for a an orderId. Multiple orderIds can also be provided. Example: GET /falloutException?orderId=12345 or GET /falloutException?orderId=12345&orderId=3312
  • Retrieves data based on orderType (this is shown as "Reference #" in the Fallout Orders page in the UI). Multiple states can also be provided. Example: GET /falloutException?orderType=product or GET /falloutException?orderType=product&orderType=Service
  • Retrieves fallout exceptions for orders that are overdue based on requested completion date. Example: GET /falloutException?overdue=true
  • Type of sorting. Must be used together with 'orderBy'. Example: GET /falloutException?orderBy=errorId&sort=desc Example: GET /falloutException?orderBy=errorId&sort=asc
    Allowed Values: [ "asc", "desc" ]
  • Retrieves data based on the state of the Fallout Exception. Multiple states can also be provided. Example: GET /falloutException?state=created or GET /falloutException?state=created&state=completed
  • The end date for the report. Must be used together with `fromRequestedCompletionDate`. Example: GET /falloutException?fromRequestedCompletionDate=2016-11-15&toRequestedCompletionDate=2016-11-20
  • The end date for the report. Must be used with `fromfalloutCreationDate`. Example: GET /falloutException?fromfalloutCreationDate=2016-11-15&tofalloutCreationDate=2016-11-20

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

The operation is successful.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : items
Match One Schema
Show Source
Nested Schema : falloutException
Type: object
Show Source
Nested Schema : aggregatedFalloutException
Aggregate of fallout exceptions grouped using orderID.
Match All
Aggregate of fallout exceptions grouped using orderID.
Aggregate of fallout exceptions grouped using orderID.
Show Source
Nested Schema : additionalFalloutProperties
Type: array
Additional fallout properties list.
Show Source
Nested Schema : attributes
Type: array
The fallout custom exception attributes.
Show Source
  • attribute
    This holds all additional attributes for the OSM user interface. For example, 'status'. The API does not provide filtering on the attributes.
Nested Schema : productNames
Type: array
List of product names.
Show Source
Nested Schema : taskStatuses
Type: array
List of task statuses.
Show Source
Nested Schema : additionalFalloutProperties
Type: object
This holds all the additional properties such as schema details.
Show Source
Nested Schema : attribute
Type: object
This holds all additional attributes for the OSM user interface. For example, 'status'. The API does not provide filtering on the attributes.
Show Source
  • The name of the attribute. For example, 'status' owned by the user interface.
  • The value of the attribute. For example, the value of 'status', handled by UI backend.
Nested Schema : productNames
Type: object
List of ProductNames.
Show Source
Nested Schema : aggregatedFalloutException-allOf[1]
Type: object
Show Source

400 Response

Bad Request
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. Typically, with an HTTP error response-code (3xx, 4xx, 5xx).
Show Source

401 Response

Unauthorized
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. Typically, with an HTTP error response-code (3xx, 4xx, 5xx).
Show Source

403 Response

Forbidden
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. Typically, with an HTTP error response-code (3xx, 4xx, 5xx).
Show Source

404 Response

Not Found
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. Typically, with an HTTP error response-code (3xx, 4xx, 5xx).
Show Source

500 Response

Internal Server Error
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. Typically, with an HTTP error response-code (3xx, 4xx, 5xx).
Show Source
Back to Top