Response Format
The MeetBit Public API wraps resource objects returned in responses in a base response format.A short response message
The resource object/s returned
Response Codes
We follow RFC 9110 in using HTTP status codes to indicate success or failure of your requests. In general, 2xx HTTP codes correspond to success, 4xx codes are for client-side errors, and 5xx codes are for server-side issues.Status Code | Description |
---|---|
200 | Successful request. |
202 | Successful request without content in response. |
400 | Invalid input parameters. |
401 | Invalid access key or permissions. |
404 | Resource not found. |
429 | Rate limit exceeded. |
500 | Server error. |
Common Errors
Validation Error
This error is returned when the request parameter/s are invalid or malformed.A short response message
errors
object with keys that correspond to input fields. Each key’s value is an array of strings describing the errors encountered in validating that field.
Resource Object Not Found
This error is returned when the specified resource object is not found.Unauthenticated Error
This error is returned when the request has invalid or is missing access keys.Unauthorized Error
This error is returned when the Client does not have the necessary permissions to perform the action.Rate Limited Error
This error is returned when the rate limit has been exceeded.Number of seconds to wait before making another request.