Get Batch Import Errors
Get the error message and code for any users that failed from a user import job.
This call is a step in an asynchronous workflow.
Path Parameters
ID that can be used to check the status and retrieve results for the batch import
Query Parameters
The token that can be used in a request to fetch the next page of results
A successful response.
Schema
results object[] optional
The total number of failures for the specified user import
The token that can be used in a subsequent request to fetch the next page of import failures
{
"results": [
{
"message": "The error message",
"code": "error_code",
"user": {
"uid": "xyz123",
"properties": {
"rewards_status": "platinum"
}
}
}
],
"total_records": "1200",
"next_page_token": "asd543="
}
Returned when this API is called while the job that is still processing.
Schema
- any
Returned when invalid input has been provided. Fix the issue and retry.
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "uid is required",
"code": "required_field"
}
Returned when access to the resource is unauthorized.
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "access is unauthorized",
"code": "unauthorized"
}
Returned when access is not allowed due to insufficient permissions.
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "insufficient permissions",
"code": "forbidden"
}
Returned when the resource does not exist.
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "Requested resource does not exist",
"code": "resource_not_found"
}
Returned when the client has exceeded the rate limit for this endpoint. A Retry-After
header will be included with the response. This header will contain the number of seconds that you should wait before attempting to send another request.
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "Too many requests. Client has exceeded the rate limit for this endpoint.",
"code": "too_many_requests"
}
Returned when a server error is encountered
Schema
Long form description of what went wrong
A short snake-cased value that is safe to handle programmatically
{
"message": "Server error was encountered",
"code": "server_error"
}
GET /v2/users/batch/{job_id}/errors
Authorization: ApiKeyAuth
name: Authorizationin: headertype: apiKey
https://api.fullstory.com/v2/users/batch/{job_id}/errors
- cURL
- Python
- Go
- Javascript
curl -L -X GET 'https://api.fullstory.com/v2/users/batch/:job_id/errors' \
-H 'Accept: application/json' \
-H 'Authorization: Basic <API_KEY_VALUE>'
curl -L -X GET 'https://api.fullstory.com/v2/users/batch/:job_id/errors' \
-H 'Accept: application/json' \
-H 'Authorization: Basic <API_KEY_VALUE>'
curl -L -X GET 'https://api.fullstory.com/v2/users/batch/:job_id/errors' \
-H 'Accept: application/json' \
-H 'Authorization: Basic <API_KEY_VALUE>'
curl -L -X GET 'https://api.fullstory.com/v2/users/batch/:job_id/errors' \
-H 'Accept: application/json' \
-H 'Authorization: Basic <API_KEY_VALUE>'