Fulcrum API

Name: Fulcrum API API
Brand: Fulcrum API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms SurveysapiKey13 EndpointsREST

For Agents

Manage Fulcrum forms and field-collection records, list users, and pull photos captured in the mobile app.

Connect the Fulcrum API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fulcrum 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.

Install Jentic One Beta (Self-Hosted)

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

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 Fulcrum API API.

Create and update Fulcrum forms that drive mobile field data collection

Submit new field records against an existing form

Retrieve a single record with all captured field values

List users in the Fulcrum organisation for assignment and audit

GET STARTED

Start building with Fulcrum API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Fulcrum API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Fulcrum API, keeping it validated and agent-ready. Fulcrum is a mobile data collection platform used for field inspections, asset surveys, and geospatial data capture. This streamlined edition of the API exposes 13 endpoints centred on apps (forms), records, users, and photo retrieval, ideal for read-and-write integrations that do not need the full object surface. Authentication uses an X-ApiToken header.

Use Cases

Patterns agents use Fulcrum API API for, with concrete tasks.

★ Field Inspection Submission

When a back-office system needs to seed a Fulcrum field crew with inspection records, an integration calls POST /records with the form_id, geometry, and form_values payload. Crews then complete the records on the mobile app and the office can pull them back via GET /records/{id} for downstream reporting.

Create a Fulcrum record on form_id abc123 with a point geometry and form_values for a site inspection

Form Lifecycle Management

Operations teams keep field forms in sync with policy. The forms endpoints support GET /forms to list current templates, PUT /forms/{id} to roll out updated questions, and DELETE /forms/{id} to retire deprecated workflows. Schema changes propagate to the Fulcrum mobile clients on next sync.

Update form abc123 with a new required field and verify the response shows the updated schema

Photo Retrieval for Reports

Inspection photos captured on the Fulcrum mobile app can be pulled by access_key via GET /photos/{access_key} for full size or GET /photos/{access_key}/large for a downsized variant. This lets a reporting service build PDF or HTML reports that embed the original field imagery.

Download the large variant of a photo by access_key for inclusion in an inspection report

Agent-Driven Field Operations

An AI agent receives a request to brief on yesterday's inspections, lists records via GET /records filtered by date, retrieves the highest-priority record in detail, and downloads the most relevant photo via /photos. Through Jentic the X-ApiToken stays in the vault.

Search Jentic for 'list fulcrum records', load GET /records, execute filtered by created_after, and summarise the top three

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/forms

List forms in the organisation

POST

/forms

Create a new form

PUT

/forms/{id}

Update an existing form

POST

/records

Submit a new record against a form

GET

/records/{id}

Retrieve a record with field values

GET

/users

List users in the organisation

GET

/photos/{access_key}/large

Download a large preview of a captured photo

GET

/forms

List forms in the organisation

POST

/forms

Create a new form

PUT

/forms/{id}

Update an existing form

POST

/records

Submit a new record against a form

GET

/records/{id}

Retrieve a record with field values

GET

Why though Jentic?

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

Credential isolation

Fulcrum X-ApiToken values are stored encrypted in the Jentic MAXsystem vault. Agents call operations through scoped execution tokens, and the raw token is injected into the X-ApiToken header only at execution time.

Intent-based discovery

Agents search Jentic for intents like 'submit a fulcrum record' or 'list fulcrum forms' and Jentic returns the matching POST /records or GET /forms operation with its input schema, so the agent does not have to read field-collection docs.

Time to first call

Direct Fulcrum integration: 1-3 days to model forms, handle geometries, and download photos. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Fulcrum API (full)

Fuller 61-endpoint Fulcrum spec covering projects, memberships, and webhooks

Use the full fulcrum-api spec when the integration needs projects, choice lists, layers, or webhooks beyond the core 13 endpoints

Alternative

KoboToolbox

Open-source field data collection and survey platform

Choose KoboToolbox when the use case is humanitarian or research data collection rather than commercial inspections

Alternative

JotForm

General-purpose online forms platform

Choose JotForm when the team wants browser-only forms without geospatial capture or offline mobile sync

FAQs

Specific to using Fulcrum API API through Jentic.

Why is there no official OpenAPI spec for Fulcrum API?

Fulcrum does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Fulcrum 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 Fulcrum API use?

Fulcrum uses an API token sent as the X-ApiToken header. The token is generated in the Fulcrum web app under integrations. Jentic stores the token encrypted in the MAXsystem vault and injects it into the X-ApiToken header at execution time.

Can I create a record on an existing Fulcrum form?

Yes. POST /records with form_id and a form_values object that conforms to the form schema. Optional latitude, longitude, and altitude fields attach geospatial context. The response includes the created record id.

What are the rate limits for the Fulcrum API?

Fulcrum applies per-account throttling that varies with plan. As a guideline keep concurrent calls under five and back off on any 429 responses; bulk syncs should run sequentially rather than in parallel.

How do I download a record's photo through Jentic?

Search Jentic for 'download a fulcrum photo', load the GET /photos/{access_key} schema (or /photos/{access_key}/large for a smaller variant), and execute with the access_key from the record's photos array.

Which Fulcrum API should I pick — fulcrum or fulcrum-api?

This Fulcrum spec covers the core 13 endpoints for forms, records, users, and photos. Use the fulcrum-api spec when you need the wider 61-endpoint surface including projects, choice lists, memberships, and webhooks.