GET Async Batch Job Errors enterprise only
Note
This is a blocking call that streams CSV error data with chunked transfer-encoding.
The batch job errors service allows you to retrieve error information for a batch job. Errors are returned as CSV data with detailed error information for each failed record.
Resource URL
https://www.mapquestapi.com/geocoding/v1/batch/jobs/{jobId}/errors
Resource Information
| Response Formats | CSV |
| Authentication | Yes (Requires Key) |
| Rate Limited | Yes |
Request Parameters
| Request Parameter | Description | Required |
|---|---|---|
| key | The API Key, which is needed to make requests to MapQuest services. | Yes |
Note: The jobId is specified in the URL path, not as a query parameter.
Response Format
The response is returned as:
- Content-Type:
text/plain - Transfer-Encoding:
chunked - Format: CSV with pipe (
|) delimited fields
CSV Field Descriptions
| Field | Type | Description |
|---|---|---|
recId | string | Record identifier (matches input recId or auto-generated) |
errorCode | number | Numeric error code indicating the type of error |
errorMessage | string | JSON string containing detailed error information |
Error Message Structure
The errorMessage field contains a JSON object with the following structure:
json
{
"status": 999,
"recordId": "InputLine_1",
"title": "Illegal input line",
"cause": "The input line does not conform to given input format for job.",
"action": "Please check format for job record and resubmit in new job.",
"jobRecord": "Denver,,CO,,"
}| Field | Type | Description |
|---|---|---|
status | number | Error status code |
recordId | string | Identifier of the failed record |
title | string | Brief error title |
cause | string | Detailed explanation of what caused the error |
action | string | Recommended action to resolve the error |
jobRecord | string | The original input record that caused the error |
Example Request
bash
curl -X GET "https://www.mapquestapi.com/geocoding/v1/batch/jobs/abc123-def456-ghi789/errors?key=YOUR_API_KEY"Example Response
The response is a CSV stream with the following format:
csv
recId|errorCode|errorMessage
InputLine_1|999|{"status":999,"recordId":"InputLine_1","title":"Illegal input line","cause":"The input line does not conform to given input format for job.","action":"Please check format for job record and resubmit in new job.","jobRecord":"Denver,,CO,,"}
InputLine_2|999|{"status":999,"recordId":"InputLine_2","title":"Illegal input line","cause":"The input line does not conform to given input format for job.","action":"Please check format for job record and resubmit in new job.","jobRecord":"Boulder,,CO,,"}
InputLine_3|999|{"status":999,"recordId":"InputLine_3","title":"Illegal input line","cause":"The input line does not conform to given input format for job.","action":"Please check format for job record and resubmit in new job.","jobRecord":"Aspen,,CO,,"}Important Notes
- Blocking Call: This is a synchronous request that returns immediately with error data
- Authentication: Same API key as other endpoints, passed as query parameter
- Job ID: The job ID is passed in the URL path, not as a query parameter
- Error Availability: Errors are only available when the job has failed records
- Streaming Response: Error data is streamed with chunked transfer-encoding
- CSV Format: Errors are returned as pipe-delimited CSV data
- Content-Type: Response uses
text/plaincontent type - Empty Response: If no errors occurred, this endpoint will return an empty CSV with headers only