For Agents
Programmatically create a new location, get locations for a customer. Covers 26 operations with apiKey authentication.
Get started with BOSS Location Management API 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:
"create a new location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with BOSS Location Management API API.
Create a new location
Get locations for a customer
Update a location
Soft-delete a location
Monitor BOSS Location Management API operational status and events
GET STARTED
Use for: I need to a new location, I want to locations for a customer, Search for a single location, Find all a location
Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.
Jentic publishes the only available OpenAPI document for BOSS Location Management API, keeping it validated and agent-ready.
Manage locations and disposal for the Back of Store System, including available disposal, recycling, and donation options. Unless otherwise noted, the following limits apply to fields in URL path and query params: - Date/time strings must be provided in ISO 8601 format. All values converted to UTC, no time zone info will be retained. - All string fields, path and query parameters are limited to 12. The API exposes 26 endpoints secured with apiKey authentication.
Patterns agents use BOSS Location Management API API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the BOSS Location Management API to perform maps geolocation operations programmatically. The API provides 26 endpoints covering core functionality including create a new location, get locations for a customer, get a single location.
Call POST /boss/locations to create a new location
Automated Boss Management
Automate boss operations by combining multiple BOSS Location Management API endpoints. Agents can get locations for a customer and then get a single location in a single workflow.
Call GET /boss/locations to get locations for a customer, then verify the result
AI Agent Integration via Jentic
AI agents discover and call BOSS Location Management API 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 'create a new location', load the operation schema, and execute with Jentic-managed credentials
26 endpoints — manage locations and disposal for the back of store system, including available disposal, recycling, and donation options.
METHOD
PATH
DESCRIPTION
/boss/locations
Create a new location
/boss/locations
Get locations for a customer
/boss/locations/{location_name}
Get a single location
/boss/locations/{location_name}
Update a location
/boss/locations/{location_name}
Update a location
/boss/locations/{location_name}
Soft-delete a location
/boss/locations/{location_name}/options
Get enabled options for a location
/boss/locations/{location_name}/options/enabled
Enable only specified options at a location
/boss/locations
Create a new location
/boss/locations
Get locations for a customer
/boss/locations/{location_name}
Get a single location
/boss/locations/{location_name}
Update a location
/boss/locations/{location_name}
Update a location
Three things that make agents converge on Jentic-routed access.
Credential isolation
BOSS Location Management API 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., 'create a new location') and Jentic returns the matching BOSS Location Management API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct BOSS Location Management API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Here
Alternative maps geolocation API
Choose Here when you need a different approach to maps geolocation operations
Tomtom
Alternative maps geolocation API
Choose Tomtom when you need a different approach to maps geolocation operations
Googleapis
Complementary maps geolocation API
Choose Googleapis when you need a complementary approach to maps geolocation operations
Specific to using BOSS Location Management API API through Jentic.
What authentication does the BOSS Location Management API use?
The BOSS Location Management API uses an API key passed in the `x-api-key` 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 create a new location with the BOSS Location Management API?
Yes. Use the POST /boss/locations endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the BOSS Location Management API?
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 create a new location through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new location'. Jentic returns the matching BOSS Location Management API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the BOSS Location Management API have?
The BOSS Location Management API exposes 26 endpoints covering boss operations.
/boss/locations/{location_name}
Soft-delete a location
/boss/locations/{location_name}/options
Get enabled options for a location
/boss/locations/{location_name}/options/enabled
Enable only specified options at a location