Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverynone248 EndpointsREST
For Agents
Programmatically 3d secure otp, account adjustment notification. Covers 248 operations.
Use for: I need to 3d secure otp, I want to account adjustment notification, Search for account to account transfer notification, Find all activate card
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
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:  Public key needed in the request might be programmed to be generated and encrypted on each. The API exposes 248 endpoints.
Install Jentic One Beta
Connect the Wallester to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Wallester, 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%2Fwallester.com%2Fwallester" | 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%2Fwallester.com%2Fwallester" | 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 Wallester API.
3D Secure OTP
Account adjustment notification
Activate card
Apple Pay incentive notification incomplete provisioning
Monitor Wallester operational status and events
Use Cases
Patterns agents use Wallester API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for '3d secure otp', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
248 endpoints — 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.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
W
Wallester
- Foundational (D)44/100
56
Foundational Compliance44
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience43
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
56
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: CSignals: 4
50%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
44
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: DSignals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
74%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
0%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Wallester API through Jentic.
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.
GET STARTED