Bnsf Logistics Blume Logistics Dispatch Manager API
Community OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically create work order, update work order. Covers 3 operations with apiKey authentication.
Use for: I need to work order, I want to work order, Search for cancel work order, List all records from Blume Logistics Dispatch Manager API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Blume Logistics Dispatch Manager API. Category: Blume Logistics. The API exposes 3 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Blume Logistics Dispatch Manager API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blume Logistics Dispatch Manager API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.bnsf-logistics%2Fswaggerhub-bnsf-logistics" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.bnsf-logistics%2Fswaggerhub-bnsf-logistics" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Blume Logistics Dispatch Manager API.
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
Patterns agents use Blume Logistics Dispatch Manager API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'create work order', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — blume logistics dispatch manager api.
METHOD
PATH
DESCRIPTION
POST
/create
Create Work Order
PUT
/update
Update Work Order
POST
/cancel
Cancel Work Order
POST
/create
Create Work Order
PUT
/update
Update Work Order
POST
/cancel
Cancel Work Order
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Blume Logistics Dispatch Manager API through Jentic.
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.
GET STARTED