canonical: https://jentic.com/apis/swaggerhub.swaggerquiputech/api-voucher

# Swaggerquiputech API Voucher

**API Voucher** *Version 1.0* - Mockup store voucher image. *Version 1.1* - GET voucher by id - GET voucher by external - POST voucher *Version 1.2* - Added merchantImage to voucher (required) - Added traceId to voucher (required) - Added transactionId to voucher (required) - POST report *Version 1.6* - Added voucher type to voucherImageRequest *Version 1.7* - Added brand to voucherImageRequest *V. The API exposes 4 endpoints secured with basic authentication.

## For AI agents

Programmatically store image generated for report, retrieve voucher info by externalid. Covers 4 operations with basic authentication.

## Scope

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

## Capabilities

- Store image generated for report
- Retrieve voucher info by externalId
- Integrate API Voucher into automated workflows
- Query and filter API Voucher records by parameters
- Monitor API Voucher operational status and events

## Use cases

### Payments Operations

Use the API Voucher to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including store image generated for report, retrieve voucher info by externalid, store image generated for voucher.

Example prompt: Call POST /report/store to store image generated for report

### Automated Report API Management

Automate report API operations by combining multiple API Voucher endpoints. Agents can retrieve voucher info by externalid and then store image generated for voucher in a single workflow.

Example prompt: Call GET /voucher/queryByExternal/{externalId} to retrieve voucher info by externalid, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Voucher 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 'store image generated for report', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /report/store | Store image generated for report |
| GET | /voucher/queryByExternal/{externalId} | Retrieve voucher info by externalId |
| POST | /voucher/store | Store image generated for voucher |
| GET | /voucher/{voucherId} | Retrieve voucher info by voucherId |

## Key resources

- **Report API** — RESTful API for digital report operations
- **Voucher API** — Operations related to Voucher API

## Why Jentic

- **Setup:** Wiring API Voucher by hand means handling its basic auth, targeting the test-environment host, and managing voucher store and query calls and retries yourself. Through Jentic you install once, import API Voucher from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** This API puts the voucher id in the URL path (/voucher/{voucherId}), so a rule can pin your agent to reading a single voucher or querying by external id. You choose the operations it may call, so writes like storing a voucher or a report are not included unless you add them.
- **Credential handling:** Your API Voucher 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 'look up a voucher by id' or 'store a voucher', and Jentic returns the matching API Voucher operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the API Voucher use?

The API Voucher 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 store image generated for report with the API Voucher?

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

### What are the rate limits for the API Voucher?

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 store image generated for report through Jentic?

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

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

The API Voucher exposes 4 endpoints covering report API, voucher API operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which API Voucher operations and credentials the agent may use. Because the voucher id sits in the URL path (GET /voucher/{voucherId}), you can pin the agent to read-only lookups such as fetching a single voucher or querying by external id with GET /voucher/queryByExternal/{externalId}. Write operations like POST /voucher/store or POST /report/store are excluded unless you explicitly add them to the agent's allowed operations.