Chargeblast API

Name: Chargeblast API
Brand: Chargeblast API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey17 EndpointsREST

For Agents

Track chargeback alerts, ingest orders for matching, request credits to deflect disputes, and manage merchant enrollment. Useful for fraud and dispute operations agents working across multiple alert generations.

Install Jentic One Beta

Connect the Chargeblast API to your agent

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

Pull deflection logs from /api/v3/deflections/logs to audit which alerts were resolved before posting

Track outbound notifications and webhook callbacks via POST /api/v2/track

Manage order data with GET /api/v2/orders, individual lookups, and POST /api/v2/orders/upload bulk ingestion

GET STARTED

Start building with Chargeblast API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Chargeblast API for, with concrete tasks.

★ Multi-Network Chargeback Deflection

Merchants enrolled across CDRN, Ethoca, and RDR pull alerts from /api/v2/alerts and decide whether to refund (deflect) or fight. The platform lets the merchant call POST /api/v2/credit-request/create to instruct the issuer to credit the cardholder, which prevents the dispute from progressing into a chargeback. Audit trails are pulled from /api/v3/deflections/logs.

Pull /api/v2/alerts with state=open, post /api/v2/credit-request/create for each over the deflection threshold, then verify with /api/v3/deflections/logs

Order Sync for Faster Resolution

POST /api/v2/orders/upload accepts a batch of completed orders so incoming alerts can be matched against the merchant's actual transaction record. Better matching reduces manual review time on the dispute desk and lets the merchant decide on credit-vs-fight in seconds rather than minutes.

POST /api/v2/orders/upload with the last 24 hours of orders and confirm via GET /api/v2/orders that the records are searchable

Merchant Onboarding into Alert Networks

Payment service providers and aggregators onboard merchants into the chargeback alert networks through POST /api/enroll_merchant. The endpoint registers the descriptors and the merchant identifier; POST /api/unenroll cleanly reverses enrollment when the merchant offboards. GET /api/merchants and /api/descriptors give the read-side view for reconciliation.

POST /api/enroll_merchant with merchant identifiers and descriptors, then verify via GET /api/merchants

Agent-Driven Dispute Operations via Jentic

An AI agent given a directive like 'deflect any open alert under $200 by issuing a credit' can resolve the workflow through Jentic. The agent searches Jentic for the list-alerts and credit-request operations, iterates the alerts, and issues the credit instructions, while the API key stays in the MAXsystem vault.

Search Jentic for 'list chargeback alerts', filter to open alerts under $200, and post /api/v2/credit-request/create for each

Key Endpoints

17 endpoints — chargeblast is a chargeback alert and prevention tool that notifies merchants whenever a cardholder initiates a dispute, allowing the merchant to refund or contest before it becomes a chargeback.

METHOD

PATH

DESCRIPTION

GET

/api/v2/alerts

List chargeback alerts (v2)

POST

/api/v2/alerts/update/{id}

Update an alert outcome (v2)

POST

/api/v2/credit-request/create

Submit a credit request to deflect an alert

POST

/api/v2/orders/upload

Bulk upload merchant orders

GET

/api/v2/orders/{id}

Retrieve a single order by ID

GET

/api/v3/deflections/logs

Read deflection audit logs (v3)

POST

/api/enroll_merchant

Enroll a merchant into the alert network

GET

/api/v2/alerts

List chargeback alerts (v2)

POST

/api/v2/alerts/update/{id}

Update an alert outcome (v2)

POST

/api/v2/credit-request/create

Submit a credit request to deflect an alert

POST

/api/v2/orders/upload

Bulk upload merchant orders

GET

/api/v2/orders/{id}

Retrieve a single order by ID

Why Jentic?

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

Credential isolation

Chargeblast uses an X-API-Key header. Jentic stores the key encrypted in the MAXsystem vault and gives the agent a scoped execution token, so the merchant's master key never enters the agent's context.

Intent-based discovery

Agents query Jentic with intents like 'list chargeback alerts' or 'submit a credit request', and Jentic returns the matching Chargeblast operations with the alert ID and credit amount schema resolved.

Time to first call

Direct Chargeblast integration: 2-4 days for alert polling, order ingestion, and deflection workflows. Through Jentic: under an hour — search, load, execute against the alert IDs.

FAQs

Specific to using Chargeblast API through Jentic.

What authentication does the Chargeblast API use?

Chargeblast uses an API key in the X-API-Key header on every request. Through Jentic, the key is stored encrypted in the MAXsystem vault and only injected server-side at execution time.

Can I deflect a chargeback by issuing a credit through the Chargeblast API?

Yes. POST /api/v2/credit-request/create with the alert ID and credit amount and Chargeblast forwards the credit instruction to the issuer. If accepted in time, the dispute is closed before it becomes a chargeback.

What is the difference between the v2 and v3 endpoints on this API?

The v2 endpoints handle alert listing, order upload, and credit-request creation. The v3 namespace currently exposes /api/v3/deflections/logs for the audit trail. Both versions share the same X-API-Key auth and base URL.

What are the rate limits for the Chargeblast API?

Chargeblast does not publish a fixed public rate limit. Real-time alert workloads should poll /api/v2/alerts at modest intervals and bulk-upload orders via /api/v2/orders/upload rather than per-order writes; back off on HTTP 429.

How do I bulk-upload orders for matching through Jentic?

Install jentic with pip install jentic, search for 'upload merchant orders for chargeback matching', load the schema for POST /api/v2/orders/upload, and execute. Sign up at https://app.jentic.com/sign-up for an agent API key.

Does the Chargeblast API expose deflection audit logs?

Yes. GET /api/v3/deflections/logs returns the history of alerts that were successfully deflected, suitable for compliance reporting and reconciliation against the merchant's chargeback ratio over time.

Chargeblast API

Connect the Chargeblast API to your agent

Capabilities

Start building with Chargeblast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs