Mockaroo API
Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting QaapiKey11 EndpointsREST
For Agents
Generate realistic synthetic test data in JSON, CSV, SQL, XML, or TXT formats and pull saved Mockaroo datasets and downloads.
Use for: I need to generate 100 fake user records as JSON, Generate a CSV of synthetic transactions for load testing, Get the list of Mockaroo field types I can use in a schema, Retrieve a saved Mockaroo dataset by name
Not supported: Does not handle production data anonymisation, database hosting, or schema migrations - use for generating synthetic test data only.
Mockaroo generates realistic synthetic test data on demand in JSON, CSV, TXT, SQL, and XML formats so engineers can populate development environments, run load tests, or seed analytics pipelines without using real customer data. The API exposes 11 endpoints covering field type metadata, multi-format generation, saved schemas under /api/datasets, and downloadable result files. Authentication is by API key in either the X-API-Key header or a key query parameter.
Install Jentic One Beta
Connect the Mockaroo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mockaroo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmockaroo.com%2Fmockaroo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmockaroo.com%2Fmockaroo" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Mockaroo API.
Generate fake data in JSON via /api/generate.json with a custom field schema
Generate the same dataset as CSV, SQL, TXT, or XML through /api/generate.csv, /api/generate.sql, /api/generate.txt, or /api/generate.xml
Run a fully custom format using a Mockaroo template at /api/generate.custom
Inspect the catalogue of supported field types via /api/types
Reference a saved schema by name through /api/datasets/{name}
Retrieve a previously generated download by ID at /api/downloads/{id}
Authorise requests with an API key in either header or query parameter form
Use Cases
Patterns agents use Mockaroo API for, with concrete tasks.
★ Seed test data for a development database
Engineers seed a development database by POSTing a field schema to /api/generate.sql and capturing the returned INSERT statements, or by calling /api/generate.json and importing the result into the application directly. The same schema can be replayed across CI runs to give every environment a consistent baseline of synthetic data.
POST a 5-field schema to /api/generate.sql with count=500 and a target table name, capture the INSERT statements, and run them against the dev database.
Load testing fixtures
Performance engineers generate large CSV or JSON fixtures via /api/generate.csv and /api/generate.json to drive load tests against APIs and analytics pipelines. The format flexibility means the same logical dataset can be rendered for whichever ingestion path the load test exercises, without rebuilding the schema each time.
Call /api/generate.csv with count=10000 and a custom schema, save the response to fixtures.csv, and feed it to the load test runner.
Saved dataset replay for QA
QA teams reference a saved Mockaroo schema through /api/datasets/{name} so the same well-known fixture can be regenerated on demand for regression tests. Combined with /api/downloads/{id} for previously generated files, this gives QA a stable, reproducible test data surface across environments.
GET /api/datasets/'customer_baseline' to regenerate the saved customer dataset, and store the response under tests/fixtures/customer_baseline.json.
Agent integration via Jentic
An AI assistant building test harnesses can search Jentic for 'generate fake JSON test data', load the /api/generate.json schema, and execute the call without ever holding the Mockaroo API key. The agent can then write the response straight into a fixtures directory and trigger downstream tests.
Search Jentic for 'generate fake JSON test data', load the /api/generate.json schema, execute it for 50 records using the 'user' field set, and write the result to fixtures/users.json.
Key Endpoints
11 endpoints — mockaroo generates realistic synthetic test data on demand in json, csv, txt, sql, and xml formats so engineers can populate development environments, run load tests, or seed analytics pipelines without using real customer data.
METHOD
PATH
DESCRIPTION
GET
/api/types
List supported field types
POST
/api/generate.json
Generate JSON synthetic data
POST
/api/generate.csv
Generate CSV synthetic data
POST
/api/generate.sql
Generate SQL INSERT statements
POST
/api/generate.xml
Generate XML synthetic data
POST
/api/generate.custom
Generate output using a custom Mockaroo template
GET
/api/datasets/{name}
Reference a saved dataset by name
GET
/api/downloads/{id}
Retrieve a previously generated download
GET
/api/types
List supported field types
POST
/api/generate.json
Generate JSON synthetic data
POST
/api/generate.csv
Generate CSV synthetic data
POST
/api/generate.sql
Generate SQL INSERT statements
POST
/api/generate.xml
Generate XML synthetic data
POST
/api/generate.custom
Generate output using a custom Mockaroo template
GET
/api/datasets/{name}
Reference a saved dataset by name
GET
/api/downloads/{id}
Retrieve a previously generated download
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mockaroo API by hand means handling its API key auth, picking the right generate format among JSON, CSV, SQL, and XML, and posting each schema yourself. Through Jentic you install once, import the Mockaroo API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Mockaroo's schemas travel in the request body and its dataset and download ids sit in the URL path, so scope your agent by limiting it to the operations it needs, such as listing types and generating JSON data. You leave out dataset downloads so the agent produces synthetic test data without pulling saved datasets.
Credential isolation
Your Mockaroo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate fake JSON test data' or 'list available Mockaroo field types', and Jentic returns the matching Mockaroo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mockaroo API through Jentic.
What authentication does the Mockaroo API use?
Mockaroo accepts an API key in the X-API-Key header or as the 'key' query parameter on each request. Through Jentic the API key is held in your Jentic One instance and injected automatically; the agent never sees the raw key.
Can I generate SQL INSERT statements directly?
Yes. POST your schema to /api/generate.sql with the desired row count and table name and Mockaroo returns the INSERT statements ready to run against a target database. The same schema can be reused at /api/generate.json or /api/generate.csv to switch formats.
What are the rate limits for the Mockaroo API?
Limits are tied to the Mockaroo plan rather than the OpenAPI specification: the free tier permits 200 requests per day with up to 1,000 rows per call, and paid plans raise both ceilings. Confirm current limits at mockaroo.com/docs.
How do I generate JSON test data through Jentic?
Run pip install jentic, search Jentic for 'generate fake JSON test data', load the /api/generate.json schema, and execute it with your field schema and row count. Jentic injects the API key and returns the JSON payload to the agent.
Can I save a schema and reuse it across runs?
Yes. Save the schema under a name in the Mockaroo UI, then call GET /api/datasets/{name} to regenerate the same fixture on demand from the API. This is the recommended path for repeatable QA fixtures.
Is the Mockaroo API free to use?
Mockaroo offers a free tier capped at 200 daily API calls and 1,000 rows per call; higher volumes require a paid plan. Get started with Jentic One, the self-hosted execution layer.
Can I limit what my agent is allowed to do with the Mockaroo API?
Yes. Because you run Jentic One yourself, your own rules decide which Mockaroo operations and credentials the agent may use. You can allow only the calls it needs, such as listing field types at /api/types and generating data at /api/generate.json, while leaving out saved-dataset access at /api/datasets/{name} and file retrieval at /api/downloads/{id}. This lets the agent produce synthetic test data without pulling saved datasets or downloads.
GET STARTED