Authentication is performed using an API key, which is able to be generated admins of each organization.
Every request requires the API key in the form of a Authorization Bearer token header:
"Authorization: Bearer <ORGANIZATION_API_KEY>"
For example, a cURL request would appear as the following:
curl -H "Authorization: Bearer <ORGANIZATION_API_KEY>"
https://api.blood.dev/devices/dashboard/<DEVICE_TYPE>/<SERIAL_NUMBER>
Note that API Keys are only available for customers which have a valid 
Generating API keys:
User accounts who have API Access (Organization Admins) are able to see a button on the left side of the settings page for API Access. Clicking on that button will open a page, which will show all current API tokens and allow generation of new ones.
To generate a new key:
- Determine if you wish to generate a Sandbox key or a normal key. Read more about Sandbox Mode below.
- For sandbox keys, login to https://sandbox.blood.dev
- Navigate to the API Access settings page
- Select an expiration date (if any)
- Enter a key alias / nickname to assist with identificaiton of it in the future.
- Click "Generate API Key"
- A new API key is generated and ready to use!
Enterprise Software Partners 
Software providers are able to partner with Delta Development Team in order to provide combined services, offer BloodCOMM data (Temperature, alerts, etc) within their software application.
Software partners will be able to integrate BloodCOMM data into their application and allow Delta Development hardware to work seamlessly with their platforms. API requests are able to be submitted on behalf of a customer's account, without the purchase of an Enterprise license.
Note that customers who purchase your software will still need to purchase a BloodCOMM
or
subscription. API requests for cloud devices with invalid licenses will be rejected.
Additionally, each new customer account will need to be authorized to your application by Delta Development Team, to ensure data security and privacy. Submit requests for authorization through your partnership manager.
Contact Delta Development Team Support if you are interested in becoming an Enterprise Software Partner.
Sandbox Mode 
Application Developers are able to utilize a special developer mode, allows for certain features to be enabled and/or bypassed for testing purposes.
Application developers should use this mode to test their applications, as it will not affect licensing, billing, or the production BloodCOMM website/app.
This mode is available for both regular API access and Software Partners, but may need to be activated separately. Contact support if you are unable to request a developer key.
The BloodCOMM Sandbox is available at https://sandbox.blood.dev/. Login with the same credentials used for the production site, and request a sandbox key using the same method of requesting a key normally.
This key is valid for use querying data available within the Sandbox, and will reflect only data within the BloodCOMM Sandbox.
Note that the Sandbox is completely detached from the Production server, meaning that you accounts, settings, devices, etc. will not exist on the sandbox server. Contact support to have a sandbox organization setup with demo devices and licenses.