Endpoint
Airnode serves an API to a blockchain according to Oracle Integration Specifications (OIS). An API is composed of operations, which represent individual functionalities that an API offers. OIS maps each API operation to an endpoint, which can be thought of as an Airnode operation. The endpoints that an Airnode will serve over the request–response protocol are listed under triggers of config.json.
endpointId
endpointId
identifies a specific endpoint that an Airnode serves. Its derivation, shown below, is enforced by airnode-validator
.
ethers.utils.keccak256(
ethers.utils.defaultAbiCoder.encode(
['string', 'string'],
[oisTitle, endpointName]
)
);
2
3
4
5
6
An alternative method to create an endpointId
is to use the Admin CLI to derive the endpoint ID.
Note that this means that an endpointId
is not unique, and two Airnodes can serve equivalent endpoints using the same ID (in fact, this is the desired outcome). This is not an issue, as requests are made with a airnode
(Airnode's address
) and endpointId
pair.
Authorizers
Airnodes can assign a list of authorizers for each chain it responds to. See Authorizers for more information.
FLEX_END_TAG