Faker API (fakerapi.it) is a free, public REST API that generates realistic fake data for development and testing, with no registration or API keys. Developers retrieve mock data across many categories — persons, addresses, companies, products, credit cards, images, and custom fields — with multiple locales, a seed for reproducibility, and batches of up to 1,000 records, ideal for seeding databases and test suites.
Power end-to-end data operations for your Faker API API with Nexla. Our bi-directional Faker API connector is purpose-built for Faker API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Faker API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Faker API workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Faker API (fakerapi.it) is a completely free, public REST API that requires no registration, account creation, or API keys. You can begin retrieving fake data immediately without any sign-up process.
The only configuration required is selecting the base URL for the API version you want to use:
v2 (Latest) — https://fakerapi.it/api/v2 — Recommended for all new integrations. Version 2 includes the latest resources and features, including the updated Persons endpoint with the other gender option.
v1 (Legacy) — https://fakerapi.it/api/v1 — Available for compatibility with existing integrations that were built against the v1 API. New integrations should use v2.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Select the Faker API base URL from the Faker API Base URL field. This determines which version of the Faker API will be used for all data requests made with this credential.
v2 (Latest) — https://fakerapi.it/api/v2 — Select this option for all new integrations. This is the current, actively maintained version of the API.
v1 (Legacy) — https://fakerapi.it/api/v1 — Select this option only if you have an existing integration that requires compatibility with the v1 API.
The base URL defaults to https://fakerapi.it/api/v2. Unless you have a specific reason to use v1, leaving the default value is recommended.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with a new data source.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Faker API connector tile, then select the credential that will be used to connect to the Faker API instance, and click Next; or, create a new Faker API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Faker API endpoints. Each template is designed specifically for the corresponding Faker API resource, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Persons
Retrieves fake person records including first name, last name, email address, phone number, gender, date of birth, and a nested address object. Use this endpoint to generate test user profiles, populate demographic datasets, or validate pipelines that process personal identity data.
Enter the number of person records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to control the language and regional formatting of generated names, addresses, and other locale-sensitive fields. The default is en_US. Available locales include:
English (US) — en_US
English (UK) — en_GB
French (France) — fr_FR
German (Germany) — de_DE
Spanish (Spain) — es_ES
Italian (Italy) — it_IT
Japanese — ja_JP
Chinese (Simplified) — zh_CN
Portuguese (Brazil) — pt_BR
Russian — ru_RU
Optionally, enter an integer in the Seed field to produce reproducible results. When a seed value is provided, the same request will always return the same set of records. Leave this field empty to generate different random data on each run.
Optionally, select a value from the Gender dropdown to filter results to a specific gender. Available options are:
Any (default) — Returns a mix of genders.
Male — Returns only male person records.
Female — Returns only female person records.
Other — Returns person records with a non-binary gender designation.
Optionally, enter a date in YYYY-MM-DD format in the Birthday Start field to restrict results to persons born on or after the specified date.
Optionally, enter a date in YYYY-MM-DD format in the Birthday End field to restrict results to persons born on or before the specified date. Use Birthday Start and Birthday End together to produce records within a specific age range.
Each person record returned by this endpoint includes a nested address object. Nexla will automatically flatten or preserve this nested structure based on your Nexset schema settings.
List Addresses
Retrieves fake address records including street name, street address, city, ZIP/postal code, state, and country. Use this endpoint to generate test shipping or billing address datasets, validate address-parsing pipelines, or populate location fields in development databases.
Enter the number of address records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to control the language and regional formatting of the generated addresses. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
Optionally, enter an ISO 3166-1 alpha-2 country code in the Country Code field (for example, US, FR, or DE) to restrict all generated addresses to that specific country. Leave this field empty to receive addresses from a mix of countries.
List Companies
Retrieves fake company records including company name, email address, VAT number, phone number, country, and a nested address. Use this endpoint to generate test B2B datasets, populate company lookup tables, or test pipelines that process organizational data.
Enter the number of company records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to control the regional formatting of company names and other locale-sensitive fields. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
List Users
Retrieves fake user account records including username, email address, hashed password, IP address, MAC address, website URL, and registration timestamp. Use this endpoint to test user authentication flows, populate user tables in development databases, or validate pipelines that handle account data.
Enter the number of user records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to control locale-sensitive field values. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
Password values returned by this endpoint are randomly generated strings and are not real credentials. They are provided solely as test data to simulate the shape of a user record.
List Products
Retrieves fake product records including product name, EAN barcode, description, stock quantity, price, and category identifiers. Use this endpoint to populate product catalogs in development environments, test e-commerce pipelines, or build demo storefronts.
Enter the number of product records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
Optionally, enter a tax percentage integer in the Tax Percentage field (for example, 10 or 20) to include a calculated tax amount in each product record. Leave this field empty to omit tax information.
Optionally, select the format in which category identifiers are returned from the Categories Type dropdown. Available options are:
UUID (default) — Returns category identifiers as UUID strings.
Integer — Returns category identifiers as integers.
String — Returns category identifiers as human-readable strings.
Optionally, enter an integer in the Categories Per Product field to control how many category identifiers are included per product record. The default is 1.
Optionally, enter a decimal value in the Minimum Price field to set a lower bound on generated product prices.
Optionally, enter a decimal value in the Maximum Price field to set an upper bound on generated product prices. Use Minimum Price and Maximum Price together to generate products within a realistic price range for your use case.
List Books
Retrieves fake book records including title, author name, genre, description, ISBN, publisher name, and publication date. Use this endpoint to populate library or catalog datasets, build demo content applications, or test pipelines that process bibliographic data.
Enter the number of book records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to influence the language of generated titles and author names. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
List Credit Cards
Retrieves fake credit card records including card type (e.g., Visa, MasterCard), card number, expiration date, and owner name. Use this endpoint to test payment form validation, populate mock payment records, or build demos that simulate financial transactions.
Enter the number of credit card records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
For Testing Purposes Only
Credit card numbers returned by this endpoint are randomly generated and are not valid for any real financial transaction. Never use this data in production systems or present it as real payment information.
List Images
Retrieves fake image metadata including a URL, title, and description. Image URLs link to actual placeholder images hosted by the Faker API service. Use this endpoint to populate image fields in development environments, test media rendering pipelines, or build UI prototypes with realistic placeholder assets.
Enter the number of image records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different image URLs on each run.
Optionally, select an image type from the Image Type dropdown. Available options are:
Any (default) — Returns general-purpose placeholder image URLs.
Pokemon — Returns Pokémon image URLs, useful for distinct, colorful placeholder images in UI testing.
Optionally, enter a pixel value in the Image Width field to set the width of the placeholder images. The default is 640 pixels.
Optionally, enter a pixel value in the Image Height field to set the height of the placeholder images. The default is 480 pixels.
List Places
Retrieves fake geographic place records including city name, state/region, country, and latitude/longitude coordinates. Use this endpoint to generate test geolocation datasets, populate location fields in development databases, or test mapping and spatial analytics pipelines.
Enter the number of place records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to influence the language and regional formatting of place names. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random places on each run.
List Texts
Retrieves fake text content as an array of character strings. Use this endpoint to generate filler content for UI mockups, populate text fields in development databases, or test pipelines that process unstructured text data.
Enter the number of text records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown to control the language of generated text. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random text on each run.
Optionally, enter an integer in the Characters field to set the maximum number of characters in each generated text string. The default is 200 characters.
List Custom Fields
Retrieves fake records with a fully custom schema defined by you. Instead of using a fixed resource type, this endpoint lets you specify exactly which fields to include and what type of fake data each field should contain. Use this endpoint when none of the pre-built resource templates match your target data shape, or when you need a highly specific combination of field types.
Enter the number of custom records to retrieve in the Quantity field. Accepted values are 1–1000. The default is 10.
Optionally, select a locale from the Locale dropdown. The default is en_US.
Optionally, enter an integer in the Seed field to produce reproducible results. Leave this field empty to generate different random data on each run.
Enter your custom field definitions in the Custom Field Definitions field as a URL-encoded query string, where each key is the output field name you want in the response and each value is the Faker API field type that will generate the data. For example:
name=firstName&email=freeEmail — Returns records with a name field (first name) and an email field (free-provider email address).
phone=phoneNumber&zip=postcode&city=city — Returns records with phone, ZIP code, and city fields.
Common field type values include: firstName, lastName, freeEmail, companyEmail, phoneNumber, postcode, city, streetAddress, country, url, userName, paragraph, sentence, currencyCode, ip, and iban. For a complete list of supported field types, refer to the official Faker API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Faker API data sources can also be manually configured to ingest data from any valid Faker API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method (all Faker API endpoints use GET), endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The base URL for the latest API version is https://fakerapi.it/api/v2 (or https://fakerapi.it/api/v1 for legacy), followed by the resource path and any query parameters, for example:
All Faker API parameter names are prefixed with an underscore, for example https://fakerapi.it/api/v2/persons?_quantity=50&_locale=fr_FR&_gender=female. Common parameters supported on every endpoint are _quantity (1–1000, default 10), _locale (default en_US), and _seed (integer for reproducible results); refer to the Faker API documentation for the full parameter list per resource. Date/time macros are most useful when combined with the _birthday_start and _birthday_end parameters on the List Persons endpoint, to dynamically scope generated records to persons born within a rolling date window relative to the current date. The path to data for all Faker API endpoints is $.data[*]; the top-level total and code fields sit outside this path and can be captured with a metadata path of $. Faker API does not require any authentication headers — all endpoints are publicly accessible without tokens or credentials; you only need to add request headers if your network environment requires specific proxy or routing headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Faker API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
