The Tokenization API is a REST via HTTPS interface. You can use it to create new projects, new tokens and to distribute tokens to customers. All of its functions are also available via the NYALA Web Portal, however if you create projects that have ongoing token distributions, we recommended you to integrate with the distribute tokens endpoint at least, as it is less manual and error-prone.
ℹ️ Again, all the operations contained in the Tokenization API can also be done through the NYALA Web Portal interface. Contact your Technical Sales Engineer (TSE) to request for access and to receive a user manual for the portal.
In our data model, the top-level entity is a Project. Each Project can contain one or more tokens. An example could be of a company that is simultaneously issuing two bonds with different terms (durations, interest rates, etc.). Thus, you must create a project before you can request the creation of a token.
The following steps detailed in this chapter’s sub-pages must be followed in order.
IMAGE
Skipping a step of the process will likely result in an error.
This API uses HMAC (Hash-based Message Authentication Code) for security. Every request must include an Authorization header containing a signature generated using your Secret Key.
| Header | Value |
|---|---|
Authorization | X-API-KEY |
The signature is a Base64 encoded HMAC-SHA256 hash. The "message" to be signed is constructed by concatenating the following strings in order:
- Content Length: The length of the request body (or "0" if empty).
- HTTP Method: (e.g.,
GET,POST,PATCH). - Normalized URL: The full URL, converted to lowercase, with the
?removed.