Instead of using a seat (email / password), we would like to have an API key mechanism for authentication. This can be shared with the integration engineers and is not tied to an individual user.
It is unlikely that we will provide "API users" that do not correspond to an actual user in Aha!. We need the user record so that permissions can be applied to access through the API.
However, if it desire is to have an "API key" that can be used instead of the email/password combination in order to access the API then that is possible today with a bit of work:
Although this is not documented or supported directly in the UI it is safe to use since it is using the underlying OAuth infrastructure that is used for many integrations. In the future we plan to add a UI to make these steps easier.
Thanks for the info, Chris!
You won't be notified about changes to this idea.