canonical: https://jentic.com/apis/swaggerhub.waikit-1/curfex-api

# Waikit 1 Curfex API

Curfex integration API for business partner. This is a v2 version (released on 2022) replacing existing production version [Curfex API v1](https://app.swaggerhub.com/apis/curfex/curfex_api_v1). All listed APIs are [rate limited](https://www.notion.so/curfex/Rate-Limiting-def3bf1a33e345c4b34580ea282f3deb) Please contact us at tech@curfex.com if you need any help. The API exposes 27 endpoints secured with bearer authentication.

## For AI agents

Programmatically wallethistory, walletbalance. Covers 27 operations with bearer authentication.

## Scope

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

## Capabilities

- walletHistory
- walletBalance
- transferStatus
- transferReceipt
- transferRate
- transferInfoUpdate
- transferHistory

## Use cases

### CRM Operations

Use the Curfex API to perform crm operations programmatically. The API provides 27 endpoints covering core functionality including wallethistory, walletbalance, transferstatus.

Example prompt: Call POST `/api/walletHistory` to wallethistory

### Automated Event Subscription Management

Automate event subscription operations by combining multiple Curfex API endpoints. Agents can walletbalance and then transferstatus in a single workflow.

Example prompt: Call POST `/api/walletBalance` to walletbalance, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/walletHistory` | walletHistory |
| POST | `/api/walletBalance` | walletBalance |
| POST | `/api/transferStatus` | transferStatus |
| POST | `/api/transferReceipt` | transferReceipt |
| POST | `/api/transferRate` | transferRate |
| POST | `/api/transferInfoUpdate` | transferInfoUpdate |
| POST | `/api/transferHistory` | transferHistory |
| POST | `/api/transferBank` | transferBank |

## Key resources

- **Event Subscription** — Operations related to Event Subscription
- **Authentication** — Operations related to Authentication
- **Enquiry** — Operations related to Enquiry
- **Wallet** — Operations related to Wallet
- **Transfer** — Operations related to Transfer

## Why Jentic

- **Setup:** Wiring Curfex API by hand means acquiring a bearer token, attaching it to the Authorization header on every wallet and transfer call, and refreshing it yourself. Through Jentic you install once, import Curfex API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Curfex API sends its wallet and transfer targets in the request body rather than the URL path, so scope with operations-only language: limit the agent to the operations it needs, such as checking wallet balance or reading transfer history. You choose the operations it may call, so state-changing ones like updating transfer info are not included unless you add them.
- **Credential handling:** Your Curfex API bearer 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 'check wallet balance' or 'get transfer history', and Jentic returns the matching Curfex API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Curfex API use?

The Curfex API uses a Bearer token in the Authorization header. 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 wallethistory with the Curfex API?

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

### What are the rate limits for the Curfex 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 wallethistory through Jentic?

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

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

The Curfex API exposes 27 endpoints covering event subscription, authentication, enquiry operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Curfex API operations and credentials the agent may use. Since Curfex sends its wallet and transfer targets in the request body rather than the URL path, you scope access at the operation level, allowing read-only calls like walletBalance, walletHistory, or transferHistory while withholding state-changing ones such as transferInfoUpdate. The agent can only call the operations you explicitly grant, and the stored bearer token is injected at execution time so it never reaches the agent's context.