API Locations

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

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces Searchoauth23 EndpointsREST

For Agents

Programmatically getlocations, getlocationbyid. Covers 3 operations with oauth2 authentication.

Quickstart

Get started with API Locations in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"getlocations"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with API Locations API.

getLocations

getLocationById

getLatLong

Query and filter API Locations records by parameters

Monitor API Locations operational status and events

GET STARTED

Start building with API Locations API

Explore with Jentic

View OpenAPI Document

Use for: I need to getlocations, I want to getlocationbyid, Search for getlatlong, List all records from API Locations

Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.

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

Ferguson's Location API for exchanging location data with internal Ecommerce platforms and 3rd party companies.    > Fetch summary list of locations via pagination: <details> <summary>Click to see example response</summary> </details> --- --- > Fetches details for a specific location based on id and application scope: For external users, this endpoint features a refined response. <detail. The API exposes 3 endpoints secured with oauth2 authentication.

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 though Jentic?

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

Credential isolation

API Locations oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'getlocations') and Jentic returns the matching API Locations operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Locations integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Here

Alternative maps geolocation API

Choose Here when you need a different approach to maps geolocation operations

Alternative

Tomtom

Alternative maps geolocation API

Choose Tomtom when you need a different approach to maps geolocation operations

Complementary

Googleapis

Complementary maps geolocation API

Choose Googleapis when you need a complementary approach to maps geolocation operations

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.