Documentation

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

API keys

An API key is typically used in conjunction with one of Hornbill’s pre-built or customer-built integrations and import tools, to enable machine-to-machine authentication where initial integration during setup is required, as well as to remove the need to specify plain text credentials in configuration files that will be located on computers at the point of integration.

Creating an API Key

Click on the + button to start creating a new API key.

  • User Account
    The user account under which this API will run under. The API will inherit the rights of the selected user. The API Key can be restricted further by using rules.
  • Description
    This is a simple description of the API key that is being created
  • State
    This defines the current state of the API key. The options are Active, Revoked or Suspended. Any API key that is not in Active state cannot be used.
  • Expires
    This defines the date and time until the API key is active. Once the expiry date is reached the API key can no longer be used. This is mandatory, following best security practices.

Rules

This is a list of Hornbill APIs (https://api.hornbill.com/) that can be used by the API key. You can restrict the use of an API key here by specifying only certain APIs that can be used by the API key.

If no rules are specified, then any API that the API key’s associated user account has rights to call, can be called. If one or more rules are defined, only API’s that match these rules will be allowed.

Each rule is a simple string that can include DOS-style wildcards. Rules are evaluated until a match is found, if no match is found the API call is rejected. Click on the ? to get a list of example rules.

Each rule needs to be in the following format: :<api_name>. Replace and <api_name> with relevant values. Click on the “Create” button to finish creating the new API key.

Tip

API Keys can also be viewed or managed from a user account. Each user account will show any API Key that that have been created under the context of that account.

In This Document