CardAPI vs Rewards Credit Card API
Rewards Credit Card API (rewardscc.com) is the other self-serve credit card data API. Both describe card products, not payments. Every statement about Rewards CC below comes from their own pages, linked on each row, as we read them on 15 Oct 2026. If something has changed, tell us and we'll correct it.
Side by side
| CardAPI | Rewards Credit Card API | |
|---|---|---|
| Cards covered | 353 cards from 39 issuers | “Nearly 4,000 with cards being added frequently”; “99.5% of the credit cards issued in the United States”Source: FAQ, docs |
| Countries | United States and Canada (TD, RBC, CIBC, BMO, Scotiabank, Amex Canada and more), fees in CAD | United States; their docs and changelog don't mention CanadaSource: docs, changelog |
| How the data is collected | Read from each issuer's own card pages and terms by a scraper with LLM extraction, checked by automatic publish rules | “All data is manually entered into our database by hand”, “manually reviewed and double checked for accuracy”Source: FAQ, docs |
| Refresh | Every card re-checked against the issuer's site every Friday night | “Updated daily”Source: rewardscc.com |
| Free plan | 100 calls a day, 3,000 a month, no credit card required; basic fields and each card's top 3 reward rates | No free plan listed; “You must have an active subscription”Source: docs, getting started |
| Paid plans | Starter $29/mo (7-day trial), Pro $79/mo, Enterprise $249/mo, all self-serve | BASIC $29/month, 2,500 calls; PRO $49/month, 10,000 calls; ULTRA $99/month, 50,000 calls; MEGA $199/month, 200,000 calls (caching and storage allowed; sign up by email); SUPREME $499/month, 1,000,000 calls (caching and storage allowed; sign up by email); ENTERPRISE: contact them. BASIC, PRO and ULTRA are bought on RapidAPISource: docs, RapidAPI listing |
| Caching and storing the data | Allowed on every active plan, Free included (trial data: evaluation only); deleted within 30 days after a plan ends | “Caching and downloading of data is permitted under the MEGA, SUPREME and ENTERPRISE plans only” (FAQ); the approved-use page says MEGA and SUPREME; delete “immediately” at cancellationSource: FAQ, approved use of data |
| Redistribution | Display it in your own product; no API, feed or bulk export of the raw data | Use it on a site or app you own; no API of your own, no mass downloads such as a CSV, no resaleSource: approved use of data, FAQ |
| Card images | Enterprise plan, where a real image of the card is known | “Card images for over 95% of the cards”, hosted by themSource: rewardscc.com |
| Transfer partners and spend bonuses | Transfer partner directory and per-card partners, spend bonuses (Pro) | Point transfer program endpoints and spend bonus categoriesSource: getting started, docs |
| Merchant and bank-transaction lookups | None: rates are by spending category (/v1/cards/best) | Google Maps merchant endpoints (top cards for a place) and a Plaid spend-category endpointSource: docs, changelog |
| Change history and offer changes | Per-card change history, offer history and notable offer changes (Pro) | Not mentioned in their docsSource: docs |
| Application rules | Issuer rules such as Chase 5/24 and Amex once-per-lifetime, every plan | Not mentioned in their docsSource: docs |
| Webhooks and GraphQL | card.created / card.updated / card.deleted webhooks and GraphQL (Enterprise) | Not mentioned in their docsSource: docs |
| SDKs and spec | TypeScript (@cardapi/client) and Python (cardapi) SDKs, OpenAPI spec, Postman collection | Not mentioned in their docsSource: docs |
| Rate limit | Per plan, from 100 calls a day (Free) to 20,000 (Enterprise) | 15 requests a second for direct subscribers (changelog, May 2024)Source: changelog |
Checked 15 Oct 2026. CardAPI's side is from its docs, pricing and terms.
Where Rewards Credit Card API is the better choice
- You need the long tail of US cards. Nearly 4,000 cards against CardAPI's 353 is a big difference if your users hold credit-union and small-bank cards.
- You want card images on a lower plan: they report images for over 95% of their cards.
- Your product starts from a merchant or a bank transaction: their Google Maps and Plaid endpoints answer "which card for this place or this purchase" directly.
- You want data entered and double-checked by people, updated daily, and buying through RapidAPI suits you.
Where CardAPI is the better choice
- Canada. Canadian cards are covered as fully as US ones, with fees in CAD. The Canadian credit card API.
- You want to start free and self-serve: 100 calls a day with no credit card required, and every paid plan is bought on the site.
- You want to cache what you fetch on any active plan, Free included, rather than only on the top tiers.
- You track changes: card history, offer history, notable offer changes and webhooks when a card changes, plus issuer application rules (Chase 5/24, Amex once-per-lifetime).
- You want typed SDKs, an OpenAPI spec and GraphQL.
See for yourself
Compare cards live with no account on the comparison demo, see which data each issuer's cards have on coverage, or make a first request in a minute.