Skip to main content
POST
/
v1
/
risk-score
/
ca-telematics
{
  "job_id": "job_2fb5792c",
  "status": "pending",
  "error_message": ""
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

multipart/form-data
​
file
file
required

Expected CSV Format

  1. Filename & Format

    • Must be a CSV file (.csv extension).
    • The file cannot be empty and cannot contain rows with null (empty) values.

  2. Required Columns

    • latitude (float) WGS84 format (e.g. 37.7749)
    • longitude (float) WGS84 format (e.g. -122.4194)
    • timestamp (datetime in ISO 8601 format, e.g. 2023-01-15T13:45:30Z)

    Optional Column

    • vehicle_id (string,integer or null) if not provided, the vehicle_id will be set to vehicle_1

    You can download a sample file here.

  3. Data Validation & Constraints

    • Extra columns are ignored.
    • Every row must have valid values in each required column (no nulls or missing values).
    • latitude and longitude are used to join external risk data, so they should be accurate real-world coordinates in WGS84 format.
    • timestamp must be parseable in strict ISO 8601 format.
    • Files failing these validations are rejected.
    • The file must be less than 1GB.
    • Files are deleted after request is processed.
​
version
string
required

Version of the risk scoring model used.

Allowed value: "v1"
Examples:

"v1"

​
policy_holder_id
string
required

Unique identifier for the policyholder.

Examples:

"policy-holder-123"

​
naics_code
string | null

Optional NAICS code for the policyholder.

Required string length: 2 - 6
Examples:

"492110"

Response

Successful Response

​
job_id
string
required

Unique identifier for the batch job

Examples:

"job_2fb5792c"

​
status
enum<string>
required

Current status of the job

Available options:
pending,
processing,
completed,
failed,
expired
​
error_message
string | null
required

Error message if job failed

Examples:

""