Paisabazaar APIpaisabazaar.com ↗
Access Paisabazaar credit card data via API. Browse listings by bank or category, search by keyword, and retrieve fees, rewards, and eligibility details.
What is the Paisabazaar API?
The Paisabazaar API provides 7 endpoints for accessing credit card data from India's largest credit card comparison platform. Use list_credit_cards to retrieve the top-10 cards with fees and highlights, search_credit_cards to match cards by keyword across names, categories, and banks, or get_credit_card_details to pull structured fee tables, eligibility criteria, features, and FAQs for any specific card.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/9e477bc8-7a1c-4f2f-bcdb-11c2567823d3/list_credit_cards' \ -H 'X-API-Key: $PARSE_API_KEY'
List the top 10 credit cards from the Paisabazaar top-10 page. Returns cards with fees, highlights, and category tags. Single-page response with no pagination.
No input parameters required.
{
"type": "object",
"fields": {
"cards": "array of card objects with name, link, slug, image, joining_fee, annual_fee, categories, highlights, bank_name",
"total": "integer count of cards returned"
}
}About the Paisabazaar API
Credit Card Listings and Discovery
The list_credit_cards endpoint returns up to 10 cards from the Paisabazaar top-10 page, each with name, slug, joining_fee, annual_fee, categories, highlights, and bank_name. For broader discovery, list_credit_cards_by_bank accepts a bank_slug parameter (e.g. hdfc-bank, sbi-bank, axis-bank) and returns all cards listed under that bank. list_credit_cards_by_category accepts a category_slug (e.g. travel-credit-cards) and returns all cards in that category. Use list_banks and list_categories to enumerate all valid slug values for either endpoint.
Search and Card Details
search_credit_cards accepts a free-text query and matches against card names, category tags, highlights, and bank names using OR logic — each word in a multi-word query is matched independently. Results include the full card object shape including slug, link, and fee fields. get_credit_card_details requires both bank_slug and card_slug (both retrievable from listing endpoint link fields) and returns a structured fees_and_charges object, an eligibility array, a features array, and a faqs array with question and answer fields for each entry.
Response Structure
All listing endpoints return a consistent card object shape: name, link, slug, image, joining_fee, annual_fee, categories (array), highlights (array), and bank_name. The total field on listing responses gives the integer count of cards returned. Detail responses diverge with structured sub-objects — fees_and_charges is a key-value map of fee label to amount, while features and eligibility are flat string arrays.
The Paisabazaar API is a managed, monitored endpoint for paisabazaar.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when paisabazaar.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official paisabazaar.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a credit card comparison tool filtered by bank using list_credit_cards_by_bank with bank_slug
- Populate a travel rewards card finder using list_credit_cards_by_category with 'travel-credit-cards'
- Display full fee breakdowns and eligibility requirements using get_credit_card_details fees_and_charges and eligibility fields
- Power a card search feature in a personal finance app using search_credit_cards with user-entered queries
- Aggregate joining_fee and annual_fee data across all banks to compare cost-of-ownership programmatically
- Surface card FAQs and feature highlights in a chatbot or recommendation engine using the faqs and features arrays from get_credit_card_details
- Enumerate all supported card categories with list_categories to build a filterable navigation menu
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.