Key generation and deletion are associated with the acquirer role.
For data offerings completed by importing an OpenAPI specification, API multi-keys enable purchasers to consume the acquired data, while reinforcing the security of data access.
Generation of multiple API keys in acquisition
One key is required per transaction and per acquirer, and can be generated for each person or entity that will need to consume the API. The data acquirer can name his API keys.
The acquirer is invited to copy and save the API keys generated, as they will no longer be displayed. A message is displayed in the participant portal to indicate this.
Deletion of multiple API keys in the acquisition
A key can be deleted at any time to enhance security. To do so, the data acquirer has to go to the relevant acquisition and delete the desired key.
Download API specifications
There are two ways to download API specifications in OpenAPI format:
OpenApi via a cloud connector: a cloud connector must be associated with the acquisition in question. The data acquirers must select the OpenAPI OAS specification standard to be transferred to the cloud connector. They can then send an existing key or generate a new one.
OpenAPI export: the data acquirers can download the API specifications in OpenAPI format (version 2.0 or 3.0).
