canonical: https://jentic.com/apis/swaggerhub.truckertools/invoice-api

# Truckertools Invoice Api

Create or update an invoice of a load Overview - Retrieve authentication keys from TruckerTools - Create authentication signatures for each Request - Send invoice updates to TruckerTools Authentication Authentication is done using the provided API Key and a Signature, encrypted using the Secret Key, in the header of the API call. | Sample Keys | | | - | - | | API Key | `f3f4b655b406bfa2e5ea81d02e8. The API exposes 1 endpoints.

## For AI agents

Programmatically access Invoice API resources. Covers 1 operations.

## Scope

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

## Capabilities

- Access Invoice API resources via REST API
- Manage payments data programmatically
- Integrate Invoice API into automated workflows
- Query and filter Invoice API records by parameters
- Monitor Invoice API operational status and events

## Use cases

### Payments Operations

The API provides 1 endpoints for payments operations.

Example prompt: Execute a primary operation against the Invoice API

### Data Retrieval and Monitoring

Query Invoice API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Invoice API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'invoice API', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **Sendinvoice** — Operations for sendInvoice

## Why Jentic

- **Setup:** Wiring the Invoice API by hand means pointing at its scapi.truckertools.com host, choosing between production and staging, and building your own retries around the send invoice call, even though it exposes no auth scheme. Through Jentic you install once, import the Invoice API from the API Directory, store the connection details once, and your agent calls it.
- **Permission scoping:** Limit the agent to the operations it needs, such as sending an invoice, rather than the whole surface. Because you pick the allowed operations, the agent only ever runs the calls you authorize.
- **Credential handling:** Any connection details for the Invoice API are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a broker carrier invoice', and Jentic returns the matching Invoice API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Invoice API use?

The Invoice API uses no authentication. 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.

### What are the rate limits for the Invoice 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 use invoice API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use invoice API'. Jentic returns the matching Invoice API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Invoice API have?

The Invoice API exposes 1 endpoints covering sendinvoice operations.

### Does the Invoice API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Invoice API?

Yes. Because Jentic One is self-hosted, your own rules decide which Invoice API operations the agent may call, so you can allow only the send invoice operation instead of the whole surface. The agent runs solely the calls you authorize, and the connection details for scapi.truckertools.com are stored once by your own Jentic One instance and injected at execution time rather than exposed to the agent. This keeps the agent scoped to sending broker carrier invoices and nothing more.