Include the following headers in the request:

Accept - application/json
Content-Type - application/json

To support UTF-8 character encoding, for example, to use Japanese characters in table and column names, include the following headers in the request:

Accept: application/json;charset=utf-8
Accept-Charset: charset=utf-8
Content-Type: application/json;charset=utf-8

Use the following request syntax to consume data:

{
"batchSize": <value>
"requestType": <value>
"eventId": <value>
"aggregated": <value>
}

Where

<value>

takes one of the following values:

The
batchSize
value can range between 1 to 5000. Default is 500.
The
requestType
option can use the following values:
RECONSUME
REPROCESS
PROCESS
Default is PROCESS.
The
eventId
is mandatory only when the
requestType
is set to
REPROCESS
or
RECONSUME
.
The
aggregated
option can use the following values:
true. The subscription consumes all the available publications in each API call. A separate aggregated event is created and the child event is processed.
false. The subscription consumes only the oldest publication in each API call. A separate aggregated event is not created and the child event is processed.
Default is
true
. This option is not considered when the
requestType
is set to
REPROCESS
or
RECONSUME
.

To reprocess a failed subscription, use the following request syntax:

{
"batchSize": <value>,
"requestType": "REPROCESS",
"eventId": <eventId>
}  

{
"batchSize": 2,
"requestType" : "REPROCESS",
"eventId": 318007
}  

To reconsume data that had previously been processed, use the following request syntax:

{
"batchSize": <value>,
"requestType": "RECONSUME",
"eventId": <eventId>
}

{
"batchSize": 4,
"requestType" : "REPROCESS",
"eventId": 40559,
}