JAPER Bearer Token

JAPER utilizes a multi-layered bearer token security approach to ensure a high level of security and privacy for its users. The three main components of this security system are the API Key, Application ID, and Device ID.

1. API Key: The API Key is a secret 40-character key provided by Japer Technology Pty. Ltd. under an agreement. It is required for accessing the JAPER API, except for the /ping endpoint. The API Key is used to authenticate the application making the request and ensure that it has the necessary permissions to access the API. This helps prevent unauthorized access and misuse of the API.
2. Application ID: The Application ID is a secret 44-character identifier that is also provided by Japer Technology Pty. Ltd. under an agreement. It is required for accessing the JAPER API, except for the /ping and /device/create endpoints. The Application ID is used to identify the specific application making the request, allowing JAPER to track and manage access to its API on a per-application basis. This further enhances the security of the system by allowing for granular control over API access.
3. Device ID: The Device ID is generated when a JAPER App is installed and calls the JAPER API to create a new device. The API returns a new Device ID and status 201 if the Device ID is created successfully. The Device ID is used to identify a specific instance of the JAPER App on a user's device. This allows JAPER to manage and control access to its API on a per-device basis, ensuring that each device has the appropriate level of access and preventing unauthorized use of the system.

Together, the API Key, Application ID, and Device ID form a robust and secure bearer token system that ensures the privacy and security of JAPER's users and their data. By requiring these tokens for API access, JAPER can effectively manage and control access to its services, prevent unauthorized access, and maintain a high level of security for its users.