canonical: https://jentic.com/apis/swaggerhub.bnsf-logistics/swaggerhub-bnsf-logistics

# Bnsf Logistics Blume Logistics Dispatch Manager API

Blume Logistics Dispatch Manager API. Category: Blume Logistics. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create work order, update work order. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create Work Order
- Update Work Order
- Cancel Work Order
- Query and filter Blume Logistics Dispatch Manager API records by parameters
- Monitor Blume Logistics Dispatch Manager API operational status and events

## Use cases

### Developer Tools Operations

Use the Blume Logistics Dispatch Manager API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including create work order, update work order, cancel work order.

Example prompt: Call POST /create to create work order

### Automated blume Management

Automate blume operations by combining multiple Blume Logistics Dispatch Manager API endpoints. Agents can update work order and then cancel work order in a single workflow.

Example prompt: Call PUT /update to update work order, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Blume Logistics Dispatch Manager 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 work order', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/create` | Create Work Order |
| PUT | `/update` | Update Work Order |
| POST | `/cancel` | Cancel Work Order |

## Key resources

- **blume** — Dispatch Manager API
- **workorder** — Operations related to workorder

## Why Jentic

- **Setup:** Wiring the Blume Logistics Dispatch Manager API by hand means learning its apikey header auth, targeting the Blume Global work-orders host, and handling the create, update, and cancel calls with retries yourself. Through Jentic you install once, import the Blume Logistics Dispatch Manager API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The work-order operations carry their target in the request body rather than a resource id in the URL path, so scope the agent to the operations it needs, such as POST /create and PUT /update. You choose the allowed set, so cancelling a work order with POST /cancel is not included unless you add it.
- **Credential handling:** Your Blume Logistics 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 dispatch work order' or 'update a work order', and Jentic returns the matching Blume Logistics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Blume Logistics Dispatch Manager API use?

The Blume Logistics Dispatch Manager API uses an API key passed in the `apikey` 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 work order with the Blume Logistics Dispatch Manager API?

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

### What are the rate limits for the Blume Logistics Dispatch Manager 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 work order through Jentic?

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

### How many endpoints does the Blume Logistics Dispatch Manager API have?

The Blume Logistics Dispatch Manager API exposes 3 endpoints covering blume, workorder operations.

### Can I limit what my agent is allowed to do with the Blume Logistics Dispatch Manager API?

Yes. Because you run Jentic One yourself, your own rules decide which of the work-order operations the agent may call and which credentials it can use. This API has three operations, POST /create, PUT /update, and POST /cancel, so you can allow only the ones the agent needs, for example creating and updating work orders while leaving POST /cancel out of the allowed set. The API key you store stays with your self-hosted instance and is injected only for the operations you have permitted.