Card Validator API
Overview
To use Card Validator, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/cardvalidatorExample
How to call the Card Validator API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/cardvalidator?number=4900264223817524" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/cardvalidator?number=4900264223817524', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/cardvalidator?number=4900264223817524', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/cardvalidator?number=4900264223817524", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"card": {
"niceType": "Visa",
"type": "visa",
"patterns": [
4
],
"gaps": [
4,
8,
12
],
"lengths": [
16,
18,
19
],
"code": {
"name": "CVV",
"size": 3
},
"matchStrength": 1
},
"cardNumber": "4900264223817524",
"isValid": true
}
}Authentication
The Card Validator API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Card Validator API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Card Validator API:
Validate Card Number
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
number | string | required | The card number to validate Length: 13 - 19 chars | - |
Response
The Card Validator API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<card>
<niceType>Visa</niceType>
<type>visa</type>
<patterns>
<pattern>4</pattern>
</patterns>
<gaps>
<gap>4</gap>
<gap>8</gap>
<gap>12</gap>
</gaps>
<lengths>
<length>16</length>
<length>18</length>
<length>19</length>
</lengths>
<code>
<name>CVV</name>
<size>3</size>
</code>
<matchStrength>1</matchStrength>
</card>
<cardNumber>4900264223817524</cardNumber>
<isValid>true</isValid>
</data>
</response>
status: ok
error: null
data:
card:
niceType: Visa
type: visa
patterns:
- 4
gaps:
- 4
- 8
- 12
lengths:
- 16
- 18
- 19
code:
name: CVV
size: 3
matchStrength: 1
cardNumber: '4900264223817524'
isValid: true
| key | value |
|---|---|
| card | {niceType:Visa,type:visa,patterns:[4],gaps:[4,8,12],lengths:[16,18,19],code:{name:CVV,size:3},matchStrength:1} |
| cardNumber | 4900264223817524 |
| isValid | true |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
card | object | Card identification and validation details | |
â”” niceType | string | Human-readable card type name like Visa | |
â”” typePremium | string | Machine-readable card type identifier | |
â”” patternsPremium | array | Starting digit patterns for card type | |
â”” gapsPremium | array | Character positions for spacing formatting | |
â”” lengthsPremium | array | Valid card length values in digits | |
â”” codePremium | object | Security code specifications for card | |
â”” name | string | Name of security code like CVV | |
â”” size | number | Number of digits in security code | |
â”” matchStrengthPremium | number | Confidence level of card type match | |
cardNumber | string | The validated card number provided | |
isValid | boolean | Whether the card number is valid |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Card Validator through GraphQL to combine it with other API calls in a single request. Query only the card validator data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
cardvalidator(
input: {
number: "4900264223817524"
}
) {
card {
niceType
type
patterns
gaps
lengths
code {
name
size
}
matchStrength
}
cardNumber
isValid
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Card Validator API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Card Validator requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Card Validator API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Card Validator
Official Card Validator packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Card Validator works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Card Validator?
How many credits does Card Validator cost?
Each successful Card Validator API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful card validator lookups.
Can I use Card Validator in production?
The free plan is for testing and development only. For production use of Card Validator, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Card Validator from a browser?
What happens if I exceed my Card Validator credit limit?
When you reach your monthly credit limit, Card Validator API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








