canonical: https://jentic.com/apis/swaggerhub.jbhifi/audit-trail-api

# Jbhifi Audit Trail API

Audit Trail API on Azure - Used to record staff actions for other staff (e.g. HR) to view, not for transactional/technical logging. The API exposes 1 endpoints.

## For AI agents

Programmatically creates a new audit entry. Covers 1 operations.

## Scope

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

## Capabilities

- Creates a new audit entry
- Manage payments data programmatically
- Integrate Audit Trail API into automated workflows
- Query and filter Audit Trail API records by parameters
- Monitor Audit Trail API operational status and events

## Use cases

### Payments Operations

Use the Audit Trail API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including creates a new audit entry.

Example prompt: Call POST `/Audit/api/Create` to creates a new audit entry

### Data Retrieval and Monitoring

Query Audit Trail 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 Audit Trail API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Audit Trail 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 'creates a new audit entry', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/Audit/api/Create` | Creates a new audit entry |

## Key resources

- **Write** — Operations related to Write

## Why Jentic

- **Setup:** Wiring the Audit Trail API by hand means reading its spec, building the create-audit-entry request, and handling request formatting and retries yourself. Through Jentic you install once, import Audit Trail from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** This spec exposes a single operation, POST `/Audit/api/Create`, so you limit the agent to the operations it needs: here that is creating an audit entry, and nothing else runs unless you add it. You decide which operations are in the allowed set as your own positive choice.
- **Credential handling:** Any connection detail the Audit Trail API needs 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 audit entry', and Jentic returns the matching Audit Trail 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 Audit Trail API use?

The Audit Trail 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.

### Can I creates a new audit entry with the Audit Trail API?

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

### What are the rate limits for the Audit Trail 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 creates a new audit entry through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new audit entry'. Jentic returns the matching Audit Trail API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Audit Trail API have?

The Audit Trail API exposes 1 endpoints covering write operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. The Audit Trail API exposes a single operation, POST `/Audit/api/Create`, so you can allow the agent to create audit entries and nothing else, because no operation runs unless you add it to the allowed set. Any connection detail the API needs is stored once by your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.