This endpoint allows users to submit a workflow for bulk routing operations. The request must include the necessary payload for the operation and returns a workflow URL.
HTTP Request
- URL Composition
Base URL: https://api.cloud.precisely.com
Bulk Routing : /v1/routing/bulk-operations
- Supported Methods: POST only
- Rate Limit (Transactions per second): 100
-
Authentication and Input Fields: Data Integrity Suite's APIs provide multiple authentication methods. Whether you want to pass the API Key and Secret directly as part of the Basic Authentication header or use bearer tokens, you can do either using the same header. The two ways of authentication are:
- Basic Authentication (Using API Key and secret)
- Bearer Token Authentication
For more information about authentication, see How to Authenticate and follow the instructions.
Request Body Fields
The below table lists the input fields for Bulk Routing API:
| Field | Type | Required | Description |
|---|---|---|---|
| operation | String | Yes | The routing operation to be performed. Possible values are:
|
| payload | String | Yes | Contains parameters according to the Operation specified. Refer tables below. |
Payload Parameters
| Parameters | Type | Required | Description |
|---|---|---|---|
| fileId | String | Yes | File ID generated via Generate Upload URL endpoint. |
| delimiter | String | No | Delimiter used in the file. If no delimiter is provided, the default pipe separator "|" will be used. For more information, see Supported Delimiters |
Examples
Request
https://api.cloud.precisely.com/v1/routing/bulk-operations
{
"operation": "TRAVEL_BOUNDARY",
"payload": {
"fileId": "5b4d7911-8861-468b-867b-228c0f9b884e",
"delimiter": ","
}
}Response
{
"statusUrl": "https://api.cloud.precisely.com/v1/li/workflows/status/606969c3-a570-495e-88b4-c34790b32201"
}