Re-imports all kickout files from a completed bill import task as a single new import
Use this endpoint to retry bills that were kicked out during a previous import. All kickout
files from the specified task are zipped together and re-imported as a new import task.
The original task must have a status of “Completed with kickouts” and be of type Bill Import.
Returns a new task GUID — use GET /task/{guid} to check progress and results.
Requires Bills and Batches Create permission.
Request Headers
| Header | Value | Required | Description |
|---|---|---|---|
| ECI-ApiKey | string | Yes | Your API key. See Authentication. |
| Content-Type | application/json | Yes | All requests must specify JSON content type, including the request body. |
Path Parameters
| Name | Description | Type | Required |
|---|---|---|---|
| taskGuid | The GUID of a bill import task that completed with kickouts | string (uuid) | Required |
Request Body
BillKickoutImportRequest
| Property | Description | Type | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| batchSettings | BatchSettings | |||||||||||||||||||
|
BatchSettings properties
|
||||||||||||||||||||
| comment | Optional comment to explain why the audit is being auto resolved | string | ||||||||||||||||||
| importNote | Optional note/comment. | string | ||||||||||||||||||
| saveAsResolved | Optional property to indicate if failed audits automatically get marked as resolved | boolean | ||||||||||||||||||
Example Request Body
{ "batchSettings": { "batchMode": "string", "existingOpenBatchId": 1, "leaveExistingBatchesOpen": false, "newBatchCode": "string", "pendingBatchId": 1
}, "comment": "string", "importNote": "string", "saveAsResolved": false
}
Responses
200
OK
The request succeeded and the response body contains the requested data.
Response Body Parameters
GuidResponse
| Property | Description | Type |
|---|---|---|
| taskGUId | A guid that identifies the current task | string (uuid) |
Example Response
{ "taskGUId": "string"
}
404
Not Found
The requested resource was not found. Verify the ID or path is correct.