Curfex API

Name: Curfex API API
Brand: Curfex API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer27 EndpointsREST

For Agents

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

Use for: I need to wallethistory, I want to walletbalance, Search for transferstatus, Find all transferreceipt

Connect the Curfex API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Curfex API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Curfex API API.

walletHistory

walletBalance

transferStatus

transferReceipt

transferRate

GET STARTED

Start building with Curfex API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Curfex API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Curfex API API for, with concrete tasks.

★ CRM Operations

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

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.

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.

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

Key Endpoints

27 endpoints — curfex integration api for business partner.

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

POST

/api/walletHistory

walletHistory

POST

/api/walletBalance

walletBalance

POST

/api/transferStatus

transferStatus

POST

/api/transferReceipt

transferReceipt

POST

/api/transferRate

transferRate

POST

/api/transferInfoUpdate

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Curfex API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'wallethistory') and Jentic returns the matching Curfex API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Curfex API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hubspot

Alternative crm API

Choose Hubspot when you need a different approach to crm operations

Alternative

Salesforce

Alternative crm API

Choose Salesforce when you need a different approach to crm operations

Complementary

Pipedrive

Complementary crm API

Choose Pipedrive when you need a complementary approach to crm operations

Complementary

Zoho

Complementary crm API

Choose Zoho when you need a complementary approach to crm operations

FAQs

Specific to using Curfex API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.