Samples
Last updated: Aug 15th, 7:27am
- Run a daily activity report
- Run a transaction summary report
- Get results by report ID
- Get metadata
- Get data
- Create a report template
- Update a report template
- Get a report template
- Delete a report template
- Create a schedule
- Get a schedule
- Update a schedule
- Delete a schedule
- Run a transaction ID search
- Run a profile - Next payment date report
- Run a profile - Profile modified date Report
Run a daily activity report
Request
This request demonstrates how to run a Daily Activity Report with a page size of 50 lines to obtain results for September 7, 2014.
<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user>User</user> <vendor>Vendor</vendor> <partner>Partner</partner> <password>Password</password> </authRequest> <runReportRequest> <reportName>DailyActivityReport</reportName> <reportParam> <paramName>report_date</paramName> <paramValue>2014-09-07</paramValue> </reportParam> <pageSize>50</pageSize> </runReportRequest> </reportingEngineRequest>
Response
In the response to running the Daily Activity Report, the
responseCode
of 100 indicates that the report completed
successfully. The reportId
132 returned is used to uniquely
identify this report in future calls to the Reporting API.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <runReportResponse>8 <reportId>132</reportId>9 <statusCode>3</statusCode>10 <statusMsg>Report has completed successfully</statusMsg>11 </runReportResponse>12 </reportingEngineResponse>
Run a transaction summary report
Request
The request demonstrates how to run a Transaction Summary Report with a page size of 50 lines starting on October 13 at 12:00AM and ending on October 15 at 12:59 and 59 seconds PM.
<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user>User</user> <vendor>Vendor</vendor> <partner>Partner</partner> <password>Password</password> </authRequest> <runReportRequest> <reportName>TransactionSummaryReport</reportName> <reportParam> <paramName>start_date</paramName> <paramValue>2020-10-13</paramValue> </reportParam> <reportParam> <paramName>end_date</paramName> <paramValue>2020-10-15</paramValue> </reportParam> <pageSize>50</pageSize> </runReportRequest> </reportingEngineRequest>
Response
In the response to running the Transaction Summary Report, the response code
of 100
indicates that the request completed successfully. The
status code of 3 indicates that the report completed successfully and the
reportId
131 is returned for future reverence in calls inquiring
about this report.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <runReportResponse>8 <reportId>133</reportId>9 <statusCode>3</statusCode>10 <statusMsg>Report has completed successfully</statusMsg>11 </runReportResponse>12</reportingEngineResponse>
Get results by report ID
Request
In the request to get the results by report ID, reportId
131
specifies the report for which results are being requested. The
reportId
131 was returned in a previous call to run the report.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <getResultsRequest> <reportId>131</reportId> </getResultsRequest> </reportingEngineRequest>
Response
In the response to getting results by report ID, the response code of
100
indicates that the request completed successfully. The status
code of 3 indicates that the report with reportId
131 completed
successfully.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <getResultsResponse>8 <Results>9 <reportId>131</reportId>10 <statusCode>3</statusCode>11 <statusMsg>Report has completed successfully</statusMsg>12 </Results>13 </getResultsResponse>14</reportingEngineResponse>
Get metadata
Request
The request demonstrates how to obtain the formatting information for the
report with reportId
131.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <getMetaDataRequest> <reportId>131</reportId> </getMetaDataRequest> </reportingEngineRequest>
Response
In the response to retrieving metadata, the response code of
100
indicates that the request completed successfully. The
response returns the number columns, rows, pages, and lines per page are
present in the format of the report with reportID
131. For each
table column, the response returns the column heading.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <getMetaDataResponse>8 <numberOfRows>13</numberOfRows>9 <numberOfPages>1</numberOfPages>10 <pageSize>50</pageSize>11 <numberOfColumns>11</numberOfColumns>12 <columnMetaData>13 <dataName>Transaction ID</dataName>14 <dataType>string</dataType>15 </columnMetaData>16 <columnMetaData>17 <dataName>Trans Time</dataName>18 <dataType>date</dataType>19 </columnMetaData>20 <columnMetaData>21 <dataName>Trans Type</dataName>22 <dataType>string</dataType>23 </columnMetaData>24 <columnMetaData>25 <dataName>Tender Type</dataName>26 <dataType>string</dataType>27 </columnMetaData>28 <columnMetaData>29 <dataName>Account Number</dataName>30 <dataType>string</dataType>31 </columnMetaData>32 <columnMetaData>33 <dataName>Expires</dataName>34 <dataType>string</dataType>35 </columnMetaData>36 <columnMetaData>37 <dataName>Amount</dataName>38 <dataType>string</dataType>39 </columnMetaData>40 <columnMetaData>41 <dataName>Result</dataName>42 <dataType>number</dataType>43 </columnMetaData>44 <columnMetaData>45 <dataName>Reponse Msg</dataName>46 <dataType>string</dataType>47 </columnMetaData>48 <columnMetaData>49 <dataName>Comment1</dataName>50 <dataType>string</dataType>51 </columnMetaData>52 <columnMetaData>53 <dataName>Comment2</dataName>54 <dataType>string</dataType>55 </columnMetaData>56 </getMetaDataResponse>57</reportingEngineResponse>
The format returned by this sample is:
Note The last four digits of the account number are returned.
Transaction ID | Trans Time | Trans Type | Tender Type | Account Number | Expires | Amount | Result | Response Msg | Comment1 | Comment2 |
---|---|---|---|---|---|---|---|---|---|---|
V89A0A000087 | 2014-09-07 17:45:07 | S | O | 1111 | 01/15 | A1000 | O | Approved | ||
V89A0A000088 | 2014-09-07 17:45:09 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000089 | 2014-09-07 17:48:20 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008A | 2014-09-07 17:52:03 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008B | 2014-09-07 17:53:07 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008C | 2014-09-07 17:53:32 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008D | 2014-09-07 17:54:20 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008E | 2014-09-07 17:56:02 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008F | 2014-09-07 17:56:33 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000090 | 2014-09-07 18:01:31 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000091 | 2014-09-07 18:01:44 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000092 | 2014-09-07 18:02:19 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000093 | 2014-09-07 18:03:09 | S | O | 1111 | 01/07 | A1000 | O | Approved |
Get data
Request
In the request to retrieve data, reportId
131 specifies the
report for which the data is being requested. The reportId
value
of 131 was returned in a previous call to run the report. The
pageNum
refers to the page number desired in a multi-page report.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <getDataRequest> <reportId>131</reportId> <pageNum>1</pageNum> </getDataRequest> </reportingEngineRequest>
Response
In the response to retrieving data, the response code of
100
indicates that the request completed successfully. The
response returns the data in each of the columns and rows of the report with
reportID
131.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <getDataResponse>8 <reportDataRow>9 <columnData>10 <data>V89A0A000087</data>11 </columnData>12 <columnData>13 <data>2014-09-07 17:45:08</data>14 </columnData>15 <columnData>16 <data>S</data>17 </columnData>18 <columnData>19 <data>0</data>20 </columnData>21 <columnData>22 <data>4111XXXXXXXX1111</data>23 </columnData>24 <columnData>25 <data>01/07</data>26 </columnData>27 <columnData>28 <data>A1000</data>29 </columnData>30 <columnData>31 <data>0</data>32 </columnData>33 <columnData>34 <data>Approved</data>35 </columnData>36 <columnData>37 <data/>38 </columnData>39 <columnData>40 <data/>41 </columnData>42 </reportDataRow>43 <reportDataRow>44 <columnData>45 <data>V89A0A000088</data>46 </columnData>47 <columnData>48 <data>2014-09-07 17:46:09</data>49 </columnData>50 <columnData>51 <data>S</data>52 </columnData>53 <columnData>54 <data>0</data>55 </columnData>56 <columnData>57 <data>4111XXXXXXXX1111</data>58 </columnData>59 <columnData>60 <data>01/15</data>61 </columnData>62 <columnData>63 <data>A1000</data>64 </columnData>65 <columnData>66 <data>0</data>67 </columnData>68 <columnData>69 <data>Approved</data>70 </columnData>71 <columnData>72 <data/>73 </columnData>74 <columnData>75 <data/>76 </columnData>77 </reportDataRow>78 <reportDataRow>79 <columnData>80 <data>V89A0A000089</data>81 </columnData>82 <columnData>83 <data>2014-09-07 17:48:20</data>84 </columnData>85 <columnData>86 <data>S</data>87 </columnData>88 <columnData>89 <data>0</data>90 </columnData>91 <columnData>92 <data>4111XXXXXXXX1111</data>93 </columnData>94 <columnData>95 <data>01/15</data>96 </columnData>97 <columnData>98 <data>A1000</data>99 </columnData>100 <columnData>101 <data>0</data>102 </columnData>103 <columnData>104 <data>Approved</data>105 </columnData>106 <columnData>107 <data/>108 </columnData>109 <columnData>110 <data/>111 </columnData>112 </reportDataRow>113 <reportDataRow>114 <columnData>115 <data>V89A0A00008A</data>116 </columnData>117 <columnData>118 <data>2014-09-07 17:52:03</data>119 </columnData>120 <columnData>121 <data>S</data>122 </columnData>123 <columnData>124 <data>0</data>125 </columnData>126 <columnData>127 <data>4111XXXXXXXX1111</data>128 </columnData>129 <columnData>130 <data>01/15</data>131 </columnData>132 <columnData>133 <data>A1000</data>134 </columnData>135 <columnData>136 <data>0</data>137 </columnData>138 <columnData>139 <data>Approved</data>140 </columnData>141 <columnData>142 <data/>143 </columnData>144 <columnData>145 <data/>146 </columnData>147 </reportDataRow>148 <reportDataRow>149 <columnData>150 <data>V89A0A00008B</data>151 </columnData>152 <columnData>153 <data>2014-09-07 17:53:07</data>154 </columnData>155 <columnData>156 <data>S</data>157 </columnData>158 <columnData>159 <data>0</data>160 </columnData>161 <columnData>162 <data>4111XXXXXXXX1111</data>163 </columnData>164 <columnData>165 <data>01/15</data>166 </columnData>167 <columnData>168 <data>A1000</data>169 </columnData>170 <columnData>171 <data>0</data>172 </columnData>173 <columnData>174 <data>Approved</data>175 </columnData>176 <columnData>177 <data/>178 </columnData>179 <columnData>180 <data/>181 </columnData>182 </reportDataRow>183 <reportDataRow>184 <columnData>185 <data>V89A0A00008C</data>186 </columnData>187 <columnData>188 <data>2014-09-07 17:53:32</data>189 </columnData>190 <columnData>191 <data>S</data>192 </columnData>193 <columnData>194 <data>0</data>195 </columnData>196 <columnData>197 <data>4111XXXXXXXX1111</data>198 </columnData>199 <columnData>200 <data>01/15</data>201 </columnData>202 <columnData>203 <data>A1000</data>204 </columnData>205 columnData>206 data>0</data>207 </columnData>208 <columnData>209 <data>Approved</data>210 </columnData>211 <columnData>212 <data/>213 </columnData>214 <columnData>215 <data/>216 </columnData>217 </reportDataRow>218 <reportDataRow>219 <columnData>220 <data>V89A0A00008D</data>221 </columnData>222 <columnData>223 <data>2014-09-07 17:54:20</data>224 </columnData>225 <columnData>226 <data>S</data>227 </columnData>228 <columnData>229 <data>0</data>230 </columnData>231 <columnData>232 <data>4111XXXXXXXX1111</data>233 </columnData>234 <columnData>235 <data>01/07</data>236 </columnData>237 <columnData>238 <data>A1000</data>239 </columnData>240 <columnData>241 <data>0</data>242 </columnData>243 <columnData>244 <data>Approved</data>245 </columnData>246 <columnData>247 <data/>248 </columnData>249 <columnData>250 <data/>251 </columnData>252 </reportDataRow>253 <reportDataRow>254 <columnData>255 <data>V89A0A00008E</data>256 </columnData>257 <columnData>258 <data>2014-09-07 17:56:02</data>259 </columnData>260 <columnData>261 <data>S</data>262 </columnData>263 <columnData>264 data>0</data>265 </columnData>266 <columnData>267 <data>4111XXXXXXXX1111</data>268 </columnData>269 <columnData>270 <data>01/15</data>271 </columnData>272 <columnData>273 <data>A1000</data>274 </columnData>275 <columnData>276 <data>0</data>277 </columnData>278 <columnData>279 <data>Approved</data>280 </columnData>281 <columnData>282 <data/>283 </columnData>284 <columnData>285 <data/>286 </columnData>287 </reportDataRow>288 <reportDataRow>289 <columnData>290 <data>V89A0A00008F</data>291 </columnData>292 <columnData>293 <data>2014-09-07 17:56:33</data>294 </columnData>295 <columnData>296 <data>S</data>297 </columnData>298 <columnData>299 <data>0</data>300 </columnData>301 <columnData>302 <data>4111XXXXXXXX1111</data>303 </columnData>304 <columnData>305 <data>01/15</data>306 </columnData>307 <columnData>308 <data>A1000</data>309 </columnData>310 <columnData>311 <data>0</data>312 </columnData>313 <columnData>314 <data>Approved</data>315 </columnData>316 <columnData>317 <data/>318 </columnData>319 <columnData>320 <data/>321 </columnData>322 </reportDataRow>323 <reportDataRow>324 <columnData>325 <data>V89A0A000090</data>326 </columnData>327 <columnData>328 <data>2014-09-07 18:01:31</data>329 </columnData>330 <columnData>331 <data>S</data>332 </columnData>333 <columnData>334 <data>0</data>335 </columnData>336 <columndata>337 <data>4111XXXXXXXX1111</data>338 </columnData>339 <columnData>340 <data>01/15</data>341 </columnData>342 <columnData>343 <data>A1000</data>344 </columnData>345 <columnData>346 <data>24</data>347 </columnData>348 <columnData>349 <data>Unknown error</data>350 </columnData>351 <columnData>352 <data/>353 </columnData>354 <columnData>355 <data/>356 </columnData>357 </reportDataRow>358 <reportDataRow>359 <columnData>360 <data>V89A0A000091</data>361 </columnData>362 <columnData>363 <data>2014-09-07 18:01:44</data>364 </columnData>365 <columnData>366 <data>S</data>367 </columnData>368 <columnData>369 <data>0</data>370 </columnData>371 <columnData>372 <data>4111XXXXXXXX1111</data>373 </columnData>374 <columnData>375 <data>12/15</data>376 </columnData>377 <columnData>378 <data>A1000</data>379 </columnData>380 <columnData>381 <data>0</data>382 </columnData>383 <columnData>384 <data>Approved</data>385 </columnData>386 <columnData>387 <data/>388 </columnData>389 <columnData>390 <data/>391 </columnData>392 </reportDataRow>393 <reportDataRow>394 <columnData>395 <data>V89A0A000092</data>396 </columnData>397 <columnData>398 <data>2014-09-07 18:02:19</data>399 </columnData>400 <columnData>401 <data>S</data>402 </columnData>403 <columnData>404 <data>0</data>405 </columnData>406 <columnData>407 <data>4111XXXXXXXX1111</data>408 </columnData>409 <columnData>410 <data>12/15</data>411 </columnData>412 <columnData>413 <data>A1000</data>414 </columnData>415 <columnData>416 <data>0</data>417 </columnData>418 <columnData>419 <data>Approved</data>420 </columnData>421 <columnData>422 <data/>423 </columnData>424 <columnData>425 <data/>426 </columnData>427 </reportDataRow>428 <reportDataRow>429 <columnData>430 <data>V89A0A000093</data>431 </columnData>432 <columnData>433 <data>2014-09-07 18:03:09</data>434 </columnData>435 <columnData>436 <data>S</data>437 </columnData>438 <columnData>439 <data>0</data>440 </columnData>441 <columnData>442 <data>4111XXXXXXXX1111</data>443 </columnData>444 <columnData>445 <data>12/15</data>446 </columnData>447 <columnData>448 <data>A1000</data>449 </columnData>450 <columnData>451 <data>0</data>452 </columnData>453 <columnData>454 <data>Approved</data>455 </columnData>456 <columnData>457 <data/>458 </columnData>459 <columnData>460 <data/>461 </columnData>462 </reportDataRow>463 <pageNum>1</pageNum>464 </getDataResponse>465</reportingEngineResponse>
Response
The data is returned in the following tabular format of 13 rows and 11 columns:
Transaction ID | Trans Time | Trans Type | Tender Type | Account Number | Expires | Amount | Result | Response Msg | Comment1 | Comment2 |
---|---|---|---|---|---|---|---|---|---|---|
V89A0A000087 | 2014-09-07 17:45:07 | S | O | 1111 | 01/15 | A1000 | O | Approved | ||
V89A0A000088 | 2014-09-07 17:45:09 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000089 | 2014-09-07 17:48:20 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008A | 2014-09-07 17:52:03 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008B | 2014-09-07 17:53:07 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008C | 2014-09-07 17:53:32 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008D | 2014-09-07 17:54:20 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008E | 2014-09-07 17:56:02 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A00008F | 2014-09-07 17:56:33 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000090 | 2014-09-07 18:01:31 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000091 | 2014-09-07 18:01:44 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000092 | 2014-09-07 18:02:19 | S | O | 1111 | 01/07 | A1000 | O | Approved | ||
V89A0A000093 | 2014-09-07 18:03:09 | S | O | 1111 | 01/07 | A1000 | O | Approved |
Create a report template
Request
This request creates a report template from a Daily Activity Report with a
report template name of
‘
MyTemplate
’
. It sets the values of two parameters (name1
and
name2
). The parameter names and values are stored in the
database.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <createTemplateRequest> <templateDefinition> <templateName>My Template</templateName> <reportName>DailyActivityReport</reportName> <reportParam> <paramName>name1</paramName> <paramValue>value1</paramValue> </reportParam> <reportParam> <paramName>name2</paramName> <paramValue>value2</paramValue> </reportParam> </templateDefinition> </createTemplateRequest> </reportingEngineRequest>
Response
In the response to creating a report template, the response code of
100
indicates that the request completed successfully.
Thereafter, when
‘
My Template
’
is run, these parameters are automatically retrieved from the database and
used to generate the Daily Activity Report.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Update a report template
Request
The request specifies the report template to update by its name ‘My Template’ and the report type (Daily Activity Report) upon which it was originally based.Updating a report template is not an additive process. It replaces the parameters and values previously defined for ‘My Template’ with new parameters and values.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <updateTemplateRequest> <templateDefinition> <templateName>My Template</templateName> <reportName>DailyActivityReport</reportName> <reportParam> <paramName>name3</paramName> <paramValue>value3</paramValue> </reportParam> <reportParam> <paramName>name4</paramName> <paramValue>value4</paramValue> </reportParam> </templateDefinition> </updateTemplateRequest> </reportingEngineRequest>
Response
In the response to updating a report template, the response code of
100
indicates that the request completed successfully. The
getTemplateRequest
can be used to check the new parameters and
values.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Get a report template
Request
The request specifies the report template name ‘ My Template ’ to retrieve.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <getTemplateRequest> <templateName>My Template</templateName> </getTemplateRequest> </reportingEngineRequest>
Response
In the response to retrieving a report template, the response code of
100
indicates that the request completed successfully. The
response returns the report template name, the report type (Daily Activity
Report) upon which it was originally based, as well as the parameter names and
values defined for this report template.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <getTemplateResponse>8 <templateDefinition>9 <templateName>My Template</templateName>10 <reportName>DailyActivityReport</reportName>11 <reportParam>12 <paramName>name3</paramName>13 <paramValue>value3</paramValue>14 </reportParam>15 <reportParam>16 <paramName>name4</paramName>17 <paramValue>value4</paramValue>18 </reportParam>19 </templateDefinition>20 </getTemplateResponse>21</reportingEngineResponse>
Delete a report template
Request
The request to delete a report template includes the templateName
‘
My Template
’
.
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <deleteTemplateRequest> <templateName>My Template</templateName> </deleteTemplateRequest> </reportingEngineRequest>
Response
In the response to deleting a report template, the response code of
100
indicates that the request completed successfully. If you
were to specify a bogus name for the report template (in error), the
responseCode 113
is returned with the responseMsg
“
Unknown template requested
”
.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>113</responseCode>5 <responseMsg>Unknown template requested</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Create a schedule
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <createScheduleRequest> <scheduleDefinition> <scheduleName>My Schedule</scheduleName> <templateName>My Template</templateName> <notificationRequired>false</notificationRequired> <daily></daily> </scheduleDefinition> </createScheduleRequest> </reportingEngineRequest>
Response
In the response to creating a schedule, the response code of
100
indicates that the request completed successfully.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Get a schedule
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <getScheduleRequest> <scheduleName>My Schedule</scheduleName> </getScheduleRequest> </reportingEngineRequest>
Response
In the response to getting a schedule, the response code of
100
indicates that the request completed successfully. The
response returns the name of the schedule, the report template scheduled, and
the schedule (daily).
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <getScheduleResponse>8 <scheduleDefinition>9 <scheduleName>My Schedule</scheduleName>10 <templateName>My Template</templateName>11 <notificationRequired>false</notificationRequired>12 <daily></daily>13 </scheduleDefinition>14 </getScheduleResponse>15</reportingEngineResponse>
Update a schedule
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <updateScheduleRequest> <scheduleDefinition> <scheduleName>My Schedule</scheduleName> <templateName>My Template</templateName> <notificationRequired>false</notificationRequired> <daily/> </scheduleDefinition> </updateScheduleRequest> </reportingEngineRequest>
Response
In the response to updating a schedule, the response code of
100
indicates that the request completed successfully.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Delete a schedule
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <deleteScheduleRequest> <scheduleName>My Schedule</scheduleName> </deleteScheduleRequest> </reportingEngineRequest>
Response
In the response to deleting a schedule, the response code of
100
indicates that the request completed successfully.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7</reportingEngineResponse>
Run a transaction ID search
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <runSearchRequest> <searchName>TransactionIDSearch</searchName> <reportParam> <paramName>transaction_id</paramName> <paramValue>V89A0A000264</paramValue> </reportParam> <pageSize>50</pageSize> </runSearchRequest> </reportingEngineRequest>
Response
In the response to running the transaction ID search, the
responseCode
of 100 indicates that the report completed
successfully. The reportId
132 returned is used to uniquely
identify this report in future calls to the Reporting API.
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <runSearchResponse>8 <reportId>132</reportId>9 <statusCode>3</statusCode>10 <statusMsg>Report has completed successfully</statusMsg>11 </runSearchResponse>12</reportingEngineResponse>
Run a profile - Next payment date report
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <runReportRequest> <reportName>RBProfileNPDReport</reportName> <reportParam> <paramName>start_date</paramName> <paramValue>2014-06-22 00:00:00</paramValue> </reportParam> <reportParam> <paramName>end_date</paramName> <paramValue>2015-08-30 00:00:00</paramValue> </reportParam> <pageSize>50</pageSize> </runReportRequest> </reportingEngineRequest>
Response
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <runReportResponse>8 <reportId>132</reportId>9 <statusCode>3</statusCode>10 <statusMsg>Report has completed successfully</statusMsg>11 </runReportResponse>12</reportingEngineResponse>
Run a profile - Profile modified date report
Request
1<?xml version="1.0" encoding="UTF-8"?> <reportingEngineRequest> <authRequest> <user></user> <vendor></vendor> <partner></partner> <password></password> </authRequest> <runReportRequest> <reportName>RBProfilePMDReport</reportName> <reportParam> <paramName>start_date</paramName> <paramValue>2013-06-22 00:00:00</paramValue> </reportParam> <reportParam> <paramName>end_date</paramName> <paramValue>2013-08-30 00:00:00</paramValue> </reportParam> <pageSize>50</pageSize> </runReportRequest> </reportingEngineRequest>
Response
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>2<reportingEngineResponse>3 <baseResponse>4 <responseCode>100</responseCode>5 <responseMsg>Request has completed successfully</responseMsg>6 </baseResponse>7 <runReportResponse>8 <reportId>132</reportId>9 <statusCode>3</statusCode>10 <statusMsg>Report has completed successfully</statusMsg>11 </runReportResponse>12</reportingEngineResponse>