Sandboxreportingapi Connexpay ConnexPay Reporting API
Community OpenAPI document · agent-readyFinanceAccountingbasic58 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically issuing token, create sale. Covers 58 operations with basic authentication.
Use for: I need to issuing token, I want to sale, Search for void, Find all return
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
REST API for retrieving reporting data. Currently Daily Accounting data only. The API exposes 58 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the ConnexPay Reporting API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ConnexPay Reporting 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.
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%2Fsandboxreportingapi.connexpay.com%2Fsandboxreportingapi-connexpay" | 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%2Fsandboxreportingapi.connexpay.com%2Fsandboxreportingapi-connexpay" | 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 ConnexPay Reporting API.
Issuing Token
Create Sale
Void
Return
Cancel
Auth Only
Capture
Use Cases
Patterns agents use ConnexPay Reporting API for, with concrete tasks.
★ Finance and Accounting Operations
Use the ConnexPay Reporting API to perform finance operations programmatically. The API provides 58 endpoints covering core functionality including issuing token, create sale, void.
Call POST /api/v1/token to issuing token
Automated PushToCard Management
Automate pushtocard operations by combining multiple ConnexPay Reporting API endpoints. Agents can create sale and then void in a single workflow.
Call POST /api/v1/sales to create sale, then verify the result
AI Agent Integration via Jentic
AI agents discover and call ConnexPay Reporting 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 basic tokens manually.
Search Jentic for 'issuing token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
58 endpoints — rest api for retrieving reporting data.
METHOD
PATH
DESCRIPTION
POST
/api/v1/token
Issuing Token
POST
/api/v1/sales
Create Sale
POST
/api/v1/void
Void
POST
/api/v1/returns
Return
POST
/api/v1/cancel
Cancel
POST
/api/v1/authonlys
Auth Only
POST
/api/v1/Captures
Capture
POST
/api/v1/verify
Verify
POST
/api/v1/token
Issuing Token
POST
/api/v1/sales
Create Sale
POST
/api/v1/void
Void
POST
/api/v1/returns
Return
POST
/api/v1/cancel
Cancel
POST
/api/v1/authonlys
Auth Only
POST
/api/v1/Captures
Capture
POST
/api/v1/verify
Verify
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ConnexPay Reporting API by hand means encoding its HTTP basic credentials, requesting a token, and threading it through each sales, void, and return call yourself. Through Jentic you install once, import the ConnexPay Reporting API from the API Directory, store the basic credentials once, and your agent calls it.
Permission scoping
The ConnexPay Reporting API carries transaction details in the request body rather than the URL path, so you limit the agent to the operations it needs, such as running a sale or a verify, and you leave out operations like void, cancel, or returns unless you add them. Every operation the agent runs is one you chose.
Credential isolation
Your ConnexPay Reporting API basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'run a sale' or 'issue a reporting token', and Jentic returns the matching ConnexPay Reporting API 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 ConnexPay Reporting API through Jentic.
What authentication does the ConnexPay Reporting API use?
The ConnexPay Reporting API uses HTTP Basic authentication with username and password. 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 issuing token with the ConnexPay Reporting API?
Yes. Use the POST /api/v1/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the ConnexPay Reporting 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 issuing token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'issuing token'. Jentic returns the matching ConnexPay Reporting API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the ConnexPay Reporting API have?
The ConnexPay Reporting API exposes 58 endpoints covering pushtocard, card, merchantpayees operations.
Can I limit what my agent is allowed to do with the ConnexPay Reporting API?
Yes. Because you run Jentic One yourself, your own rules decide which ConnexPay Reporting API operations and credentials the agent can use, so you can grant just the endpoints it needs, such as POST /api/v1/sales to create a sale or POST /api/v1/verify to verify one. Higher-impact operations like POST /api/v1/void, POST /api/v1/cancel, and POST /api/v1/returns stay off unless you explicitly add them. Since transaction details travel in the request body rather than the URL path, every operation the agent runs is one you chose to allow.
GET STARTED