Authentication & Headers

Authentication

While the majority of our platform authenticates via the x-api-key header, RPC endpoints are different in that they require a path param of x-api-key instead.

Example:

https://rpc.web3api.io/api/v2?x-api-key=YOUR-API-KEY

If an api key is not provided the request will fail.

Note about writes:

While writes are supported they are restricted to already signed transactions only. This is due to the fact that we do not store or manage private keys.