Free Fake Data API

Quick start

One request, no setup. This returns a single complete US identity as JSON:

curl "https://fakenamely.com/api/v1/identity"

Add count for more records, country to change the locale, and seed to make the result reproducible. Nothing else is required — there is no registration step and no key to attach.

Endpoints

All endpoints are GET-only and read-only. Responses use the same envelope; csv and sql return text instead.

Parameters

Every parameter is optional. Each endpoint accepts a subset — see the per-endpoint notes below.

Endpoint reference

curl "https://fakenamely.com/api/v1/identity?count=2&country=de&gender=female"

curl "https://fakenamely.com/api/v1/address?count=5&state=CA&format=csv"

curl "https://fakenamely.com/api/v1/name?count=20&country=jp"

curl "https://fakenamely.com/api/v1/field?type=zip&count=5"

curl "https://fakenamely.com/api/v1/validate?type=iban&value=GB82WEST12345698765432"

curl "https://fakenamely.com/api/v1/imei?count=3"

Client examples

Each sample runs unmodified — there is no key to paste in and no placeholder to replace.

# Ten German female identities
curl "https://fakenamely.com/api/v1/identity?count=10&country=de&gender=female"

# Reproducible: the same seed always returns the same records
curl "https://fakenamely.com/api/v1/identity?count=5&seed=checkout-suite-v3"

# 50 California addresses as CSV, straight to a file
curl "https://fakenamely.com/api/v1/address?count=50&state=CA&format=csv" -o addresses.csv

const res = await fetch(
  "https://fakenamely.com/api/v1/identity?count=5&country=jp",
);
const { success, data, error } = await res.json();

if (!success) throw new Error(error);

for (const person of data) {
  console.info(person.name.full, person.address.city);
}

import requests

res = requests.get(
    "https://fakenamely.com/api/v1/identity",
    params={"count": 5, "country": "gb", "seed": "fixtures-2026"},
    timeout=10,
)
res.raise_for_status()
payload = res.json()

if not payload["success"]:
    raise RuntimeError(payload["error"])

for person in payload["data"]:
    print(person["name"]["full"], person["address"]["postalCode"])

<?php
$query = http_build_query([
    'count'   => 5,
    'country' => 'fr',
    'seed'    => 'fixtures-2026',
]);

$body = file_get_contents("https://fakenamely.com/api/v1/identity?{$query}");
$payload = json_decode($body, true);

if (!$payload['success']) {
    throw new RuntimeException($payload['error']);
}

foreach ($payload['data'] as $person) {
    echo $person['name']['full'], ' — ', $person['address']['city'], PHP_EOL;
}

const https = require("node:https");

https.get(
  "https://fakenamely.com/api/v1/name?count=25&country=se",
  (res) => {
    let body = "";
    res.on("data", (chunk) => (body += chunk));
    res.on("end", () => {
      const { data } = JSON.parse(body);
      console.info(data.map((n) => n.full).join("\n"));
    });
  },
).on("error", console.error);

Validating a value, not just generating one

The same checksum rules that produce a value can verify one, and if you are testing your own validation you usually want both halves. /api/v1/validate runs the identical pure functions behind the on-site validator tools, so an API verdict and a page verdict can never disagree. Nothing you submit is logged or stored.

# Is this IBAN structurally valid?
curl "https://fakenamely.com/api/v1/validate?type=iban&value=GB82WEST12345698765432"

# Card number: Luhn check plus scheme detection
curl "https://fakenamely.com/api/v1/validate?type=card&value=4242424242424242"

# VIN, returning the check digit it should have had
curl "https://fakenamely.com/api/v1/validate?type=vin&value=1HGCM82633A004352"

The national-identity validators (SSN, SIN, NINO) exist as tool pages but are deliberately not exposed here. Making government-identity checking programmatically scriptable is a different act from putting one behind a form; this endpoint is for developer utilities — checksum and format rules that tell you a value is well-formed and nothing more.

Response format

Every JSON response uses the same envelope, so a client can branch on success alone. data holds the records, error is null on success, and meta carries the seed that produced the payload plus the fictional-data label. On an error, data is null and error explains which parameter was wrong and what values are accepted.

{
  "success": true,
  "data": [
    {
      "seed": "fixtures-2026#0",
      "sex": "female",
      "name": {
        "full": "Margit Lindqvist",
        "first": "Margit",
        "last": "Lindqvist",
        "initials": "ML"
      },
      "address": {
        "street": "4127 Sturegatan",
        "city": "Uppsala",
        "regionLabel": "County",
        "stateOrRegion": "Uppsala",
        "postalCode": "75236",
        "country": "Sweden",
        "countryCode": "SE",
        "geo": { "lat": 59.86, "lng": 17.64 }
      },
      "contact": { "phone": "+46 18 555 0142", "email": "margit.lindqvist@example.com" },
      "personal": { "birthday": "1988-04-19", "age": 37, "nationalId": { "masked": "8804XX-XXXX" } },
      "meta": { "fake": true, "disclaimer": "…" }
    }
  ],
  "error": null,
  "meta": {
    "count": 1,
    "seed": "fixtures-2026",
    "deterministic": true,
    "country": "sweden",
    "fictional": true,
    "disclaimer": "Randomly generated fictional data …",
    "docs": "https://fakenamely.com/api"
  }
}

Reproducible output: the seed parameter

Generation is a pure function of the seed. The same seed and parameters always return byte-identical records — on this API, in the on-site generator, and in the bulk exporter, because all three run the same engine. Record i of a multi-record response uses the row seed {seed}#{i}.

That makes API output usable where random data normally is not. A seeded request can be committed as a test fixture, referenced in a bug report, or used in a snapshot test that has to produce the same diff on every run. Seeded requests are also cached at the edge, so replaying a fixture is fast. Omit the seed and you get fresh random data with a freshly minted seed returned in meta.seed — keep that value if you want to reproduce the batch later.

Rate limits and fair use

The limit is approximately 120 requests per minute per IP address, with no daily cap and no key to apply for. It is stated approximately on purpose: the limiter is per-instance and best-effort, so the exact ceiling moves with how many instances are serving traffic. Treat it as a courtesy threshold rather than a contract, and handle 429 by honouring the Retry-After header.

For datasets larger than a single request, do not loop the API — use the bulk exporter, which builds up to 100,000 rows in the browser and downloads them as CSV, JSON or SQL with no request at all. It is faster than paginating and it costs this site nothing to serve.

The API is free to use, including in commercial projects. Attribution is appreciated but not required. There is no paid tier, and no plan to add one — the site is funded by advertising on the pages, which is why the data can stay free.

OpenAPI specification and tooling

The full contract is published as an OpenAPI 3.1 document at /api/openapi.json. Import that URL into Postman, Insomnia, Bruno, Hoppscotch or an OpenAPI code generator to get a typed client without writing any request code. The spec is generated from the same definitions that drive this page, so it cannot describe an endpoint that does not exist.

# Import into any OpenAPI-aware tool
curl "https://fakenamely.com/api/openapi.json" -o fakename-openapi.json

# Or generate a typed client (example: TypeScript)
npx openapi-typescript "https://fakenamely.com/api/openapi.json" -o fakename.d.ts

Selecting columns for CSV and SQL

Pass fields to flatten the response into column-selected rows, and format=csv or format=sql to get text instead of JSON. SQL output emits INSERT statements against an identities table, which is usually enough to seed a development database directly from a shell pipe. There are 32 available column keys:

fullName, firstName, lastName, sex, street, city, state, stateCode, postalCode, country, lat, lng, phone, email, username, password, website, birthday, age, zodiac, nationalId, heightCm, weightKg, bloodType, cardType, cardNumber, cardCvv, cardExpiry, currency, vehicle, vin, guid

# Seed a dev database straight from the API
curl "https://fakenamely.com/api/v1/identity?count=100&seed=dev-seed&format=sql&fields=fullName,email,city,postalCode" \
  | psql "$DATABASE_URL"

Supported countries

Pass either the slug or the ISO-3166 alpha-2 code. The country controls the name pools, address format, regional subdivision label, phone format, postal-code shape and currency — not just a country string appended to a US-shaped record.

united-states (us), united-kingdom (gb), canada (ca), australia (au), germany (de), france (fr), spain (es), mexico (mx), italy (it), japan (jp), south-korea (kr), china (cn), brazil (br), netherlands (nl), sweden (se), norway (no), denmark (dk), finland (fi), poland (pl), russia (ru), turkey (tr), greece (gr), romania (ro), hungary (hu), ukraine (ua), vietnam (vn), indonesia (id), thailand (th), israel (il), austria (at), switzerland (ch), india (in), ireland (ie), portugal (pt), taiwan (tw), belgium (be)

What this data is not for

Every record is synthetic and describes no real person. National-ID placeholders are returned masked and use never-issued number ranges; payment-card numbers come from published sandbox test ranges and cannot be charged; phone numbers use reserved fiction ranges; IMEI values use a reserved test type-allocation code and are not assigned to any device.

Use it for software testing, QA fixtures, database seeding, demos, documentation, screenshots and load testing. Do not use it for fraud, impersonation, shipping, billing, KYC, tax, government, employment, banking, medical or legal identity purposes, or anywhere accurate real information is required. Every response repeats this in meta.disclaimer so the constraint travels with the data.

Frequently asked questions

Related pages

• Bulk export up to 100,000 rows
• Fake identity generator
• Single-field generators
• Generators by country
• US addresses by state
• Free validators
• Guide: deterministic test-data seeding
• Guide: test data generation