Swaggerquiputech API Authorization

Name: API Authorization API
Brand: API Authorization
Availability: InStock

Browse all Swaggerhub Swaggerquiputech APIs

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthorizationapiKey4 Endpoints

Install Jentic One Beta

Connect the API Authorization to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Authorization, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 API Authorization API.

Authorization

VoidMerchantTrx

Void

Query and filter API Authorization records by parameters

GET STARTED

Start building with API Authorization API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Authorization API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

4 endpoints — api encargada de la autorizacion de transacciones.

METHOD

PATH

DESCRIPTION

POST

/authorization/{product}/{merchantId}

Authorization

POST

/void/{merchantId}

VoidMerchantTrx

POST

/void/{product}/{merchantId}

Void

POST

/void/{product}/{merchantId}/{backofficeId}

VoidBackOffice

POST

/authorization/{product}/{merchantId}

Authorization

POST

/void/{merchantId}

VoidMerchantTrx

POST

/void/{product}/{merchantId}

Void

POST

/void/{product}/{merchantId}/{backofficeId}

VoidBackOffice

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using API Authorization API through Jentic.

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.

Swaggerquiputech API Authorization

Connect the API Authorization to your agent

Capabilities

Start building with API Authorization API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs