As previously announced, accessing Infura will begin requiring a Project ID generated from the new Infura Dashboard. If you are using Infura and have not yet migrated your project, please take the time to do so now. The first milestone in this transition will be activated next week on January 23, 2019 at 20:00 UTC.

More information on how to send requests using a Project ID can be found in our docs. As a reminder, here is the timeline:

January 23, 2019, 20:00 UTC

Requests using Dashboard-generated Project IDs will be prioritized over legacy keys during periods of high traffic activity. Legacy keys may experience slower response times.

March 27, 2019, 20:00 UTC

Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.

What do I need to do?

If you haven’t done so already, create an account at https://infura.io/register. Once you have created your account and logged in to the Dashboard, simply create a new project, and your Project ID (and associated Infura API endpoint URLs) will be generated. Replace the Infura URL in your code with the newly generated URL.

You may also create multiple projects to isolate traffic for multiple dapps/use-cases. Stats can be viewed in aggregate or on a per-project basis.

If you maintain a library that leverages Infura, please reach out directly to us if there is anything we can do to help you with this transition.

How do I know I am using the correct API endpoint URL?

Prior to July 2018, your Infura API endpoint would have looked like this:

https://mainnet.infura.io/[YOUR_KEY]

The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:

https://mainnet.infura.io/v3/[PROJECT_ID]

If you have any questions please post them at community.infura.io or email us at support@infura.io.