Platform / API
API
Read your ground investigation data programmatically. A plain HTTP API returning JSON, read-only by design, so your own systems can pull from GIMLabs without anyone exporting a file.
Endpoints
Your ground data, over plain HTTP
List projects, drill into locations with their coordinates, ground level and final depth, then read any AGS table for a project or a single location. JSON in a consistent envelope, so anything that can make a web request can use it: a Python script, a BI tool, a GIS pipeline, or a scheduled sync into your warehouse. Available on Pro.
Keys & scopes
Keys that can only do what you tick
Mint a key in Product OS with an explicit list of scopes and nothing granted by default. Restrict it to named projects as a second axis, so a leak exposes only what that one integration ever needed. Keys belong to the company rather than the person who made them, and revoking one takes effect on the very next request.
Every feature you need
The complete set of capabilities built to make your team faster, smarter and more confident in the field.
Read-only by design
No endpoint creates, changes or deletes anything, so an API key can never damage a project.
Projects & locations
List projects and their locations, with coordinates, ground level and final depth as numbers.
Any AGS table
Read GEOL, SAMP, ISPT or any other group, for a whole project or a single location.
Scoped keys (Pro)
A key carries an explicit scope list and can do nothing that is not ticked on it.
Project-restricted keys
Limit a key to named projects, so a leak exposes only what that one integration needed.
Incremental sync
Pass updatedSince and get only the rows that have changed since your last run.
Cursor paging
Stable cursors rather than offsets, so pages hold still while rows are added underneath you.
Stable error types
Every failure carries a machine-readable type and a link to the docs. Branch on type, not message.
Visible rate limits
Every response reports your remaining budget, so a client can slow down before it is refused.
Instant revocation
Revoking a key takes effect on the next request. Only a hash is stored, so keys are never recoverable.
Company-owned keys
A key belongs to the company, not its creator, so it keeps working after someone leaves.
Map data
Site boundaries, location groups and marker styling, behind a separate map:read scope.
More from the platform
Each product is built to work on its own and even better together. Mix and match the parts your team needs.
Frequently asked questions
Everything you need to know about GIMLabs. Can't find an answer? We're happy to help.
View all FAQs