Privacy.com API

Security / API Key Intermediate HTTPS
Varies by plan (check documentation)

Overview

The Privacy.com API lets developers create virtual, merchant-specific credit card numbers that protect real bank details during online purchases. You can programmatically create, pause, or close cards to control spending and reduce fraud exposure. It's popular for building expense management tools and privacy-focused payment flows.

💡

Beginner Tip

Start by creating a card with a low spend_limit to test the integration safely — set the spend_limit_duration to TRANSACTION so each charge is individually capped.

Available Data

randomly generated data
customizable output format
vehicle make and model
year and specifications
fuel economy
VIN decode data

Example Response

JSON Response
{
  "make": "Toyota",
  "model": "Camry",
  "year": 2025,
  "engine": "2.5L 4-cylinder",
  "fuel_economy": {
    "city_mpg": 28,
    "highway_mpg": 39
  },
  "msrp": 28400
}

Field Reference

token Unique identifier for this virtual card, used in subsequent API calls.
pan The 16-digit virtual card number for making purchases.
cvv Security code for the virtual card.
exp_month Card expiration month.
state Current card status: OPEN, PAUSED, or CLOSED.
spend_limit Maximum spend allowed on this card in cents.

Implementation Example

// ⚠️ Note: This URL may be a documentation page. Check official docs for actual API endpoint.
const url = "https://privacy.com/developer/docs";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized The API key is missing or formatted incorrectly in the Authorization header.
Use the format: Authorization: api-key YOUR_API_KEY (not Bearer).
Card creation fails in sandbox Required fields like memo or type may be missing from the request body.
Include at minimum the type field (SINGLE_USE or MERCHANT_LOCKED) when creating a card via POST /v1/card.
Production API returns 403 Your account may not be approved for API access or production use.
Privacy.com requires manual approval for production API access — contact their team and use the sandbox environment while waiting.

Matrix Score Breakdown

🌐 Reachability 30/30
⚡ Speed 15/20
🔒 Security 15/15
🛠 Developer XP 12/20
✓ Reliability 10/15

Partially tested on Apr 5, 2026

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS UNKNOWN
Category Security
Difficulty Intermediate
Verified: 2026-04-07

Similar APIs

View All →