Overview
Random Generator works by generating random data based on the type specified. It can generate random numbers, strings, dates, and more. The data is generated using advanced algorithms to ensure randomness and unpredictability.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/randomgenerator?type=number&count=10&includeAvatar=true" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/randomgenerator?type=number&count=10&includeAvatar=true', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/randomgenerator?type=number&count=10&includeAvatar=true",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/randomgenerator?type=number&count=10&includeAvatar=true", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
typeOptional | string | The type of random data to generatenumberdicephonedatecoinuuidguidcolor+4default number |
countOptionalPremium | integer | The number of random data to generate (1 to 100) default 1 · range 1–100 |
includeAvatarOptionalPremium | boolean | Include an AI-generated face avatar (only applies when type=name) |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"type": "phone",
"count": 10,
"data": [
"967-950-4587",
"792-611-7468 x1293",
"(933) 311-9829",
"389.357.7403 x793",
"1-621-490-6394",
"1-699-562-6833 x8558",
"875.226.1530 x641",
"744-991-0150 x1974",
"1-393-784-0533 x15199",
"954-876-6958 x0398"
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
type | string | "phone" | The kind of random data generated (e.g. phone, name, email) |
count | number | 10 | Number of random values generated |
data | array | [967-950-4587, ...] | The generated random values; item shape depends on the requested type |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Database Seeding
- Populate staging tables with synthetic names, addresses, and phone numbers before running integration tests against newly deployed schemas.
- UI Prototype Mocking
- Front-end developers render placeholder user profiles with generated usernames, emails, and hex colors while building interface layouts.
- Unique Key Generation
- When verifying record deduplication pipelines, QA engineers inject generated UUIDs and timestamps into intake streams.
- Game Mechanics Simulation
- To test random drop rates and turn orders, game creators draw coin flips and dice rolls directly into prototype loops.
Other ways to use Random Data Generator
Set up Random Data Generator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Generation: