Developing the APIs
Protocol APIs
Following are the APIs to be developed by BAP and BPP:
BAP
BAP should consume the following on_action APIs and trigger action APIs.
on_search API
on_select API
on_init API
on_confirm
on_status
on_update
on_rating
on_support
BPP
BPP should consume the following action APIs and trigger on_action APIs.
search API
select API
init API
confirm
status
update
rating
support
Steps to create a Request:
All the action and on_action APIs have
context
andmessage
objects. Refer to this link to understand the list of properties in the context object. Message object varies based on the API, refer Reference Implementation Guides for examples. Below is the sample API request with context and message objects.
Participant should sign the payload and send to gateway. Steps to sign the request payload and verify when a payload received.
Error codes implementation by BAP and BPP.
Only search API goes through gateway, rest all APIs are between BAP and BPP. Example: BAP sends search API to gateway, and it will broadcast to all available providers in that domain. Next, BPP will make on_search API directly to BAP.
Note:
Protocol Server is a reference application, which helps the participants to quickly develop the protocol APIs. It will help in signing and verification of payload signature, schema validation, sending and receiving requests to Gateway and Participants.
It is not mandatory to use the protocol server; you can build your own network adaptors to connect to the ONEST network.
Sample code for implementing signature and verification.
Registry Lookup API
The registry lookup API can be used to get the details of all the participants in the registry. In request body, type
can be BG
,BAP
, BPP
Gateway URL
Last updated