Get Batch Imported Events
Get the event details for successful events imported from a batch events 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
Whether to include the schema in the response.
A successful response.
Schema
- Array [
- ]
results object[] optional
Page of events import responses for the batch import
user object optional
The user identifier
session object optional
The session identifier. If the event is attached to a session.
The Fullstory generated identifier for the session to associate the event with.
context object optional
The context in which the events are attached to.
browser object optional
The browser context in which the events are attached to.
mobile object optional
The mobile context in which the events are attached to.
device object optional
The device context in which the events are attached to.
location object optional
The location context in which the events are attached to.
ISO 3166-1 alpha-2 standard country code.
ISO-3166-2 standard region code.
Name of the city.
The event's name.
Optional. The event's timestamp represented in ISO 8601 format. If not provided, the current Fullstory server time will be used.
Optional. The custom event's payload.
schema object optional
Optional. Schema declaration, to define the structure of the data, the schema will override Fullstory's default type inference.
A mapping of field names to their corresponding types.
Total number of records in this batch import
The token that can be used in a subsequent request to fetch the next page of import results
{
"results": [
{
"user": {
"id": "123456789",
"uid": "xyz123"
},
"session": {
"id": "123456789:1298251231"
},
"context": {
"browser": {
"url": "https://app.example.com",
"user_agent": "Example_User_Agent",
"initial_referrer": "https://referrer.example.com"
}
},
"name": "Support Ticket",
"timestamp": "2022-03-15T14:23:23Z",
"properties": {
"id": 424242,
"priority": "Normal",
"source": "Email",
"title": "Account locked out"
}
}
],
"total_records": "1200",
"next_page_token": "asd543="
}
Returned when this API is called while the job 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"
}