POSTFetch Link API
Use Case
This API can be used to get all links created as per the filters defined by the merchant. The merchant can filter by
- Date
- Link Status
- Link/Invoice ID
- Recipient Name
- Recipient Mobile
- Recipient Email
Request Attributes
Head
Attribute | Description |
---|---|
timestamp string(15) optional | EPOCH timestamp of the time at which request is being sent. |
clientId string(3) optional | Paytm use the merchant key on the basis of clientId parameter value. It requires only if the merchant has more than one key. Example: C11 |
version string(4) optional | Version of the API. Example: v2 |
channelId string(3) mandatory | The parameter value identifies the Channel for which API call is initiated. Possible values:
WEB
,
For websites, the value to be passed should be "WEB"
WAP
For Mobile websites/App, the value to be passed should be "WAP"
|
tokenType string mandatory | This parameter identifies whether the API works on checksum authentication. The value to be sent in tokenType is 'AES' for this API. |
signature string(108) mandatory | Paytm validates the request and ensures that parameters are not tempered by verifying the signature in the request. For creating the checksum (signature) refer to the steps given in Checksum Logic. |
Body
Attribute | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
merchantRequestId string optional | Unique ID to be generated by merchant. | ||||||||
mid string(20) mandatory | Paytm provides MID as a unique identifier to each merchant. For your staging MID, click here. You get the production MID post the account activation. Example: INTEGR7769XXXXXX9383 | ||||||||
linkId long optional | Unique Identifier for each Link | ||||||||
pageNo int optional | Page Number | ||||||||
pageSize int optional | Page Size = Total Links/Total no. of Pages | ||||||||
searchFilterRequestBody object optional | Seach Filter Request | ||||||||
SeachFilterRequest +
| |||||||||
linkTypeMultiple array optional | Link type Possible Values: ["FIXED","GENERIC"] | ||||||||
linkDescription string optional | This is the link-description from which link can be fetched | ||||||||
customerName string optional | This is customerName from which link can be fetched | ||||||||
customerPhone string optional | This is customerPhone Number through which link can be fetched | ||||||||
customerEmail string optional | This is customerEmail through which link can be fetched | ||||||||
paymentStatus string optional | This is the payment status values which link can be fetched Possible Values: PENDING, INIT, EXPIRED, PAID | ||||||||
invoiceId string optional | invoice number or unique id | ||||||||
resellerId string optional | Applicable for resellers. The ID will be shared at the time of onboarding. Example: "Dipend011" | ||||||||
resellerName string optional | Name of the reseller Example: "Automation" |
Response Attributes
Head
Attribute | Description |
---|---|
timestamp string(15) | EPOCH timestamp of the time at which response is being sent. |
clientId string(3) | Paytm use the merchant key on the basis of clientId parameter value. It requires only if the merchant has more than one key. Example: C11 |
version string | Version of the API passed in the request. |
channelId string(3) | The parameter value identifies the Channel for which API call is initiated. Possible values:
WEB
,
For websites, the value to be passed should be "WEB"
WAP
For Mobile websites/App, the value to be passed should be "WAP"
|
tokenType string | This parameter identifies whether the API works on checksum authentication. The value to be sent in tokenType is 'AES' for this API. |
signature string(108) | Paytm validates the request and ensures that parameters are not tempered by verifying the signature in the request. For creating the checksum (signature) refer to the steps given in Checksum Logic. |
Body
Attribute | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
resultInfo object | This parameter gives the information about the result of the API response | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ResultInfo +
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
links object | Details of the Links | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Links +
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
mid string(20) | Paytm provides MID as a unique identifier to each merchant. For your staging MID, click here. You get the production MID post the account activation. Example: INTEGR7769XXXXXX9383 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
countLink string | Count of Links as part of the result |
Response Codes & Messages
resultCode | resultStatus | resultMessage |
---|---|---|
200 | SUCCESS | Success |
404 | FAILED | Data Not Found |
501 | FAILED | Internal Server Error |
502 | FAILED | Unknown Error Occurred |
5004 | FAILED | empty merchant Id. |
5028 | FAILED | Checksum provided is invalid. |
5029 | FAILED | request body cannot be empty |
5030 | FAILED | request head cannot be empty |
curl -X POST 'https://securestage.paytmpayments.com/link/fetch' \
--header 'Content-Type: application/json' \
--data '{"body":{"mid":"{mid}"},"head":{"tokenType":"AES","signature":"{signature}"}}'