Get the history of a Batch

get

/capture/api/v1.1/batches/{batchId}/history

This operation will return this history of a given batch as specified by the batchId parameter. This history is a collection of message activities have occurred within the batch, as well as associated documents. In essence, it represents activity logging of that batch processing.

The history is only available while the batch is present. Once the batch is deleted from Capture, either manually or through a Commit operation, this history is removed from the system. At that point, only audit information may be obtained.

Request

Supported Media Types
Path Parameters
Query Parameters
  • The locale parameter is used to specify the language translations used for messages in the audit events. It does not effect the language of detail activity messages. The value must be in the form of standard language tags as defined by RFC 4647.

    If this is not specified, the default language settings locale will be used.

Back to Top

Response

Supported Media Types

200 Response

The batch history specified by batchId.

Body ()
Root Schema : Batch History
Type: object
Title: Batch History

This object contains a collection of messages that detail the history of a batch as it progresses through Capture.

The history is set of audit events and associated detail messages. For instance, several processing audit events may occur in the life of a batch. As batch processing is happening, detail messages are written to logs that provide more information as to what is happening during processing.

Show Source
Nested Schema : batchAuditMessages
Type: array

This array contains all batch audit event messages. It is time ordered (descending) by the message timestamp.

Show Source
  • History Message
    Title: History Message

    This message that occurs in Capture that represents a distinct audit event, or associated logging message.

    A message will always be associated to an individual audit event. But, the message can be the actual audit event. Other messages provide more detail related to that event.

    The message produced in Capture will be associated to a Batch. They may, or may not, be associated to a Document in that batch.

Nested Schema : detailMessages
Type: array

This array contains all the logging messages associated with the batch. It is time ordered (descending) by the message timestamp.

Show Source
  • History Message
    Title: History Message

    This message that occurs in Capture that represents a distinct audit event, or associated logging message.

    A message will always be associated to an individual audit event. But, the message can be the actual audit event. Other messages provide more detail related to that event.

    The message produced in Capture will be associated to a Batch. They may, or may not, be associated to a Document in that batch.

Nested Schema : documentAuditMessages
Type: array

This array contains all document audit event message that pertain to this batch. It is time ordered (descending) by the message timestamp.

Show Source
  • History Message
    Title: History Message

    This message that occurs in Capture that represents a distinct audit event, or associated logging message.

    A message will always be associated to an individual audit event. But, the message can be the actual audit event. Other messages provide more detail related to that event.

    The message produced in Capture will be associated to a Batch. They may, or may not, be associated to a Document in that batch.

Nested Schema : History Message
Type: object
Title: History Message

This message that occurs in Capture that represents a distinct audit event, or associated logging message.

A message will always be associated to an individual audit event. But, the message can be the actual audit event. Other messages provide more detail related to that event.

The message produced in Capture will be associated to a Batch. They may, or may not, be associated to a Document in that batch.

Show Source

404 Response

Not Found

The request includes a resource URI that does not exist. The response will be an Error Detail object.

500 Response

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request. The response will be an Error Detail object.

Back to Top