geoCapture API

Name: geoCapture API
Brand: geoCapture API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee ManagementapiKey129 EndpointsREST

For Agents

Read and write geoCapture workforce data — time tracking, GPS positions, cost bookings, wage groups, and tool assignments — for German field-service operations.

Install Jentic One Beta

Connect the geoCapture API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the geoCapture API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with geoCapture API.

Fetch and upsert container records, including container inquiries used in field operations

Pull cost-booking data and trigger export jobs for accounting hand-off

Manage wage groups and their per-tool cost settings for accurate job costing

GET STARTED

Start building with geoCapture API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for geoCapture API, keeping it validated and agent-ready. geoCapture is a German workforce-management platform for time tracking, GPS tracking, and field-service disposition used by construction, logistics, and trades businesses. The API exposes 129 endpoints covering containers, cost bookings, tools, wage groups, trackers, and dispatch operations, with both fetch (read) and upsert (write) variants for most resources. It is designed to integrate geoCapture data into payroll, ERP, and accounting systems.

Use Cases

Patterns agents use geoCapture API for, with concrete tasks.

★ Payroll Hand-Off

Construction and trades businesses running geoCapture for time tracking need clean payroll records each pay period. The cost-booking endpoints — fetch and the export trigger pair — produce a structured extract of hours worked by employee and project, ready for hand-off to DATEV or another payroll system. The export flow runs createExport, startExport, then fetchExportData.

Trigger /cost_booking/createExport for the current pay period, start it via /cost_booking/startExport, then poll /cost_booking/fetchExportData for the file

Fleet GPS Reporting

Operations managers monitor where field crews and tools are located in real time. The tracker endpoints expose GPS-enabled equipment with cost settings, letting an integration build a daily fleet-utilisation report or pipe live positions into a dispatch dashboard alongside job allocations.

Pull tracker cost settings via /tracker_cost_setting/fetch and join them with active job assignments to produce a daily utilisation report

Job Costing Synchronisation

Project managers reconciling job costs need wage groups, tool costs, and container assignments aligned across geoCapture and the back-office ERP. The wage_group, tool_cost_setting, and container fetch/upsert pairs let an integration both pull current state into the ERP and push corrections back when project codes change mid-engagement.

Fetch wage groups via /wage_group/fetch, compare with the ERP's project mapping, and upsert any corrections via /wage_group/upsert

AI Agent Field-Service Dispatcher

An AI agent acting as a dispatcher needs read access to crew locations and write access to disposition records. Through Jentic the agent searches for 'get geoCapture tracker data' or 'create a container inquiry', loads the schema, and executes — keeping the apitoken in the vault rather than the agent context.

Search Jentic for 'fetch geoCapture trackers', execute /tracker_cost_setting/fetch, and assign the nearest crew to the next open job

Key Endpoints

129 endpoints — jentic publishes the only available openapi specification for geocapture api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/container/fetch

Fetch container records

POST

/container_inquiry/upsert

Create or update a container inquiry

POST

/cost_booking/fetch

Fetch cost-booking records

POST

/cost_booking/createExport

Create a cost-booking export job

POST

/cost_booking/startExport

Start a previously-created export job

POST

/cost_booking/fetchExportData

Fetch the data of a completed export

POST

/wage_group/fetch

Fetch wage group definitions

POST

/tracker_cost_setting/fetch

Fetch tracker cost settings for the fleet

POST

/container/fetch

Fetch container records

POST

/container_inquiry/upsert

Create or update a container inquiry

POST

/cost_booking/fetch

Fetch cost-booking records

POST

/cost_booking/createExport

Create a cost-booking export job

POST

/cost_booking/startExport

Start a previously-created export job

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

geoCapture apitoken values live in the Jentic vault encrypted with the customer-scoped key. Jentic injects the token as the apitoken query parameter at execution time — agents see operation names and parameters but never the raw secret.

Intent-based discovery

Agents search by intent ('fetch geoCapture cost bookings', 'upsert container inquiry') and Jentic returns the matching operation across the 129-endpoint surface, so the agent doesn't need to know geoCapture's resource naming conventions.

Time to first call

Direct geoCapture integration: 1-2 weeks to wrap auth, the fetch/upsert pattern, and the export flow across the resources you care about. Through Jentic: under 1 hour to call the operations you need.

FAQs

Specific to using geoCapture API through Jentic.

Why is there no official OpenAPI spec for geoCapture API?

geoCapture documents its API in HTML help pages but does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call geoCapture API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the geoCapture API use?

geoCapture uses an API token passed as the apitoken query parameter on every request. Through Jentic the token is stored encrypted in the vault and attached to outgoing requests at execution time, so the apitoken never appears in agent context or logs.

Can I export cost bookings to DATEV or another payroll system?

Yes. The cost-booking export uses a three-step flow: POST /cost_booking/createExport to define the export, POST /cost_booking/startExport to run it, then POST /cost_booking/fetchExportData to retrieve the file. The output structure aligns with DATEV-style payroll imports.

Does the geoCapture API expose GPS tracker positions?

Yes. The tracker_cost_setting and related tracker endpoints expose configuration and position data for GPS-enabled trackers attached to vehicles and equipment, useful for fleet utilisation reporting and dispatch.

What are the rate limits for the geoCapture API?

The OpenAPI spec does not declare explicit rate limits. geoCapture is a tenant-isolated SaaS — practical limits depend on the customer's contract, so coordinate large export jobs with the geoCapture account manager and avoid tight polling on /cost_booking/fetchExportData.

How do I sync wage groups into our ERP through Jentic?

Run pip install jentic, search Jentic for 'fetch geoCapture wage groups', and call /wage_group/fetch. After mapping the records to your ERP project codes, push corrections back via /wage_group/upsert in the same Jentic session.

geoCapture API

Connect the geoCapture API to your agent

Capabilities

Start building with geoCapture API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs