Creating access keys for the Asta Vision API

You use the API Keys page to create and delete API access keys, which enable users to access the Asta Vision API and to construct requests with the access rights of a specific Asta Vision user. The API access keys are displayed in a list, with the list displaying the user that has been specified for each key and the expiry date of each key. You can filter and sort the API access keys in the list and change the width of columns in the list.

To access the API Keys page from the Asta Vision Home page, click Admin then click API Keys.

You need to supply an API access key as a header when constructing requests in an external application that accesses data using the Asta Vision API. For each API access key, you specify a user - so you should create one API access key for each Asta Vision user that will access the API. The specified user's Asta Vision access rights apply to all API calls that are made using the key, and any new programme versions that are created by an API call are recorded as having been created by that user.

For example:

  • If you supply an API access key that specifies an Asta Vision user with full access rights over all data - an administrator user - as a header in an API request that GETs information on Asta Vision projects, information on all projects will be returned.
  • If you supply an API access key that specifies an Asta Vision user with full access rights over some, but not all, projects as a header in an API request that GETs information on Asta Vision projects, only information on the projects to which the user has access will be returned.
  • If you supply an API access key that specifies an Asta Vision user with read-only access rights over projects as a header in an API request that POSTs information to Asta Vision projects, the request will fail, as the user has insufficient access rights to POST.

Related Topics:

Introduction to the Asta Vision API

Working with users

Configuring security rules