canonical: https://jentic.com/apis/receiptwrangler.io/receiptwrangler

# Receipt Wrangler API

Receipt Wrangler is a self-hosted receipt management system with OCR processing, AI-powered data extraction, and collaborative expense tracking. The API exposes 76 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically user login, user logout. Covers 76 operations with apiKey, bearer authentication.

## Scope

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

## Capabilities

- User login
- Refresh access tokens
- Create a new user (admin only)
- List all users
- Update a user (admin only)

## Use cases

### Analytics Operations

Use the Receipt Wrangler API to perform analytics operations programmatically. The API provides 76 endpoints covering core functionality including user login, user logout, user registration.

Example prompt: Call POST /login/ to user login

### Automated Apikey Management

Automate apikey operations by combining multiple Receipt Wrangler API endpoints. Agents can user logout and then user registration in a single workflow.

Example prompt: Call POST /logout/ to user logout, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Receipt Wrangler 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, bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login/` | User login |
| POST | `/logout/` | User logout |
| POST | `/signUp` | User registration |
| POST | `/token/` | Refresh access tokens |
| POST | `/user` | Create a new user (admin only) |
| GET | `/user` | List all users |
| PUT | `/user/{userId}` | Update a user (admin only) |
| DELETE | `/user/{userId}` | Delete a user (admin only) |

## Key resources

- **Apikey** — Operations for apiKey
- **Category** — Operations for category
- **Comment** — Operations for comment
- **Dashboard** — Operations for dashboard
- **Export** — Operations for export

## Why Jentic

- **Setup:** Wiring the Receipt Wrangler API by hand means handling its bearer token and Authorization API key auth, and pointing every request at your own self-hosted instance host. Through Jentic you install once, import the Receipt Wrangler API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Receipt Wrangler puts the user id in the URL path (`/user/{userId}`), so a rule can pin your agent to a specific user. You choose the operations it may call, so writes like updating or deleting a user are only included if you add them.
- **Credential handling:** Your Receipt Wrangler token 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 'log in a user' or 'fetch a user record', and Jentic returns the matching Receipt Wrangler operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Receipt Wrangler API use?

The Receipt Wrangler API uses apiKey, bearer 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 user login with the Receipt Wrangler API?

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

### What are the rate limits for the Receipt Wrangler 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 user login through Jentic?

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

### How many endpoints does the Receipt Wrangler API have?

The Receipt Wrangler API exposes 76 endpoints covering apikey, category, comment operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Receipt Wrangler operations and credentials the agent may use. Receipt Wrangler puts the user id in the URL path, such as `/user/{userId}`, so a rule can pin the agent to a single user, and you pick the operations it may call. That means write actions like PUT `/user/{userId}` to update a user or DELETE `/user/{userId}` to delete one are only in reach when you explicitly grant them, while read-only calls stay off unless you allow them.