POST /v1/core/random-data

Test data

Names, emails, addresses and phone numbers that look real, for filling a test database.

Generate realistic fake data now No key, no code — 1 credit either way.

curl -X POST "$DOATHING_API/v1/core/random-data" \
  -H "x-api-key: $DOATHING_KEY" \
  -H "content-type: application/json" \
  -d '{"options": {"count": 2, "fields": ["name", "email"], "seed": 42}}'

Names, emails, addresses and phone numbers that look real, for filling a test database.

Generate locale-aware fake names, emails, addresses, phone numbers and companies for test fixtures.

Response

The result carries your remaining balance alongside it, so you can track spend without a second call.

{
  "records": [
    {
      "name": "Julie Ward",
      "email": "wjoanne@example.org"
    }
  ],
  "count": 2,
  "locale": "en_GB",
  "request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
  "credits_remaining": 96
}

Cost

1 credit per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.

A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.

Parameters

Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.

NameInTypeDefaultNotes
fieldsoptionsstring[]Any of name, email, phone, address, city, postcode, company, job and more. from name, first_name, last_name, email, username, phone, address, street, city, postcode, country, company, job, date_of_birth, url, ipv4, uuid, sentence, text
countoptionsinteger10Records to generate, up to 500. 1 to …
localeoptionsstring"en_GB"Faker locale, for example en_GB or de_DE. e.g. en_GB, en_US, de_DE, fr_FR
seedoptionsstringFix the output so a fixture is reproducible.