canonical: https://jentic.com/apis/sandboxreportingapi.connexpay.com/sandboxreportingapi-connexpay

# Sandboxreportingapi Connexpay ConnexPay Reporting API

REST API for retrieving reporting data. Currently Daily Accounting data only. The API exposes 58 endpoints secured with basic authentication.

## For AI agents

Programmatically issuing token, create sale. Covers 58 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Issuing Token
- Create Sale
- Void
- Return
- Cancel
- Auth Only
- Capture

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **PushToCard** — Operations related to PushToCard
- **Card** — Operations related to Card
- **MerchantPayees** — Operations related to MerchantPayees
- **Sale** — Operations related to Sale
- **Token** — Operations related to Token

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### 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.