Paymish Loading Docs Preparing guides, collections, and live API references...
Paymish Docs

Get payment products

Topics

Endpoint Overview

Products

Get payment products

GET /api/payment-service/external/v1/products/get-products Requires authentication

Purpose

Use this endpoint to get payment products. It belongs to the Products collection and is designed for backend integrations.

Request shape

9 parameters and 0 documented body fields using application/json.

Implementation Guide

Recommended workflow

1

Authenticate first and inject a valid bearer token or secret key before calling the endpoint.

2

Validate the input data, identifiers, and account state in your application before making the request.

3

Send the GET request from your backend using the required headers and the expected content type (application/json).

4

Persist the important identifiers returned in the response so later lookups, webhooks, or support actions can be linked correctly.

Implementation notes

  • Validate and encode query parameters before sending them so filters and pagination behave predictably.

Query Parameters

status
boolean
Product status (true/false)
quantityType
string
Stock type (Limited/Unlimited)
quantityStock
integer
Quantity in stock
quantityStockType
string
Quantity stock type (moreThan/lessThan/equals)
productPrice
string
Product price
productPriceType
string
Product price type (moreThan/lessThan/equals)
searchPlanText
string
Search plan text
startDate
string
Start date (in ISO 8601 format)
endDate
string
End date (in ISO 8601 format)

Responses

200 Get products
400 Bad request

Expected Outcomes

200

Success example

Get products

Representative Response 
{
  "status": "success",
  "message": "Record retrieved successfully",
  "data": {
    "reference": "PM-REF-12345",
    "status": "success"
  }
}
400

Record not found

Bad request

Representative Error 
{
  "status": "error",
  "message": "Requested record was not found.",
  "errors": {
    "reference": [
      "Check the identifier and merchant context before retrying."
    ]
  }
}
After the response:
  • Log the Paymish reference or request context returned by the API so support teams can trace the call later.
  • Retry only when the failure is safe to repeat; otherwise correct the payload or auth state first.
  • Store enough internal metadata to match the API response back to your order, payout, case, or checkout record.

Language Notes

Python

Use `requests` from a backend worker, service, or Django/Flask app and centralize headers in a reusable helper.

Node.js

Use `axios` or `fetch` from Node.js services only; do not place secret credentials in frontend bundles.

PHP

Wrap cURL usage in a small client class so auth headers, error handling, and logging stay consistent.

cURL

Use cURL for smoke testing and debugging, then move the final logic into your backend service code.

Code Examples

Python 
import requests

headers = {
    "Authorization": "Bearer YOUR_SECRET_KEY",
}
response = requests.get(
    "https://api.paymish.com/api/payment-service/external/v1/products/get-products",
    headers=headers,
)

data = response.json()
print(data)
Node.js 
const axios = require("axios");

const response = await axios({
  method: "get",
  url: "https://api.paymish.com/api/payment-service/external/v1/products/get-products",
  headers: {
    Authorization: "Bearer YOUR_SECRET_KEY",
  }
});

console.log(response.data);
cURL 
curl https://api.paymish.com/api/payment-service/external/v1/products/get-products \
   \
  -H "Authorization: Bearer YOUR_SECRET_KEY"
PHP 
<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/payment-service/external/v1/products/get-products");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "GET");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer YOUR_SECRET_KEY",
]);

$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
Previous endpoint Create New Product Next endpoint Get product detail