API Communication
Overview
The API communication between the customer backend and the Fireblocks platform takes place over HTTP (REST). The authentication mechanism is done by creating an API user and signing a JWT token for each request made by the customer.
Not familiar with the API user creation and authentication?
Visit the links below to understand how each process works:
API roles
The Fireblocks NCW feature comes with two new API roles: NCW Admin and NCW Signer.
NCW Admin
This role is used for general workspace operations, such as creating a new NCW.
![](https://files.readme.io/4f21de9-NCW_ADMIN.png)
NCW Signer
This role is used for specific wallet operations, such as creating a transaction from a specific NCW.
![](https://files.readme.io/b58c3e9-NCW_SIGNER.png)
Permissions
The table below lists the different operations that can be executed by the NCW Admin & NCW Signer API users.
![](https://files.readme.io/5b77afa-API_Communication_-_Table.png)
Updated 11 months ago