Advisory: We only operate services from the RANDOM.ORG domain. Other sites that claim to be operated by us are impostors. If in doubt, contact us.

Beta Key Migration Guide


We are now in the process of leaving the beta phase for our Core API.

If you have beta API keys, you'll need to upgrade them to production keys in order to avoid an interruption in service. To help with this, we have developed a 3-step upgrade path for our beta key users.

Step 1: Migrate your Beta Key to your RANDOM.ORG Account

Please note: This step is only necessary if you don't see your beta key in your API Dashboard.

This step will migrate your beta keys into your RANDOM.ORG account, such that you can manage them via our new API Dashboard. Migrating a beta key will not change your key or its daily limits, and it will not cause any interruption in service.

The API Dashboard looks like the following:

API Dashboard

To migrate a beta key such that it appears in the API Dashboard, please do the following:

  1. Make sure you have a RANDOM.ORG account to hold your API key. If your beta key was created before 1 March 2019, we asked for your email address to send you the key, but we did not automatically create a RANDOM.ORG account to hold the key for you at that time. However, you may have created a RANDOM.ORG account separately (by following our regular signup process), and if you do, you can now use that account to hold your API keys. If you don't have a RANDOM.ORG account, it is easy to create one.
  2. Login to your RANDOM.ORG account, newly created or otherwise.
  3. Open your API Dashboard and click on the button labeled ‘Migrate an Existing API Key.’
  4. You will now see the following form: Beta Key Migration Form
  5. Enter your API key into the API key migration form and submit the form.
  6. You will receive an email to the email address you used when you registered your beta key. Please click on the confirmation link in that email.
  7. Your beta key will now appear in your API Dashboard.

Please note that your RANDOM.ORG account can hold a maximum of ten API keys at this time. If you need more, please send us an email.

Step 2: Upgrade your Client to API Release 2 (Optional)

While production keys will work with Release 1 of the API, we recommend that you upgrade your clients to use Release 2 or later.

If you are still using Release 1, you can switch to Release 4 by changing the URL endpoint in your client from the following:

To the following:

For the vast majority of clients, no further changes should be required.

For full details about the differences between the two releases, please see the Release 2 API documentation.

Step 3: Converting to a Production Key

The final step is to convert your key to a production key. To do this, you first need to decide which license is right for you. You will find the list of licenses on our Pricing Page.

Once you have decided on a license, open your your API Dashboard and click on the beta key you wish to convert. In the resulting view, you will see a button labeled ‘Convert to Production Key.’

Convert Button

Clicking on the button will open the conversion modal, which you see below.

Conversion Modal

To proceed, select the desired license from the dropdown menu, then check each box after you have made sure you understand what it means. Finally, submit the form to complete the conversion of your key.

Conversion Complete

Once your key has been converted, you can return to the API Dashboard to confirm that everything looks as expected.

Please don't hesitate to get in touch, if you have questions about the conversion process.