Ferguson Api API Locations

Name: API Locations API
Brand: API Locations
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces Searchoauth23 Endpoints

Install Jentic One Beta

Connect the API Locations to your agent

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

getLocations

getLocationById

getLatLong

Query and filter API Locations records by parameters

GET STARTED

Start building with API Locations API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Maps and Geolocation Operations

Use the API Locations to perform maps geolocation operations programmatically. The API provides 3 endpoints covering core functionality including getlocations, getlocationbyid, getlatlong.

Call GET /v2/locations to getlocations

Automated Location Summary Management

Automate location summary operations by combining multiple API Locations endpoints. Agents can getlocationbyid and then getlatlong in a single workflow.

Call GET /v2/locations/{locationId} to getlocationbyid, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Locations endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Search Jentic for 'getlocations', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — ferguson's location api for exchanging location data with internal ecommerce platforms and 3rd party companies.

METHOD

PATH

DESCRIPTION

GET

/v2/locations

getLocations

GET

/v2/locations/{locationId}

getLocationById

GET

/v2/locations/geocode/{outputFormat}

getLatLong

GET

/v2/locations

getLocations

GET

/v2/locations/{locationId}

getLocationById

GET

/v2/locations/geocode/{outputFormat}

getLatLong

Why Jentic?

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

Credential isolation

Your Ferguson client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a branch location' or 'geocode an address', and Jentic returns the matching API Locations operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using API Locations API through Jentic.

What authentication does the API Locations use?

The API Locations uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I getlocations with the API Locations?

Yes. Use the GET /v2/locations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Locations?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I getlocations through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getlocations'. Jentic returns the matching API Locations operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Locations have?

The API Locations exposes 3 endpoints covering location summary, location detail, geocode operations.

Can I limit what my agent is allowed to do with the API Locations?

Yes. Because you self-host Jentic One, your own rules decide which API Locations operations and credentials the agent may use. Since the location id sits in the URL path (GET /v2/locations/{locationId}), you can pin the agent to a single location so it reads that one and nothing else. You also choose which operations it may call, so listing every location via GET /v2/locations or geocoding an address via the geocode endpoint stays off limits unless you add it.

Ferguson Api API Locations

Connect the API Locations to your agent

Capabilities

Start building with API Locations API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs