Manage API keys

API keys are the authentication and authorization method for API calls toward published workflows: any program that uses a published workflow via its API must include the value of a valid API key associated with the workflow in each request.
The exception to this rule is interactive testing of a published workflow from inside the EI-Flow designer Web application, which can be done whether or not the workflow has API keys associated with it because the Web application uses a different authorization method.

API keys can be public or project-based.
Public API keys are visible to everyone, while project API keys are visible only to the project owner and any users with whom the project has been shared.
The ability to manage public API keys depends on the user's role, while project API keys, aside from the project owner who has full powers on them, depend on the permissions with which the project was shared.
The main page for viewing and managing public API keys is API keys, while project API keys are viewed and managed in the Assets tab of the project workspace.

The following articles describe all the procedures for managing API keys.