Privacy.com API

82 A

Metadata Score Metadata estimate · not endpoint-tested

Visit Official Site Compare Alternatives

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

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

randomly generated data

customizable output format

vehicle make and model

year and specifications

fuel economy

VIN decode data

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative

{
  "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

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request

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

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

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.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

How is this scored? →