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

# Swaggerquiputech API Authorization

API encargada de la autorizacion de transacciones. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically authorization, voidmerchanttrx. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Authorization
- VoidMerchantTrx
- Void
- Query and filter API Authorization records by parameters
- Monitor API Authorization operational status and events

## Use cases

### Identity and Authentication Operations

Use the API Authorization to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including authorization, voidmerchanttrx, void.

Example prompt: Call POST /authorization/{product}/{merchantId} to authorization

### Automated Authorization API Management

Automate authorization API operations by combining multiple API Authorization endpoints. Agents can voidmerchanttrx and then void in a single workflow.

Example prompt: Call POST /void/{merchantId} to voidmerchanttrx, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Authorization 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /authorization/{product}/{merchantId} | Authorization |
| POST | /void/{merchantId} | VoidMerchantTrx |
| POST | /void/{product}/{merchantId} | Void |
| POST | /void/{product}/{merchantId}/{backofficeId} | VoidBackOffice |

## Key resources

- **Authorization Api** — RESTful API to authorize transactions.
- **Void Api** — RESTful API to void transactions.

## Why Jentic

- **Setup:** Wiring the API Authorization service by hand means setting its Authorization access-token header, targeting the authorization host, and handling authorization and void calls and retries yourself. Through Jentic you install once, import API Authorization from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** This API puts the merchant id in the URL path (/authorization/{product}/{merchantId}), so a rule can pin your agent to one merchant: it can run authorizations for that merchant and nothing else. You choose the operations it may call, so voids at the product or backoffice level are not included unless you add them.
- **Credential handling:** Your API Authorization access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'authorize a payment for a merchant' or 'void a transaction', and Jentic returns the matching API Authorization operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the API Authorization use?

The API Authorization uses an API key passed in the `Authorization` header. 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 authorization with the API Authorization?

Yes. Use the POST /authorization/{product}/{merchantId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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 authorization through Jentic?

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

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

The API Authorization exposes 4 endpoints covering authorization API, void API operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because the API Authorization puts the merchant id in the URL path, such as /authorization/{product}/{merchantId}, you can pin the agent to a single merchant and let it run authorizations for that merchant only. You also choose which operations it may call, so voids at the product or backoffice level, like /void/{product}/{merchantId} or /void/{product}/{merchantId}/{backofficeId}, stay off limits unless you add them.