# Glossary

## ApiKey

When you call the RelationONE Api, you need to add `ApiKey` in the http Header.

The ApiKey is used to authenticate the application making the request.

The following ApiKey sample is for testing purposes only(NOT for the production environment): 581c6c4fa0b54912b00088aa563342a4.

If you need to use an ApiKey for production, please refer to this form:

{% embed url="<https://docs.google.com/forms/d/1B38ferfackqnLuPUlWr5Pc2bvrK8C1M3TI5wwiw4Kxo>" %}

## Rate Limits

The request frequency

## addressAuthToken

Some Api need to add the `I-Authorization: ${addressAuthToken}` in the http header to identify the user identity.

You can get it from the following Api:

{% content-ref url="../api/signature" %}
[signature](https://relationlabs.gitbook.io/relation-one-api/api/signature)
{% endcontent-ref %}

## unifiedAuthToken

Some Api need to add the `Authorization: ${unifiedAuthToken}` in the http header to identify the user identity.

You can get it from the following API:

{% content-ref url="../api/auth" %}
[auth](https://relationlabs.gitbook.io/relation-one-api/api/auth)
{% endcontent-ref %}
