Roffer API gives the latest plans and best offer plans for mobile. The mobile roffer check API supports JSON format to display latest packs from operators
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get available mobile recharge offers for the supplied number and product code.
Endpoint
POST https://pay2new.in/apis/offer/v1/roffer
Headers
| Header | Required | Value / description |
|---|---|---|
secret | Yes | Your Pay2New API secret. Keep it on your server. |
Content-Type | Yes for JSON requests | application/json |
Accept | Optional | application/json |
Authentication
Use an active Pay2New partner account with verified KYC, an active wallet and API access. Send requests from your registered IP address. Enable the relevant service where applicable; offer services may also require an active plan.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
number | string | Yes | Mobile, subscriber or bill account number for the selected product. |
request_id | string | Yes | Unique client reference for this request. Store it for reconciliation and support. Minimum 8 characters. |
product_code | string | Yes | Product/operator code returned by the Product List API. Use numeric characters. |
Request example
Illustrative values
All identifiers, identity data, amounts and IP addresses in these examples are synthetic. Replace the secret, product/customer references and sample inputs with the values for your integration before sending a request.
curl --request POST \
--url 'https://pay2new.in/apis/offer/v1/roffer' \
--header 'secret: <YOUR_PAY2NEW_SECRET>' \
--header 'Content-Type: application/json' \
--data '{
"number": "9999999999",
"request_id": "EXAMPLE202609260001",
"product_code": "1"
}'
Response fields
| Field | Type | Description |
|---|---|---|
status | integer | 1: successful operation; 2: failed/rejected operation; 3: pending or indeterminate where returned. |
message | string | Human-readable result or error message. |
data | array | Offer rows containing rs and desc; returned amounts may be strings. |
Response example
{
"status": 1,
"message": "Transaction Successful!",
"data": [
{
"rs": "100",
"desc": "Illustrative offer description"
}
]
}
Errors
Application failures return status: 2 and a message. Invalid fields can also be identified in an errors object. Authentication, IP registration, service access and product availability can prevent processing. Other response fields may be absent when processing fails before a transaction is created. Evaluate the JSON result even when the HTTP request completes successfully. Preserve your request and order references when an outcome is pending or indeterminate.
{
"status": 2,
"message": "Invalid Parameters",
"errors": {
"number": "Illustrative field validation message"
}
}