Furkot Trips

Name: Furkot Trips API
Brand: Furkot Trips
Availability: InStock

✓ Official Vendor SpecMaps GeolocationRouting Directionsoauth23 EndpointsREST

For Agents

Create and update Furkot road-trip itineraries and synchronise their ordered stop lists, including skipped stops, on behalf of authenticated users via OAuth 2.0.

Connect the Furkot Trips to your agent

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

Create or update a multi-day Furkot road trip with named waypoints and dates via /trip

Add or modify stops on an existing trip identified by trip_id through /trip/{trip_id}/stop

Track stops the traveller has chosen to skip using /trip/{trip_id}/skipped

Authenticate third-party trip integrations through OAuth 2.0 authorization-code or implicit flows

GET STARTED

Start building with Furkot Trips API

Explore with Jentic

View OpenAPI Document

The Furkot Trips API exposes programmatic access to multi-day road-trip itineraries built in the Furkot trip planner, focusing on creating and updating trips and synchronising the stop list including skipped stops. The API is OAuth 2.0 protected with both authorization-code and implicit flows, so third-party apps can act on behalf of Furkot users without handling passwords. The three current endpoints cover trip-level operations and stop-level mutations, returning Furkot's structured trip and stop models that include geocoded waypoints, dates, and ordering. The service is targeted at travel apps, RV planners, and itinerary tools that want to push or pull Furkot road-trip data alongside their own content.

Use Cases

Patterns agents use Furkot Trips API for, with concrete tasks.

★ Itinerary Sync from a Travel Planner

Push a curated multi-stop itinerary from a third-party travel app into Furkot by calling /trip to create the trip and then /trip/{trip_id}/stop for each waypoint, so the traveller can use Furkot's mobile features for navigation, mileage, and lodging suggestions on the road. OAuth 2.0 authorization-code flow keeps user credentials in Furkot.

Authorise the user via OAuth, then call /trip to create a trip and /trip/{trip_id}/stop for each of three destinations from the user's saved list.

RV Detour Handling

When an RV-focused companion app detects that the user has skipped a planned stop, it calls /trip/{trip_id}/skipped to record the skip in Furkot so the remaining itinerary recalculates correctly. Recording skipped stops keeps the Furkot trip in sync with reality without rebuilding the route from scratch.

Call /trip/{trip_id}/skipped with the stop the traveller bypassed and return the updated trip state.

Trip Backup and Versioning

Back up Furkot itineraries into a separate storage system by periodically pulling each user's trips and stop lists through the OAuth-authorised endpoints, then storing the snapshots for restore-on-demand. This keeps trip plans recoverable even if the user accidentally deletes a stop.

Pull the current trip state via /trip and the stop list via /trip/{trip_id}/stop and store both as a JSON snapshot.

Agent-Managed Trip Updates via Jentic

An AI travel-planning agent receives natural-language requests like 'add Yellowstone to my Tuesday trip' and uses Jentic to discover the right Furkot operation, load its schema, and execute the call against the user's authorised account. Jentic handles the OAuth token isolation so the agent never touches the user's credentials.

Search Jentic for 'add a stop to a furkot trip', load /trip/{trip_id}/stop, and execute it for trip_id 12345 with the new waypoint.

Key Endpoints

3 endpoints — the furkot trips api exposes programmatic access to multi-day road-trip itineraries built in the furkot trip planner, focusing on creating and updating trips and synchronising the stop list including skipped stops.

METHOD

PATH

DESCRIPTION

POST

/trip

Create or update a Furkot trip

POST

/trip/{trip_id}/stop

Add or update a stop on a trip

POST

/trip/{trip_id}/skipped

Record stops the traveller has skipped

POST

/trip

Create or update a Furkot trip

POST

/trip/{trip_id}/stop

Add or update a stop on a trip

POST

/trip/{trip_id}/skipped

Record stops the traveller has skipped

Why though Jentic?

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

Credential isolation

Furkot OAuth 2.0 access tokens are stored encrypted in the Jentic vault (MAXsystem) and injected into the Authorization header at execution; the agent receives only scoped tool access, never the user's refresh or access token directly.

Intent-based discovery

Agents search Jentic with intents like 'add a stop to a furkot trip' and Jentic returns the /trip/{trip_id}/stop operation with its parameter schema, so the agent does not need to read Furkot docs.

Time to first call

Direct integration: 1-2 days including OAuth setup, callback handling, and stop synchronisation. Through Jentic: under 1 hour — search, load, execute on a managed token.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GraphHopper Directions API

Routing and turn-by-turn directions API that can supply navigation overlays for Furkot trips.

Choose this when the agent needs raw turn-by-turn directions or alternative-route comparison rather than persistent itinerary management.

Alternative

Route4Me API

Multi-stop route optimisation API used as an alternative when fleet-style optimisation matters more than trip planning.

Pick this when the agent needs vehicle routing problem (VRP) optimisation across many stops rather than user-facing itinerary editing.

FAQs

Specific to using Furkot Trips API through Jentic.

What authentication does the Furkot Trips API use?

Furkot Trips uses OAuth 2.0 with both authorization-code and implicit flows defined in the spec under furkot_auth_access_code and furkot_auth_implicit. Through Jentic, the access token is held in the encrypted vault and injected at request time so the agent never sees it.

Can I add stops to an existing Furkot trip with this API?

Yes. Send the new stop payload to /trip/{trip_id}/stop with a valid OAuth bearer token; the response returns the updated stop list so you can confirm ordering and persistence on your side.

What are the rate limits for the Furkot Trips API?

The OpenAPI spec does not declare rate limits for /trip, /trip/{trip_id}/stop, or /trip/{trip_id}/skipped, and Furkot does not publish numeric quotas at help.furkot.com. Treat the API as best-effort and back off on HTTP 429 responses.

How do I sync a road trip into Furkot through Jentic?

Authorise the user with the Furkot OAuth flow, run a Jentic search for 'create a furkot trip', load /trip, and execute it with your itinerary payload, then call /trip/{trip_id}/stop for each waypoint. Get started at https://app.jentic.com/sign-up.

Does the API let me delete a stop from a trip?

The spec exposes only /trip, /trip/{trip_id}/stop, and /trip/{trip_id}/skipped operations; outright deletion is not part of the published surface, but the skipped endpoint can mark a stop as bypassed during the trip.