Send data to the BIM or drone ingest APIs

Upload building models and aerial surveys, and track what the platform did with them.

BIM models and drone flights follow the same ingest shape as 360 captures: POST the files, then query what the platform produced.

Ingest authentication is not enforced server-side

Both specifications declare bearer authentication and the ingest service does not enforce it server-side. Send the header on every request, and do not treat it as an access control.

BIM

POST/{project_id}/uploadBIM Ingest API

Uploads a BIM model for a project.

curl -X POST "https://ingest.evercam.io/bim/$PROJECT_ID/upload" \
  -H "Authorization: Bearer $EVERCAM_TOKEN" \
  -F "file=@model.ifc"

GET/uploads/BIM Ingest API

The BIM uploads recorded so far.

The BIM API is deliberately small — four operations covering upload, listing, archive retrieval and deletion.

Drone

Drone ingest is richer, because a flight yields measurable data rather than a single artefact.

POST/{project_id}/uploadDrone Ingest API

Uploads a drone dataset for a project.

GET/uploads/Drone Ingest API

Drone uploads and their processing state.

GET/queueDrone Ingest API

What is currently being processed.

Processing is asynchronous, so poll the queue rather than expecting the upload response to contain results.

Derived data

Once a flight is processed, the drone API exposes what was measured:

GET/api/{project_id}/flight-imagesDrone Ingest API

The images captured on a flight.

GET/api/{project_id}/flight-available-featuresDrone Ingest API

Which derived features are available for a project.

POST/api/{project_id}/calculate-measuring-operationDrone Ingest API

Runs a measurement — volumes, distances and areas — over processed data.

curl -H "Authorization: Bearer $EVERCAM_TOKEN" \
  "https://ingest.evercam.io/drone/api/$PROJECT_ID/flight-available-features"

Check available features before requesting a measurement — what a flight supports depends on how it was captured and processed.

Reference

Full operation lists: BIM · Drone.