Instamojo Payments API

Name: Instamojo Payments API
Brand: Instamojo Payments API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer5 EndpointsREST

For Agents

Create Instamojo payment requests, look up payment status, and issue refunds for Indian merchants using the v2 Payments API.

Install Jentic One Beta

Connect the Instamojo Payments API to your agent

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

Create a payment request with amount, purpose, and buyer details via POST /v2/payment_requests

Look up the status of a payment request including its constituent payments via GET /v2/payment_requests/{id}

Retrieve a specific payment under a payment request to confirm settlement

GET STARTED

Start building with Instamojo Payments API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Instamojo Payments API, keeping it validated and agent-ready. The Instamojo v2 Payments API lets Indian merchants create payment requests, query payment status, and process refunds, with a separate /oauth2/token exchange to obtain a bearer access token. The surface area is small and focused — five endpoints covering the request, lookup, and refund lifecycle — which makes it well suited to embedded checkout flows on Indian e-commerce sites and marketplaces. A test base URL at test.instamojo.com mirrors production for safe development.

Use Cases

Patterns agents use Instamojo Payments API for, with concrete tasks.

★ Embedded Checkout for Indian E-Commerce

Generate a hosted Instamojo payment link by calling POST /v2/payment_requests with the order amount, buyer email, and a redirect URL, then surface the returned long URL to the customer. After the customer completes the payment, GET /v2/payment_requests/{id} confirms the status before the order is fulfilled. The full flow can be wired in a few hours since only two endpoints are involved.

Create a payment request for INR 1,499 with a redirect URL, return the long URL to the customer, and poll GET /v2/payment_requests/{id} until status is Completed.

Refund Workflow for Customer Support

When a support agent approves a refund, automate the resolution by POSTing to /v2/resolutions with the original payment id, refund type, and amount. The endpoint creates an Instamojo resolution that triggers the refund settlement, replacing manual dashboard work and giving the customer a tracked refund identifier.

POST /v2/resolutions with the payment id and amount to refund, then surface the resolution id back to the support tool.

AI Agent Payment Operator via Jentic

An AI agent that handles order creation can call Instamojo through Jentic to mint a payment link, then check status and issue refunds without holding the bearer token. Jentic manages the OAuth client credentials and exposes each operation by intent, so the agent can complete the checkout-to-refund lifecycle from natural-language tasks.

Through Jentic, call instamojo_create_payment_request with the order amount and buyer email, return the long URL, and call instamojo_get_payment_request to verify status before fulfilment.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for instamojo payments api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/payment_requests

Create a payment request

GET

/v2/payment_requests/{id}

Get a payment request and its payments

GET

/v2/payment_requests/{payment_request_id}/payments/{payment_id}

Get a specific payment

POST

/v2/resolutions

Create a refund resolution

POST

/oauth2/token

Exchange client credentials for a bearer token

POST

/v2/payment_requests

Create a payment request

GET

/v2/payment_requests/{id}

Get a payment request and its payments

GET

/v2/payment_requests/{payment_request_id}/payments/{payment_id}

Get a specific payment

POST

/v2/resolutions

Create a refund resolution

POST

/oauth2/token

Exchange client credentials for a bearer token

Why Jentic?

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

Credential isolation

Instamojo OAuth client credentials are stored encrypted in the Jentic vault. Bearer tokens are minted via /oauth2/token at execution time and never returned to the agent prompt context.

Intent-based discovery

Agents search Jentic by intent (for example 'create an Instamojo payment request' or 'refund an Instamojo payment') and Jentic returns the matching v2 operation with its input schema.

Time to first call

Direct integration: 1-2 days to wire OAuth, payment requests, status polling, and refund resolutions. Through Jentic: under 30 minutes.

FAQs

Specific to using Instamojo Payments API through Jentic.

Why is there no official OpenAPI spec for Instamojo Payments API?

Instamojo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Instamojo Payments 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 Instamojo Payments API use?

The API uses bearer authentication. You exchange client credentials at POST /oauth2/token for an access token, then send it as Authorization: Bearer <token> on subsequent calls. Through Jentic, the client credentials are held in the encrypted Jentic vault and the bearer token is injected at execution time.

Can I issue refunds with the Instamojo Payments API?

Yes. POST /v2/resolutions creates a refund resolution against a specific payment id. You supply the payment id, refund type, and amount, and the response includes a resolution id you can persist for reconciliation.

What are the rate limits for the Instamojo Payments API?

The OpenAPI specification does not encode explicit rate limits. The endpoints are transactional rather than bulk, so design integrations around per-order calls; back off on 429 responses and avoid polling /v2/payment_requests/{id} more often than every few seconds.

How do I create a payment link through Jentic?

Install with pip install jentic, then run the search-load-execute flow with the query 'create an Instamojo payment request'. Jentic returns the operation bound to POST /v2/payment_requests; the agent supplies amount, purpose, buyer name, and redirect URL, and receives a long URL to share with the customer.

Is there a sandbox base URL?

Yes. The OpenAPI spec lists https://test.instamojo.com alongside the production base URL https://api.instamojo.com. Point the bearer token issued for the test environment at the test base URL during development.

Instamojo Payments API

Connect the Instamojo Payments API to your agent

Capabilities

Start building with Instamojo Payments API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs