Generate full synthetic identities with realistic address
Generate full synthetic identities with realistic address, contact, and Luhn-valid credit card details for testing
Request
- x-api-key: <your-api-key>
- Content-Type: application/json
Response
{
"count": 3,
"identities": [
{
"address": {
"city": "Wrocław",
"country": "PL",
"countryCode": "PL",
"postalCode": "53-332",
"state": "<state>",
"street": "Powstańców Śląskich 5/212"
},
"creditCard": {
"cvv": "123",
"expirationDate": "2026-09-08",
"number": "<number>",
"type": "standard"
},
"dateOfBirth": "2026-09-08",
"email": "ada@example.com",
"firstName": "Ada",
"fullName": "Ada Lovelace",
"gender": "<gender>",
"lastName": "Lovelace",
"phone": "+48600700800",
"ssn": "078-05-1120"
}
],
"status": "success",
"tokensDeducted": 1
}What it does
Generate full synthetic identities with realistic address, contact, and Luhn-valid credit card details for testing
Request
Body
| Field | Type | Required | Description |
|---|---|---|---|
count | integer | no | |
gender | enum | no | One of: any, male, female, neutral. |
includeAddress | boolean | no | |
includeCard | boolean | no | |
locale | enum | no | One of: US, UK, CA, DE. |
Example request
{
"count": 1,
"gender": "any",
"includeAddress": true,
"includeCard": true,
"locale": "US"
}Response
| Field | Type | Description |
|---|---|---|
count | integer | |
identities | array<object> | |
↳ address | object | |
↳ creditCard | object | |
↳ dateOfBirth | string | |
↳ email | string | |
↳ firstName | string | |
↳ fullName | string | |
↳ gender | string | |
↳ lastName | string | |
↳ phone | string | |
↳ ssn | string | |
status | string | |
tokensDeducted | integer |
Example response
{
"count": 3,
"identities": [
{
"address": {
"city": "Wrocław",
"country": "PL",
"countryCode": "PL",
"postalCode": "53-332",
"state": "<state>",
"street": "Powstańców Śląskich 5/212"
},
"creditCard": {
"cvv": "123",
"expirationDate": "2026-09-08",
"number": "<number>",
"type": "standard"
},
"dateOfBirth": "2026-09-08",
"email": "ada@example.com",
"firstName": "Ada",
"fullName": "Ada Lovelace",
"gender": "<gender>",
"lastName": "Lovelace",
"phone": "+48600700800",
"ssn": "078-05-1120"
}
],
"status": "success",
"tokensDeducted": 1
}Errors
Every error answers with the same envelope: an HTTP status, a machine code and a sentence.
400 | The body or a parameter failed validation. The details array names the field. |
401 | No key, a revoked key or a wrong header. Send x-api-key. |
402 | The wallet cannot cover this call. Top up or wait for the monthly grant. |
404 | The resource does not exist, or it is not yours. Both answer identically and cost nothing. |
429 | Over the per-minute quota of your tier. Back off and retry. |
5xx | Upstream refused or timed out. The call is not billed. |
Code
curl -X POST 'https://app.castomapi.com/v1/generate/identity' \
-H 'x-api-key: <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"count": 1, "gender": "any", "includeAddress": true, "includeCard": true, "locale": "US"}'const res = await fetch('https://app.castomapi.com/v1/generate/identity', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"count": 1, "gender": "any", "includeAddress": true, "includeCard": true, "locale": "US"})
});
const data = await res.json();
console.log(data);import { request } from 'node:https';
// Node 18+ has fetch built in
const res = await fetch('https://app.castomapi.com/v1/generate/identity', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"count": 1, "gender": "any", "includeAddress": true, "includeCard": true, "locale": "US"})
});
const data = await res.json();
console.log(data);import requests
res = requests.post(
'https://app.castomapi.com/v1/generate/identity',
headers={'x-api-key': '<your-api-key>'},
json={"count": 1, "gender": "any", "includeAddress": True, "includeCard": True, "locale": "US"},
timeout=30,
)
print(res.json())<?php
$ch = curl_init('https://app.castomapi.com/v1/generate/identity');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode(['count' => 1, 'gender' => 'any', 'includeAddress' => true, 'includeCard' => true, 'locale' => 'US']),
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);Cost and limits
This operation needs no API key and costs nothing: called without a key it answers 200 and deducts zero tokens, up to 10 requests a minute per IP address.
Rate limits per minute
| No key | 10 |
| Free | 60 |
| Pro | 300 |
| Enterprise | 1200 |
Questions
What does Generate full synthetic identities with realistic address cost?
This operation needs no API key and costs nothing: called without a key it answers 200 and deducts zero tokens, up to 10 requests a minute per IP address.
How do I authenticate?
Send your key in the x-api-key header. One key covers every metered endpoint; there is nothing to enable per endpoint.
Can I send an Authorization: Bearer token instead?
Not for a metered endpoint — those take the x-api-key header and nothing else. Bearer tokens belong to the account side: the dashboard and account APIs accept a JWT session, and castomapi-auth issues those through a standard OAuth2 handshake, with authorization code, client credentials and refresh grants. The auth service page covers it.
What are the limits?
10 requests a minute per IP with no key at all, 60 a minute on the free tier, 300 on Pro, 1200 on Enterprise. Above the no-key tier the quota is per account, across every endpoint.
OpenAPI: https://app.castomapi.com/docs/json