Randommer Getting Started: API Keys & First Request (2026)

Getting started overview

Integrating with the Randommer API involves a sequence of steps designed to enable rapid access to its random data generation capabilities. The process begins with account registration on the Randommer platform, followed by the retrieval of an API key. This key is essential for authenticating all subsequent API requests. Once the API key is obtained, developers can make their first authenticated call to one of Randommer's endpoints, such as generating a random number or string. The API is designed for straightforward implementation, making it suitable for tasks like mocking APIs, populating databases with test data, and automated testing scenarios.

The following table provides a quick reference for the initial setup process:

Create an account and get keys

To begin using Randommer, an account must be created on their official website. This account serves as the central point for managing API usage and accessing your authentication credentials. The registration process typically requires an email address and password, similar to other online service sign-ups.

1. Navigate to the Sign-up Page: Open your web browser and go to the Randommer account registration page.
2. Complete Registration: Fill in the required details, which commonly include an email address and a secure password. Review and accept any terms of service.
3. Verify Email (if prompted): Some services require email verification to activate the account. Check your inbox for a verification link and follow the instructions.
4. Access the Dashboard: Once registered and logged in, you will be redirected to your Randommer dashboard.
5. Locate Your API Key: On the dashboard, your unique API key will be displayed. This key is a string of alphanumeric characters essential for authenticating your requests. It is important to treat this key as sensitive information, as unauthorized access could lead to misuse of your API quota. Copy this key, as it will be used in subsequent steps.

Randommer provides a free tier that allows up to 1000 requests per day without any charge. This tier is suitable for initial testing and development. For higher request volumes, paid plans are available, starting at $5 per month for 50,000 requests daily, as detailed in the Randommer pricing summary.

Your first request

With your API key in hand, you can now make your first authenticated request to the Randommer API. This example demonstrates how to generate a random number using a common command-line tool, cURL. The API key must be included in the X-Api-Key HTTP header for successful authentication.

Prerequisites

• A Randommer API key.
• curl installed on your system. Most Unix-like operating systems and Windows 10/11 with WSL or Git Bash include cURL by default. For Windows users without these, cURL can be downloaded from the cURL download page.

Example: Generating a Random Number

This example targets the /api/v1/random/number endpoint, which generates a specified quantity of random numbers within a given range.

1. Choose an Endpoint: For this example, we'll use the Random Number API endpoint. The documentation specifies parameters such as min, max, and count.
2. Construct the Request: The basic structure of the request will include the base URL, the endpoint, query parameters, and the X-Api-Key header.
3. Execute with cURL: Replace YOUR_API_KEY with the actual API key copied from your Randommer dashboard.

curl -X GET \
  'https://randommer.io/api/v1/random/number?min=1&max=100&count=5' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json'

In this example:

• -X GET specifies the HTTP GET method.
• 'https://randommer.io/api/v1/random/number?min=1&max=100&count=5' is the API endpoint URL, requesting 5 random numbers between 1 and 100.
• -H 'X-Api-Key: YOUR_API_KEY' sets the authentication header with your API key.
• -H 'Content-Type: application/json' indicates that the request expects a JSON response.

Expected Response

A successful response will typically return a JSON array containing the requested random numbers. For the request above, an example response might look like this:

[
  42,
  78,
  15,
  91,
  3
]

This confirms that your API key is correctly configured and that you can successfully interact with the Randommer API.

Common next steps

After successfully making your first request, several common next steps can further enhance your integration with Randommer:

• Explore Other Endpoints: Randommer offers a variety of endpoints for generating different types of random data, including strings, booleans, names, addresses, and more. Review the complete Randommer API documentation to identify other useful endpoints for your specific application needs.
• Integrate into Your Application: Move beyond cURL and integrate the API calls directly into your chosen programming language or framework. Most languages have built-in HTTP client libraries (e.g., Python's requests, JavaScript's fetch, Java's HttpClient) that simplify making web requests.
• Handle Rate Limits: Be aware of the API rate limits associated with your chosen plan (1000 requests/day for the free tier). Implement retry logic with exponential backoff for transient errors and respect HTTP 429 Too Many Requests responses to prevent your IP from being temporarily blocked. The IETF RFC 6585 section 4 defines the 429 status code.
• Secure Your API Key: Ensure your API key is not hardcoded directly into client-side code or publicly exposed repositories. For server-side applications, use environment variables or a secure configuration management system. For client-side applications requiring direct API access, consider implementing a proxy server to manage API key access.
• Monitor Usage: Regularly check your Randommer dashboard to monitor your API usage and ensure you remain within your plan's limits. This helps in anticipating when an upgrade might be necessary.
• Error Handling: Implement robust error handling in your application to gracefully manage API responses that indicate failures (e.g., invalid parameters, authentication issues). The Randommer documentation provides details on common error codes and their meanings.

Troubleshooting the first call

Encountering issues during your first API call is common. Here are some troubleshooting steps for typical problems:

• Invalid API Key (HTTP 401 Unauthorized):
  • Check for typos: Ensure the API key in your request exactly matches the one from your dashboard.
  • Verify header name: The header must be X-Api-Key, with correct capitalization.
  • Expired key: While less common for new accounts, confirm your key is active on the Randommer dashboard.
• Missing Parameters or Invalid Endpoint (HTTP 400 Bad Request, HTTP 404 Not Found):
  • Review documentation: Double-check the Randommer API documentation for the specific endpoint you are calling. Ensure all required parameters are present and correctly formatted (e.g., min, max, count for random numbers).
  • Correct URL: Verify the base URL (https://randommer.io/api/v1/) and the specific endpoint path are accurate.
• Rate Limit Exceeded (HTTP 429 Too Many Requests):
  • If you receive this error, you have sent too many requests within a given timeframe. Wait for a few minutes before retrying.
  • Review your Randommer dashboard for your current usage and plan limits.
  • Consider upgrading your plan if sustained higher usage is required.
• Network Issues:
  • Internet connection: Ensure your device has an active internet connection.
  • Firewall/Proxy: If you are in a corporate network, a firewall or proxy might be blocking the request. Consult your network administrator.
• CORS Issues (Client-side JavaScript):
  • If making requests from a web browser (e.g., using JavaScript's fetch API), Cross-Origin Resource Sharing (CORS) policies can block requests. Randommer's API supports CORS from all origins (Access-Control-Allow-Origin: *), but ensure your browser isn't configured to block it, or use a proxy if necessary. The MDN Web Docs on CORS provide a comprehensive overview.