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.