Authentication & Authorization

Understand how to securely authenticate with the MeetBit Public API

MeetBit uses Clients as the basis for communicating with the Public API. Multiple Access Keys can be issued under each Client and are used to identify the originator of requests.

Authentication

To use an Access Key, attach both the access key ID and secret as headers of each request.

POST /users
X-Access-Key-Id: MBP-#Udh23 ...
X-Access-Key-Secret: pc#KLf*rD8jeb ...

{}

X-Access-Key-Id

string

required

Access Key ID

X-Access-Key-Secret

string

required

Access Key Secret

If your access key is invalid, you will receive a 401 Unauthorized error with the following response:

401 Unauthorized
Content-Type: text/plain
Invalid or missing access key.

Authorization

Each API endpoint requires a different permission. Access Key’s adopt the permissions of its Client’s role and permissions are configured through the MeetBit Admin Panel.

If your Access Key’s Client does not have the correct permissions, you will receive a 401 Unauthorized error with the following response:

401 Unauthorized
Content-Type: text/plain
Access Denied.