canonical: https://jentic.com/apis/wallester.com/wallester

# Wallester

Wallester Card API Rate limits Wallester has no rate limits and allows sending an unlimited number of requests to API, but we reserve the right to impose such limits if necessary. RSA keys Encrypted card data exchange schema: ![Encrypted card data exchange schema](img/encrypted-card-data-exchange-schema.png) Public key needed in the request might be programmed to be generated and encrypted on each. The API exposes 248 endpoints.

## For AI agents

Programmatically 3d secure otp, account adjustment notification. Covers 248 operations.

## Scope

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

## Capabilities

- 3D Secure OTP
- Account adjustment notification
- Activate card
- Apple Pay incentive notification incomplete provisioning
- Monitor Wallester operational status and events

## Use cases

### Communications Operations

Use the Wallester to perform communications operations programmatically. The API provides 248 endpoints covering core functionality including 3d secure otp, account adjustment notification, account to account transfer notification.

Example prompt: Call POST /host:port/v1/3d-secure-otp-event to 3d secure otp

### Automated Card Management

Automate card operations by combining multiple Wallester endpoints. Agents can account adjustment notification and then account to account transfer notification in a single workflow.

Example prompt: Call POST /host:port/v1/account-adjustment-notification to account adjustment notification, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wallester 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 '3d secure otp', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/host:port/v1/3d-secure-otp-event` | 3D Secure OTP |
| POST | `/host:port/v1/account-adjustment-notification` | Account adjustment notification |
| POST | `/host:port/v1/account-to-account-transfer-notification` | Account to Account transfer notification |
| POST | `/host:port/v1/activate-card-event` | Activate card |
| POST | `/host:port/v1/apple-pay-incentive-notification-incomplete-provisioning-event` | Apple Pay incentive notification incomplete provisioning |
| POST | `/host:port/v1/apple-pay-incentive-notification-successful-transaction-event` | Apple Pay incentive notification successful transaction |
| POST | `/host:port/v1/apple-pay-orange-flow-event` | Apple pay orange flow |
| POST | `/host:port/v1/authorization-event` | Authorization |

## Key resources

- **Card** — Operations related to Card
- **Person** — Operations related to Person
- **Webhooks** — ## Introduction

This document describes how the **Client** can integrate with the **Wallester** sys
- **Company** — Operations related to Company
- **Account** — Operations related to Account

## Why Jentic

- **Setup:** Wiring Wallester by hand means routing to its api.wallester.com/v1 host and configuring each event notification callback yourself. Through Jentic you install once, import Wallester from the API Directory, store your connection credential once, and your agent calls it.
- **Permission scoping:** Wallester exposes notification and event operations that carry their target in the request body rather than in fixed resource URL paths, so limit the agent to the operations it needs, such as posting an authorization event, and leave others out of the allowed set unless you add them.
- **Credential handling:** Your Wallester credential 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 'handle a 3D Secure OTP event' or 'post an authorization event', and Jentic returns the matching Wallester operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Wallester use?

The Wallester 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 3d secure otp with the Wallester?

Yes. Use the POST /host:port/v1/3d-secure-otp-event endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wallester?

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 3d secure otp through Jentic?

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

### How many endpoints does the Wallester have?

The Wallester exposes 248 endpoints covering card, person, webhooks operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Wallester operations and credentials the agent may use. Wallester's calls are notification and event operations that carry their target in the request body rather than in fixed resource URL paths, so you add only the specific operations the agent needs, such as posting an authorization event or a 3D Secure OTP event, to the allowed set. Any operation you leave out cannot be called until you explicitly add it.