Malga Documentação Malga API

Name: Documentação Malga API
Brand: Documentação Malga API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey46 EndpointsREST

For Agents

Process card payments, manage charges and sessions, and handle customers and webhooks on the Malga payment orchestration platform. Used by agents that automate Brazilian e-commerce checkout flows and reconcile payment events.

Install Jentic One Beta

Connect the Documentação Malga API to your agent

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

Tokenise a card and create a stored card object for future charges

Create a new charge against a token or stored card with capture or pre-auth flag

Capture a previously pre-authorised charge or void an approved charge

GET STARTED

Start building with Documentação Malga API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Documentação Malga API for, with concrete tasks.

★ One-Time Card Checkout

Brazilian e-commerce checkouts need a card-tokenise-then-charge flow that handles 3DS, antifraud, and capture in one orchestration. Malga's tokens, cards, and charges endpoints together let an integration tokenise the card on the client, create a stored card, and charge it with capture set to true. The same flow supports pre-auth followed by a separate capture call.

POST /v1/tokens with the card data, POST /v1/cards with the token, then POST /v1/charges referencing the card with capture=true.

Pre-Auth and Capture Flow

Hospitality and rental businesses pre-authorise a card at booking and capture later when the service is consumed. Malga's charges endpoint supports capture=false to create the pre-auth and POST /v1/charges/{id}/capture to settle the funds when the customer checks out. Voiding a pre-auth releases the hold without a settlement.

POST /v1/charges with capture=false at booking, then POST /v1/charges/{id}/capture at check-out — or POST /v1/charges/{id}/void on cancellation.

Marketplace Split Payments

Marketplaces need to split a single customer payment between multiple sellers and the platform. Malga's sellers, merchants, and charges endpoints support split-payment configuration where each charge declares its split rules and Malga settles the right share to each seller. The same flow underpins service marketplaces and multi-vendor checkout.

Configure sellers via POST /v1/sellers, then POST /v1/charges with the split rules to settle each seller's share automatically.

AI Agent Payment Operator

Finance and ops teams can delegate routine payment lookups, retries, and refunds to an agent. Through Jentic the agent searches by intent, loads the schema, and executes the right Malga operation while X-Client-Id and X-Api-Key stay in the encrypted vault. The same loop powers checkout assistants and finance copilots.

Use Jentic to search 'create a charge on malga', execute POST /v1/charges with the resolved customer and amount, and report the charge ID and status.

Key Endpoints

46 endpoints — jentic publishes the only available openapi specification for documentação malga api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/tokens

Create a token from raw card data

POST

/v1/cards

Create a stored card from a token

POST

/v1/charges

Create a charge

GET

/v1/charges

List charges

POST

/v1/charges/{id}/capture

Capture a pre-authorised charge

POST

/v1/charges/{id}/void

Void an approved charge

POST

/v1/sessions

Create a session that bundles charges

POST

/v1/tokens

Create a token from raw card data

POST

/v1/cards

Create a stored card from a token

POST

/v1/charges

Create a charge

GET

/v1/charges

List charges

POST

/v1/charges/{id}/capture

Capture a pre-authorised charge

POST

Why Jentic?

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

Credential isolation

The X-Client-Id and X-Api-Key pair is stored encrypted in the Jentic vault. Agents call Malga through a scoped execution token and Jentic injects both headers server-side, so the secrets never enter agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a card charge in BRL') and Jentic returns POST /v1/charges with its input schema, removing the need to navigate the 46-operation surface.

Time to first call

Direct Malga integration: 3-5 days for tokenisation, charge orchestration, webhook handling, and antifraud handling. Through Jentic: under a day — search, load, execute.

FAQs

Specific to using Documentação Malga API through Jentic.

Why is there no official OpenAPI spec for Documentação Malga API?

Malga does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Documentação Malga API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Malga API use?

Malga requires both X-Client-Id and X-Api-Key headers on every request. Through Jentic both values are stored encrypted in the vault and attached at execute time, so the secrets never reach the agent context.

Can I tokenise a card before charging it?

Yes. POST /v1/tokens accepts the raw card data and returns a token; POST /v1/cards turns that token into a stored card. The charges endpoint then references the stored card rather than the raw card data.

How do I capture a pre-authorised charge?

Create the charge with capture set to false, then call POST /v1/charges/{id}/capture when you are ready to settle. POST /v1/charges/{id}/void releases a pre-auth instead of capturing it.

What are the rate limits for the Malga API?

Rate limits are not declared in the OpenAPI spec — they depend on your Malga contract and environment (sandbox versus production). Confirm with Malga support before driving high-volume traffic.

How do I create a charge through Jentic?

Run pip install jentic, search 'create a charge on malga', load the schema for POST /v1/charges, and execute with the card or token reference and amount. Jentic injects X-Client-Id and X-Api-Key from the vault.

Malga Documentação Malga API

Connect the Documentação Malga API to your agent

Capabilities

Start building with Documentação Malga API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs