Get message data
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 the notification. You can find the notification ID in the response to the original notification method call.
740e5834-3a29-46b4-9a6f-16142fde533aSuccess
The Send Email Response Payload
Required - notification ID
740e5834-3a29-46b4-9a6f-16142fde533aOptional
STRINGRequired for text messages
+447900900123Required for letter
ADDRESS LINE 1Required for letter
ADDRESS LINE 2Required for letter
ADDRESS LINE 3Required for letter
ADDRESS LINE 4Required for letter
ADDRESS LINE 5Required for letter
ADDRESS LINE 6Required for letter
NW1 2TZRequired for letter
first / second / economy / europe / rest-of-worldPossible values: Required
sms / letter / emailPossible values: Required
sending / delivered / permanent-failure / temporary-failure / technical-failureRequired - body of notification
STRINGRequired for email- subject of email
STRINGRequired - date and time notification created
2024-05-17T15:58:38.342838ZOptional - name of the person who sent the notification if sent manually
STRINGOptional - date and time notification sent to provider
2024-05-17T15:58:30.143000ZOptional - date and time notification delivered or failed
2024-05-17T15:59:10.321000ZOptional - date and time notification has been scheduled to be sent at
2024-05-17T09:00:00.000000ZOptional - URL that you provided so your recipients can unsubscribe
STRINGtrue if cost data is ready, and false if it isn't
trueOptional - cost of the notification in pounds. The cost does not take free allowance into account
0.0027Bad 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.
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"
You can filter by email, sms or letter
You can filter by message status.
{"summary":"Emails Status","description":"| Status | Description |\n| --- | --- |\n| `created` | NotifyNL has placed the message in a queue, ready to be sent to the provider. It should only remain in this state for a few seconds. |\n| `sending` | NotifyNL has sent the message to the provider. The provider will try to deliver the message to the recipient for up to 72 hours. NotifyNL is waiting for delivery information. |\n| `delivered` | The message was successfully delivered. |\n| `permanent-failure` | The provider could not deliver the message because the email address was wrong. You should remove these email addresses from your database. |\n| `temporary-failure` | The provider could not deliver the message. This can happen when the recipient’s inbox is full or their anti-spam filter rejects your email. [Check your content does not look like spam](https://www.gov.uk/service-manual/design/sending-emails-and-text-messages#protect-your-users-from-spam-and-phishing) before you try to send the message again. |\n| `technical-failure` | Your message was not sent because there was a problem between Notify and the provider. <br>You’ll have to try sending your messages again. |\n"}Possible values: An identifier you can create if necessary. This reference identifies a single notification or a batch of notifications. It must not contain any personal information such as name or postal address.
STRINGInput the ID of a notification into this argument. If you use this argument, the method returns the next 250 received notifications older than the given ID.If you leave out this argument, the method returns the most recent 250 notifications.The client only returns notifications that are 7 days old or newer. If the notification specified in this argument is older than 7 days, the client returns an empty response.
740e5834-3a29-46b4-9a6f-16142fde533aIncludes notifications sent as part of a batch upload.If you leave out this argument, the method only returns notifications sent using the API.
trueSuccess
The Send Text Message Response Payload
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.
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 the notification. You can find the notification ID in the response to the original notification method call. You can also find it by signing in to NotifyNL and going to the API integration page.
740e5834-3a29-46b4-9a6f-16142fde533aIf the request to the client is successful, the client will return bytes representing the raw PDF data.
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