Get the history of a Batch
/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
- application/json
-
batchId: string
The unique identifier of the batch in Capture.
-
locale(optional): string
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.
Response
- application/json
200 Response
The batch history specified by batchId.
object
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.
-
batchAuditMessages(optional):
array batchAuditMessages
This array contains all batch audit event messages. It is time ordered (descending) by the message
timestamp
. -
detailMessages(optional):
array detailMessages
This array contains all the logging messages associated with the batch. It is time ordered (descending) by the message
timestamp
. -
documentAuditMessages(optional):
array documentAuditMessages
This array contains all document audit event message that pertain to this batch. It is time ordered (descending) by the message
timestamp
.
array
This array contains all batch audit event messages. It is time ordered (descending) by the
message timestamp
.
-
Array of:
object 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.
array
This array contains all the logging messages associated with the batch. It is time ordered (descending) by the
message timestamp
.
-
Array of:
object 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.
array
This array contains all document audit event message that pertain to this batch. It is time ordered (descending) by the
message timestamp
.
-
Array of:
object 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.
object
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.
-
auditId(optional):
string
The audit identifier of the message. This identifier is used to correlate messages with each other. Messages with the same
auditId
are part of the same occurrence of the given audit event. -
batchId(optional):
string
The associated batch identifier.
-
batchName(optional):
string
The associated batch name.
-
documentId(optional):
string
The associated document identifier, if the message pertains to a document.
-
documentTitle(optional):
string
The associated document name, if the message pertains to a document.
The title of a document may change. This will be the title of the document at the time the message occurred.
-
message(optional):
string
The message content produced by Capture.
-
timestamp(optional):
string(date-time)
This identifies when the message occurred. The date/time in ISO-8601 Date Time format (
yyyy-MM-dd'T'HH:mm:ss.SSSZ
) UTC, governed by RFC 3339.
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.