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

PayU Authorize API

Authentication involves generating an OAuth token, which is used for further communication with PayU servers. To create a standard OAuth token, you will need client_id and client_secret keys, which can be found in your merchant panel, in the POS.

PayU Authorize API is one of 18 APIs that PayU publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Authorize. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 2.1.0.

Requests are made against 2 base URLs: https://secure.payu.com, https://secure.snd.payu.com.

1 operations 1 paths 3 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.1.0
Base URL
https://secure.payu.com
Authentication
HTTP Bearer, HTTP Basic
License
Resource Areas
1

Authentication & Security 2

PayU Authorize API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (Bearer). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Authorize 1

Authentication involves generating an OAuth token, which is used for further communication with PayU servers. To create a standard OAuth token, you will need clientid and clientse…

POST
/pl/standard/user/oauth/authorize
Create OAuth Token
oauth body → 200400401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are TrustedMerchant (5 properties), Partner (4 properties), ClientCredentials (3 properties). Each schema is shown below with its type and property counts.

Partner
object
only usable with special Technical Partner priviliges that allow management of Firms, URLs, Shops and POSes created and managed by Partner
4 properties 4 required
TrustedMerchant
object
5 properties 5 required
ClientCredentials
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payu-authorize-api-openapi.yml Raw ↑

Other APIs PayU publishes across the network.

PayU India REST API
PayU Latam Payments API
PayU Enterprise API (PaymentsOS)
PayU Card Installments API
PayU FX-Reference API
PayU Marketplace-Seller API
PayU Marketplace-Verification API
PayU MCP API
PayU Order API
PayU Partner-Merchant-Registration API
PayU Payment-Methods API
PayU Payout API
Where this information came from

This is an independent, third-party profile of PayU Authorize 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.