Get received text messages
The authorisation header is an API key that is encoded using JSON Web Tokens. You must include an authorisation header.
JSON Web Tokens have a standard header and a payload. The header consists of:
{
"type":"JWT",
"alg":"HS256"
}
The payload consists of:
{
"iss": "26785a09-ab16-4eb0-8407-a37497a57506",
"iat": 1568818578
}
JSON Web Tokens are encoded using a secret key with the following format: 3d844edf-8d35-48ac-975b-e847b4f122b0
That secret key forms a part of your API key, which follows the format
{key_name}-{iss-uuid}-{secret-key-uuid}.
For example, if your API key is
my_test_key-26785a09-ab16-4eb0-8407-a37497a57506-3d844edf-8d35-48ac-975b-e847b4f122b0:
- your API key name is
my_test_key - your iss (your service id) is
26785a09-ab16-4eb0-8407-a37497a57506 - your secret key is
3d844edf-8d35-48ac-975b-e847b4f122b0
iat (issued at) is the current time in UTC in epoch seconds. The token expires within 30 seconds of the current time.
Refer to the JSON Web Tokens website for more information on encoding your authorisation header.
When you have an encoded and signed token, add that token to a header as follows:
"Authorization": "Bearer encoded_jwt_token"
The ID of a received text message. If this is passed, the response will only list text messages received before that message.
Success
Recieved text messages
Bad request. Check the message in the response to find out why your request failed.
Auth error. Check the message in the response to find out why your request failed.
Result not found. Check the message in the response to find out why your request failed.
Last updated