Alchemy API

Enterprise Grade API for Ethereum

Jumpstart your Ethereum development with Alchemy!
Instead of running your own nodes and building your own architecture,
just plug into our API and get back to focusing on developing
your application.

Get Started

Using WebSockets

All Alchemy APIs are accessible via WebSocket as well as POST requests, and using a WebSocket to make your requests also gives you access to new APIs for subscribing to events.

Try It Out

The easiest way to test our APIs with WebSockets is to install a command line tool for making WebSocket requests such as wscat. Using wscat, you can send requests as follows:

$ wscat -c wss://

> {"jsonrpc": "2.0", "id": 0, "method": "eth_gasPrice"}
< {"jsonrpc": "2.0", "result": "0xb2d05e00", "id": 0}

Usage Details

To begin, open a WebSocket using the WebSocket URL for your app. You can find your app's WebSocket URL by opening the app's page in your dashboard and clicking "View Key". Note that your app's URL for WebSockets is different from its URL for HTTP requests, but both can be found by clicking "View Key".

Any of the APIs listed in the Alchemy API Reference or Enhanced API can also be used via WebSocket. To do so, use the same payload that would be sent as the body of a POST request, but instead send that payload through the WebSocket.

With Web3

Transitioning to WebSockets while using a client library like Web3 is simple. Simply pass the WebSocket URL instead of the HTTP one when instantiating your Web3 client. For example:

const web3 = new Web3("wss://");
web3.eth.getBlockNumber().then(console.log);  // -> 7946893

Subscription API

When connected by a WebSocket, you may use two additional methods: eth_subscribe and eth_unsubscribe. These methods will allow you to listen for particular events and be notified immediately.


Creates a new subscription for specified events.


  1. Subscription type: "newHeads" or "logs"
  2. Optional params

The first argument specifies the type of event for which to listen. The second argument contains additional options which depend on the first argument. The different description types, their options, and their event payloads are described below.


The subscription ID. This ID will be attached to any received events, and can also be used to cancel the subsciption using eth_unsubscribe.

Subscription Events

While the subscription is active, you will receive events which are objects with the following fields:

  • jsonrpc: Always "2.0"
  • method: Always "eth_subscription"
  • params: An object with the following fields:
    • subscription: The subscription ID returned by the eth_subscription call which created this subscription.
    • result: An object whose contents vary depending on the type of subscription.


Cancels an existing subscription so that no further events are sent.


  1. Subscription ID, as previously returned from an eth_subscribe call.


true if a subscription was successfully cancelled, or false if no subscription existed with the given ID.

Subscription types


Emits an event any time a new header is added to the chain, including during a chain reorganization.

When a chain reorganization occurs, this subscription will emit an event containing all new headers for the new chain. In particular, this means that you may see multiple headers emitted with the same height, and when this happens the later header should be taken as the correct one after a reorganization.




> {"jsonrpc": "2.0", "id": 1, "method": "eth_subscribe", "params": ["newHeads"]}
< {"jsonrpc":"2.0","id":2,"result":"0x9ce59a13059e417087c02d3236a0b1cc"}

< {
     "jsonrpc": "2.0",
     "method": "eth_subscription",
     "params": {
       "result": {
         "difficulty": "0x15d9223a23aa",
         "extraData": "0xd983010305844765746887676f312e342e328777696e646f7773",
         "gasLimit": "0x47e7c4",
         "gasUsed": "0x38658",
         "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
         "miner": "0xf8b483dba2c3b7176a3da549ad41a48bb3121069",
         "nonce": "0x084149998194cc5f",
         "number": "0x1348c9",
         "parentHash": "0x7736fab79e05dc611604d22470dadad26f56fe494421b5b333de816ce1f25701",
         "receiptRoot": "0x2fab35823ad00c7bb388595cb46652fe7886e00660a01e867824d3dceb1c8d36",
         "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
         "stateRoot": "0xb3346685172db67de536d8765c43c31009d0eb3bd9c501c9be3229203f15f378",
         "timestamp": "0x56ffeff8",
         "transactionsRoot": "0x0167ffa60e3ebc0b080cdb95f7c0087dd6c0e61413140e39d94d3468d7c9689f"
       "subscription": "0x9ce59a13059e417087c02d3236a0b1cc"


Emits logs which are part of newly added blocks that match specified filter criteria.

When a chain reorganization occurs, logs which are part of blocks on the old chain will be emitted again with the propery removed set to true. Further, logs which are part of the blocks on the new chain are emitted, meaning that it is possible to see logs for the same transaction multiple times in the case of a reorganization.


  1. An object with the following fields:
    • adddress (optional): either a string representing an address or an array of such strings. Only logs created from one of these addresses will be emitted.
    • topics: an array of topic specifiers. Each topic specifier is either null, a string representing a topic, or an array of strings. Each position in the array which is not null restricts the emitted logs to only those who have one of the given topics in that position.

Some examples of topic specifications:

  • []: Any topics allowed.
  • [A]: A in first position (and anything after).
  • [null, B]: Anything in first position and B in second position (and anything after).
  • [A, B]: A in first position and B in second position (and anything after).
  • [[A, B], [A, B]]: (A or B) in first position and (A or B) in second position (and anything after).


> {"jsonrpc": "2.0", "id": 1, "method": "eth_subscribe", "params": ["logs", {"address": "0x8320fe7702b96808f7bbc0d4a888ed1468216cfd", "topics": ["0xd78a0cb8bb633d06981248b816e7bd33c2a35a6089241d099fa519e361cab902"]}]}
< {"jsonrpc":"2.0","id":2,"result":"0x4a8a4c0517381924f9838102c5a4dcb7"}

< {
    "jsonrpc": "2.0",
    "method": "eth_subscription",
    "params": {
      "subscription": "0x4a8a4c0517381924f9838102c5a4dcb7",
      "result": {
        "address": "0x8320fe7702b96808f7bbc0d4a888ed1468216cfd",
        "blockHash": "0x61cdb2a09ab99abf791d474f20c2ea89bf8de2923a2d42bb49944c8c993cbf04",
        "blockNumber": "0x29e87",
        "data": "0x00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000003",
        "transactionHash": "0xe044554a0a55067caafd07f8020ab9f2af60bdfe337e395ecd84b4877a3d1ab4",
        "transactionIndex": "0x0"

Updated 8 months ago

Using WebSockets

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.