canonical: https://jentic.com/apis/swaggerhub.smartersorting/swaggerhub-smartersorting

# Smartersorting BOSS Location Management API

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.

## For AI agents

Programmatically create a new location, get locations for a customer. Covers 26 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a new location', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /boss/locations | Create a new location |
| GET | /boss/locations | Get locations for a customer |
| GET | /boss/locations/{location_name} | Get a single location |
| PUT | /boss/locations/{location_name} | Update a location |
| PATCH | /boss/locations/{location_name} | Update a location |
| DELETE | /boss/locations/{location_name} | Soft-delete a location |
| GET | /boss/locations/{location_name}/options | Get enabled options for a location |
| PUT | /boss/locations/{location_name}/options/enabled | Enable only specified options at a location |

## Key resources

- **Boss** — Operations for boss

## Why Jentic

- **Setup:** Wiring the BOSS Location Management API by hand means setting up its x-api-key header auth, pointing at the staging host, and handling location CRUD calls and retries yourself. Through Jentic you install once, import BOSS Location Management from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the location name in the URL path (/boss/locations/{location_name}/...), so a rule can pin your agent to one location: it can read that location and toggle its options and nothing else. You choose the operations it may call, so destructive ones like deleting a location are not included unless you add them.
- **Credential handling:** Your BOSS Location Management API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new location' or 'enable options for a location', and Jentic returns the matching BOSS Location Management operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the BOSS Location Management API?

Yes. Jentic One is self-hosted by you, so your own rules decide which BOSS Location Management operations and credentials the agent may use. Because the API carries the location name in the URL path (/boss/locations/{location_name}/...), you can pin the agent to a single location and allow only read and option-toggling calls such as GET /boss/locations/{location_name} and PUT /boss/locations/{location_name}/options/enabled. Destructive operations like DELETE /boss/locations/{location_name} stay out of the agent's reach unless you explicitly add them.