canonical: https://jentic.com/apis/geocapture.net/geocapture # geoCapture API 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. ## For AI agents Read and write geoCapture workforce data - time tracking, GPS positions, cost bookings, wage groups, and tool assignments - for German field-service operations. ## Scope Does not handle payroll calculation, tax filing, or accounting ledgers - use for geoCapture workforce data fetch and upsert operations only. ## Capabilities - 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 - Read GPS tracker positions and tracker cost configurations for fleet visibility - Synchronise time-tracking and disposition records into payroll or ERP systems ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'fetch geoCapture trackers', execute `/tracker_cost_setting/fetch`, and assign the nearest crew to the next open job ## Key endpoints | 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 | ## Key resources - **Containers** — Fetch and upsert containers used in field operations and the inquiries against them - **Cost Bookings** — Pull cost-booking data and run export jobs for payroll or accounting hand-off - **Wage Groups** — Manage wage groups and their per-tool cost configurations - **Trackers** — Read GPS tracker positions and tracker cost settings for fleet visibility - **Tools** — Manage tool cost settings to feed accurate job costing ## Why Jentic - **Setup:** Wiring the geoCapture API by hand means registering your apitoken, appending it as a query parameter on every request, and mapping fetch and upsert calls across a large POST surface yourself. Through Jentic you install once, import geoCapture from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** geoCapture's operations like `/container/fetch` and `/container_inquiry/upsert` take their target in the request body rather than the URL path, so scope the agent to the operations it needs, such as fetching cost bookings. You choose the operations it may call, so write actions like upserting a container inquiry or starting an export are not included unless you add them. - **Credential handling:** Your geoCapture apitoken is stored once, encrypted, by your own Jentic One instance and attached as the apitoken query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'fetch geoCapture cost bookings' or 'upsert a container inquiry', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without learning geoCapture's resource naming. ## Related APIs - **Calendly** — Schedule field-service appointments that then drive geoCapture time tracking - **Twilio** — Send SMS dispatch messages or arrival notifications based on geoCapture tracker data - **FedEx** — Generate shipping labels for containers tracked through geoCapture ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the geoCapture API? Yes. Because you run Jentic One yourself, your own rules decide which geoCapture operations and credentials the agent can use, and you grant only the specific operations it needs. You can, for example, allow read-only calls such as `/cost_booking/fetch` or `/container/fetch` while withholding write actions like `/container_inquiry/upsert` or `/cost_booking/startExport.` Since geoCapture takes its target in the request body rather than the URL path, this operation-level scoping is what determines exactly what the agent can call.