{"_id":"59a45d467ee621000fc9d407","category":{"_id":"59a45d447ee621000fc9d3bd","version":"59a45d437ee621000fc9d3b7","project":"57336fd5a6a9c40e00e13a0b","__v":0,"sync":{"url":"","isSync":false},"reference":true,"createdAt":"2015-10-19T18:30:57.575Z","from_sync":false,"order":5,"slug":"batch-payment-transaction-service","title":"Batch Transactions"},"project":"57336fd5a6a9c40e00e13a0b","user":"560d5913af97231900938124","parentDoc":null,"version":{"_id":"59a45d437ee621000fc9d3b7","project":"57336fd5a6a9c40e00e13a0b","__v":1,"createdAt":"2017-08-28T18:13:23.840Z","releaseDate":"2017-08-28T18:13:23.840Z","categories":["59a45d447ee621000fc9d3b8","59a45d447ee621000fc9d3b9","59a45d447ee621000fc9d3ba","59a45d447ee621000fc9d3bb","59a45d447ee621000fc9d3bc","59a45d447ee621000fc9d3bd","59a45d447ee621000fc9d3be","59a45d447ee621000fc9d3bf","59a45d447ee621000fc9d3c0","59a45d447ee621000fc9d3c1","59a45d447ee621000fc9d3c2","59a45d447ee621000fc9d3c3","59a45d447ee621000fc9d3c4","59a45d447ee621000fc9d3c5","59a45d447ee621000fc9d3c6","59a45d447ee621000fc9d3c7"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"3.22.1","version_clean":"8976.0.0-XML","version":"8976-XML"},"__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-22T13:00:00.982Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","examples":{"codes":[]},"method":"get","results":{"codes":[{"language":"text","code":""}]},"auth":"optional","params":[{"_id":"56953ff3fe18811700c9bfcc","ref":"","in":"path","required":true,"desc":"batch ID sent in the Create Batch Transaction request","default":"","type":"string","name":"batch-id"}],"url":"/batch-transactions/:batch-id"},"isReference":true,"order":14,"body":"Retrieve is a request that gets details about a submitted batch transaction, such as the callback URL, and the details of each transaction within the batch.\n\n<a class=\"btn btn-success\" href=\"#section-api-explorer-for-request-based-on-transaction-id-\" role=\"button\">Try it in the API Explorer</a>\n\n###Request Content\nEnter the `batch-id` into the web service URL, in the format:\n`services/2/batch-transactions/{batch-id}`\n\nFor example:\n`services/2/batch-transactions/567890`\n\n###Response Details\nIf successful, the response HTTP status code is 200 OK.\nThe response contains the retrieved `batch-transaction` resource (see [batch-transaction](doc:batch-transaction)) with the request properties plus these additions:\n `transaction-count`: number of transactions within the batch\n `transaction-id`: ID for each transaction in the batch\n `processing-info`: processing status for the entire batch and for each transaction in the batch\n\n<hr>\n\n##Examples\n\n###Request Example\n[block:code]\n{\n \"codes\": [\n {\n \"code\": \"curl -v -X GET https://sandbox.bluesnap.com/services/2/batch-transactions/id1234 \\\\\\n-H 'Content-Type: application/xml' \\\\\\n-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ='\",\n \"language\": \"curl\",\n \"name\": \"Retrieve Batch Transaction Request\"\n }\n ]\n}\n[/block]\n###Response Example\n[block:code]\n{\n \"codes\": [\n {\n \"code\": \"HTTP/ 1.1 200 OK\\n\\n<batch-transaction xmlns=\\\"http://ws.plimus.com\\\">\\n <batch-id>my_unique_batch_id</batch-id>\\n <callback-url>http://client.com/batch_callback</callback-url>\\n <transaction-count>1</transaction-count>\\n <card-transaction>\\n <card-transaction-type>AUTH_CAPTURE</card-transaction-type>\\n <merchant-transaction-id>566</merchant-transaction-id>\\n <recurring-transaction>RECURRING</recurring-transaction>\\n <soft-descriptor>DescTest txn1</soft-descriptor>\\n <amount>11</amount>\\n <currency>USD</currency>\\n <card-holder-info>\\n <first-name>test first name</first-name>\\n <last-name>test last name</last-name>\\n </card-holder-info>\\n <credit-card>\\n <card-last-four-digits>1881</card-last-four-digits>\\n <card-type>VISA</card-type>\\n <card-sub-type>CREDIT</card-sub-type>\\n <expiration-month>7</expiration-month>\\n <expiration-year>2016</expiration-year>\\n </credit-card>\\n <transaction-meta-data/>\\n <processing-info>\\n <processing-status>success</processing-message >\\n </processing-info>\\n </card-transaction>\\n <processing-info>\\n <processing-status>COMPLETED</processing-status>\\n </processing-info>\\n</batch-transaction>\",\n \"language\": \"xml\",\n \"name\": \"Retrieve Batch Transaction Response: 200 OK\"\n }\n ]\n}\n[/block]\n<hr>\n\n##Example Description\nAbove is an example request. Note that no XML content is required in the request body. All relevant info is included in the request URL. You simply need to include the batch ID in the request URL. The batch ID is the unique ID sent in the the `batch-id` property in the [Create Batch Transaction](doc:create-batch-transaction) request.\n\n\n<br>\n<a class=\"btn btn-primary\" href=\"#\" role=\"button\">Back to Top</a>\n\n<hr>\n\n##API Explorer (for request based on Transaction ID)\nTo test out a call, enter an existing batch ID (e.g *567890*) in the `batch-id` field. This will automatically insert the ID into the request URL. Leave the Body Content field empty.","excerpt":"","slug":"retrieve-batch-transaction","type":"get","title":"Retrieve Batch Transaction"}getRetrieve Batch Transaction
Definition
{{ api_url }}{{ page_api_url }}
Parameters
Path Params
batch-id:
required
string
batch ID sent in the Create Batch Transaction request
Documentation
Retrieve is a request that gets details about a submitted batch transaction, such as the callback URL, and the details of each transaction within the batch.
Request Content
Enter the batch-id into the web service URL, in the format:services/2/batch-transactions/{batch-id}
For example:services/2/batch-transactions/567890
Response Details
If successful, the response HTTP status code is 200 OK.
The response contains the retrieved batch-transaction resource (see batch-transaction) with the request properties plus these additions:
transaction-count: number of transactions within the batch
transaction-id: ID for each transaction in the batch
processing-info: processing status for the entire batch and for each transaction in the batch
Examples
Request Example
curl -v -X GET https://sandbox.bluesnap.com/services/2/batch-transactions/id1234 \
-H 'Content-Type: application/xml' \
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ='HTTP/ 1.1 200 OK
<batch-transaction xmlns="http://ws.plimus.com">
<batch-id>my_unique_batch_id</batch-id>
<callback-url>http://client.com/batch_callback</callback-url>
<transaction-count>1</transaction-count>
<card-transaction>
<card-transaction-type>AUTH_CAPTURE</card-transaction-type>
<merchant-transaction-id>566</merchant-transaction-id>
<recurring-transaction>RECURRING</recurring-transaction>
<soft-descriptor>DescTest txn1</soft-descriptor>
<amount>11</amount>
<currency>USD</currency>
<card-holder-info>
<first-name>test first name</first-name>
<last-name>test last name</last-name>
</card-holder-info>
<credit-card>
<card-last-four-digits>1881</card-last-four-digits>
<card-type>VISA</card-type>
<card-sub-type>CREDIT</card-sub-type>
<expiration-month>7</expiration-month>
<expiration-year>2016</expiration-year>
</credit-card>
<transaction-meta-data/>
<processing-info>
<processing-status>success</processing-message >
</processing-info>
</card-transaction>
<processing-info>
<processing-status>COMPLETED</processing-status>
</processing-info>
</batch-transaction>Example Description
Above is an example request. Note that no XML content is required in the request body. All relevant info is included in the request URL. You simply need to include the batch ID in the request URL. The batch ID is the unique ID sent in the the batch-id property in the Create Batch Transaction request.
API Explorer (for request based on Transaction ID)
To test out a call, enter an existing batch ID (e.g 567890) in the batch-id field. This will automatically insert the ID into the request URL. Leave the Body Content field empty.