Locations

Name: Locations API
Brand: Locations
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey5 EndpointsREST

For Agents

Programmatically addresslookup, getcountries. Covers 5 operations with apiKey authentication.

Use for: I need to addresslookup, I want to getcountries, Search for getcountry, Find all getcurrencies

Connect the Locations to your agent

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

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

addressLookup

getCountries

getCountry

getCurrencies

getCurrency

GET STARTED

Start building with Locations API

Explore with Jentic

View OpenAPI Document

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

The Locations API is a collection of methods that support geographical information. The first method is an address lookup service for UK addresses. This service can be used to provide a new customer with a list of possible addresses from which they can populate a registration form. The API exposes 5 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use Locations API for, with concrete tasks.

★ CRM Operations

Use the Locations to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including addresslookup, getcountries, getcountry.

Call GET /address/lookup/ to addresslookup

Automated Address Management

Automate address operations by combining multiple Locations endpoints. Agents can getcountries and then getcountry in a single workflow.

Call GET /countries/ to getcountries, then verify the result

AI Agent Integration via Jentic

AI agents discover and call 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 apiKey tokens manually.

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

Key Endpoints

5 endpoints — the locations api is a collection of methods that support geographical information.

METHOD

PATH

DESCRIPTION

GET

/address/lookup/

addressLookup

GET

/countries/

getCountries

GET

/countries/{countryCode}

getCountry

GET

/currencies/

getCurrencies

GET

/currencies/{currencyCode}

getCurrency

GET

/address/lookup/

addressLookup

GET

/countries/

getCountries

GET

/countries/{countryCode}

getCountry

GET

/currencies/

getCurrencies

GET

/currencies/{currencyCode}

getCurrency

Why though Jentic?

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

Credential isolation

Locations apiKey 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., 'addresslookup') and Jentic returns the matching Locations operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct 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

Hubspot

Alternative crm API

Choose Hubspot when you need a different approach to crm operations

Alternative

Salesforce

Alternative crm API

Choose Salesforce when you need a different approach to crm operations

Complementary

Pipedrive

Complementary crm API

Choose Pipedrive when you need a complementary approach to crm operations

Complementary

Zoho

Complementary crm API

Choose Zoho when you need a complementary approach to crm operations

FAQs

Specific to using Locations API through Jentic.

What authentication does the Locations use?

The Locations uses an API key passed in the `apiKey` header. 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 addresslookup with the Locations?

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

What are the rate limits for the 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 addresslookup through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'addresslookup'. Jentic returns the matching Locations operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Locations have?

The Locations exposes 5 endpoints covering address, countries, currencies operations.