| Access Key | An access key is a token that a customer provides for API calls. |
| Access Token | An access token receives all security data for the authentication of an API and identifies the user, the user groups and the user's authorizations. |
| Activation Request | An activation request is made by the customer when they request the use of an API from the provider. It is designed to ensure smooth and efficient access to our services. |
| Providers | Providers are all organizations that provide API products on the Developer Portal. |
| API | An application programming interface, often referred to as an API for short, is a program part that is made available by a software system to other programs for connection to the system. |
| API Products | This term is used when several APIs are involved (see API above). |
| App | An App describes a collection of API products that are brought together by the customer in an application. By registering API products to an App, the customer can use the services offered by these API products using the stored authentication means. By using Apps, customers can bundle their access to multiple API products, manage the authentication means and establish a contractual relationship with the provider. |
| Authentication Method | Describes the procedure required to use an API in order to exchange the information required for the authentication of an API between provider and customer. For this purpose, the Developer Portal supports authentication methods that were stored when an API was created. |
| Authentication Means | A concrete authentication means of the customer. The customer owns and controls it and it is used to authenticate the customer's identity (e.g. access token). |
| Authorizations | The authorizations of a user to use API products. |
| Business Case | Specification of value creation, use case and traffic when describing a customer's App in order to provide the provider with a rough concept of the application. |
| File | Digital document for the customer's information that a provider can store in its API for the customer (e.g. API explorer, readme). |
| Documentation | Sum of the files stored at an API. |
| Approval | A approval can be carried out by the provider after an activation request. The approval guarantees use of an API by the customer. |
| Hash-process | Hashing is a cryptographic method that converts data records and characters of any length into compact, fixed hash values. |
| Contact Person | Customer of API products must store a contact person in the Developer Portal in order to provide the provider with a direct contact person. |
| Customers | Customers are all organizations that use API products from the Developer Portal. |
| Manual Handover | Authentication method that can be used if no handover method of the authenticator has been stored in the API. This means that the exchange of authentication information is regulated individually between provider and customer. |
| Marketplace | The Marketplace is a main page in the Developer Portal where you can find all of our providers' API products. |
| Users | Users are all persons or systems (technical users) who have an account in the Developer Portal. |
| Folder | A grouped collection of files in the documentation of an API. |
| Organization | A company that is represented on the Developer Portal and offers or uses API products. |
| Organization Data | All information that organizations must provide about themselves in the Developer Portal. |
| Plan | The plan describes the extent to which an API can be used when connecting Apps and API products. |
| Readme | A file that describes how an API can be used. |
| Refresh Token | A refresh token makes it possible to obtain a new access token without prompting the user. |
| Team | Teams represent user groups of the provider or customer. Teams are used to grant or restrict access to certain resources. |
| Technical User | User who accesses functions via the Developer Portal API. A technical user is assigned to an organization and is not directly linked to a natural user. |