How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Curlec QR Codes API

QR Codes enable offline and digital payment collection. Customers scan with any UPI or card app. Supports fixed-amount and variable-amount codes, single-use and multiple-use modes.

Curlec QR Codes API is one of 30 APIs that Curlec publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include QR Codes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 6 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.razorpay.com/v1.

6 operations 4 paths 8 schemas 3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.razorpay.com/v1
Authentication
HTTP Basic, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Curlec QR Codes API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 1 scope. By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using your Razorpay API key pair. Use keyid as the username and keysecret as the password. Encode as Base64(keyid:keysecret). Keys ar…
  • oauth2 — OAuth 2.0 via the Razorpay MCP server (mcp.razorpay.com). Supports Authorization Code with PKCE (S256) for user-delegated access and Client Credentials for ser…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 3 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

QR Codes 6

QR Codes enable offline and digital payment collection. Customers scan with any UPI or card app. Supports fixed-amount and variable-amount codes, single-use and multiple-use modes.

POST
/payments/qr_codes
Create a QR code
createQrCode body → 200400401429
GET
/payments/qr_codes
Fetch all QR codes
fetchAllQrCodes 6 params → 200401429
GET
/payments/qr_codes/{id}
Fetch QR code by ID
fetchQrCode 1 param → 200401404429
PATCH
/payments/qr_codes/{id}
Update a QR code
updateQrCode 1 param body → 200400401404429
POST
/payments/qr_codes/{id}/close
Close a QR code
closeQrCode 1 param → 200400401404429
GET
/payments/qr_codes/{id}/payments
Fetch payments for a QR code
fetchQrCodePayments 5 params → 200401404429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Payment (33 properties), QrCode (16 properties), CardDetails (9 properties), AcquirerData (4 properties). Each schema is shown below with its type and property counts.

QrCode
object
16 properties
UpiDetails
object
3 properties
Collection
object
3 properties
Payment
object
33 properties
Notes
object
Key-value pairs for storing custom metadata. Maximum 15 pairs. Each key and value must not exceed 256 characters.
AcquirerData
object
4 properties
Error
object
1 property
CardDetails
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

curlec-qr-codes-api-openapi.yml Raw ↑

Other APIs Curlec publishes across the network.

Curlec Bills API
Curlec Customers API
Curlec Disputes API
Curlec Documents API
Curlec Instant Settlements API
Curlec Invoices API
Curlec Items API
Curlec Linked Accounts API
Curlec Orders API
Curlec Partner Accounts API
Curlec Partner Documents API
Curlec Partner Stakeholders API
Where this information came from

This is an independent, third-party profile of Curlec QR Codes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.