Skip to main content
POST
Load a file of locations

Authorizations

X-Session-Token
string
header
required

Session token for authentication.

Body

application/vnd.api+json

The file to load, and how to read it.

The file itself is not sent here. Upload it first with POST /v3/uploads and name the id it returns as upload_id: a 30,000-row CSV is a binary, and the same two-stage ingest already serves videos, documents and certificates. The upload is consumed by this request, and the import keeps its own copy of the bytes, so the hour-long upload expiry cannot outrun a queued import.

The requester is taken from the authenticated principal rather than accepted here, so an import can never be attributed to somebody else.

data
object
required

Response

An individual location import.

JSON API response object

data
object
required

One bulk load of locations from an uploaded CSV, and what became of every row.

The record is the import's audit trail, and that is by design rather than by accident: the bulk write path emits no per-row events, because a per-row event for a 30,000-row file would put 30,000 messages on the platform's bus for one upload. So this record answers "who loaded what, and what did it do" on its own.

jsonapi
object
required
included
object[]

Related resources that can be included when a location import is returned.

An organisation