PHP client documentation
This documentation is for developers interested in using the GOV.UK Notify PHP client to send emails, text messages or letters.
Set up the client
The Notify PHP Client is based on a PSR-7 HTTP model. To install it, you must select your preferred PSR-7 compatible HTTP client. You can follow these instructions to use Guzzle v7.
Guzzle v7
Use Composer to install the GOV.UK Notify PHP client. Run the following in the command line:
composer require php-http/guzzle7-adapter alphagov/notifications-php-clientYou can now use the autoloader to download the GOV.UK Notify PHP client.
Add the following code to your application to create a new instance of the client:
$notifyClient = new \Alphagov\Notifications\Client([ 'apiKey' => '{your api key}', 'baseUrl' => 'https://api.notifynl.nl', 'httpClient' => new \Http\Adapter\Guzzle7\Client ]);
To get an API key, sign in to NotifyNL and go to the API integration page. You can find more information in the API keys section of this documentation.
Send a message
You can use NotifyNL to send emails, text messages and letters.
Bulk sending
You cannot use a single API call to send messages in bulk.
To send a batch of messages, use the API to loop over your recipient list, sending one message at a time to each recipient.
Make sure you do not exceed our rate limits.
Send a text message
Method
For example:
Arguments
phoneNumber (required)
The phone number of the recipient of the text message. This can be a UK or international number.
templateId (required)
To find the template ID:
Go to the Templates page and select the relevant template.
Select Copy template ID to clipboard.
personalisation (optional)
If a template has placeholder fields for personalised information such as name or application date, you must provide their values in a dictionary with key value pairs. For example:
You can leave out this argument if a template does not have any placeholder fields for personalised information.
reference (optional)
A unique identifier you can create if necessary. This reference identifies a single unique notification or a batch of notifications. It must not contain any personal information such as name or postal address. For example:
You can leave out this argument if you do not have a reference.
smsSenderId (optional)
A unique identifier of the sender of the text message notification.
To find the text message sender:
Go to the Settings page.
In the Text Messages section, select Manage on the Text Message sender row.
You can then either:
copy the sender ID that you want to use and paste it into the method
select Change to change the default sender that the service will use, and select Save
You can leave out this argument if your service only has one text message sender, or if you want to use the default sender.
Response
If the request to the client is successful, the client returns an array:
If you are using the test API key, all your messages will come back with a delivered status.
All messages sent using the team and guest list or live keys will appear on your dashboard.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
phone_number Too many digits
Provide a valid recipient phone number.
phone_number Not enough digits
Provide a valid recipient phone number.
phone_number Not a NL mobile number
Provide a valid Dutch recipient phone number.
phone_number Must not contain letters or symbols
Provide a valid recipient phone number.
phone_number Not a valid country prefix
Provide a valid recipient phone number.
BadRequestError (status code 400)
sms_sender_id <sms_sender_id> does not exist in database for service id
Go to your service Settings and copy a valid sms_sender_id. Check that the API key you are using and the sms_sender_id belong to the same service.
Cannot send to this recipient when service is in trial mode - see https://admin.notifynl.nl/trial-mode
Your service cannot send this text message in trial mode. To fix, you need to request for your service to go live.
Cannot send to international mobile numbers
Sending to international mobile numbers is turned off for your service. You can change this in your service Settings.
Send an email
Method
For example:
Arguments
emailAddress (required)
The email address of the recipient.
templateId (required)
To find the template ID:
Go to the Templates page and select the relevant template.
Select Copy template ID to clipboard.
personalisation (optional)
If a template has placeholder fields for personalised information such as name or reference number, you need to provide their values in a dictionary with key value pairs. For example:
You can leave out this argument if a template does not have any placeholder fields for personalised information.
Find out how to reduce the risk of malicious content injection in placeholders.
reference (optional)
A unique identifier you can create if necessary. This reference identifies a single unique notification or a batch of notifications. It must not contain any personal information such as name or postal address.
You can leave out this argument if you do not have a reference.
one_click_unsubscribe_url (recommended)
If you send subscription emails you must let recipients opt out of receiving themThe one-click. Read our Using Notify page for more information about unsubscribe links.
The one-click unsubscribe URL will be added to the headers of your email. Email clients will use it to add an unsubscribe button.
The one-click unsubscribe URL must respond to an empty POST request by unsubscribing the user from your emails. You can include query parameters to help you identify the user.
Your unsubscribe URL and response must comply with the guidance specified in Section 3.1 of IETF RFC 8058.
You must also add an unsubscribe link to the bottom of your email. The unsubscribe link at the bottom of your email should take the email recipient to a webpage where they can confirm that they want to unsubscribe.
Find out how to add a link when you create a New template or Edit an email template.
emailReplyToId (optional)
This is an email address specified by you to receive replies from your users. You must add at least one reply-to email address before your service can go live.
To add a reply-to email address:
Go to the Settings page.
In the Email section, select Manage on the Reply-to email addresses row.
Select Add reply-to address.
Enter the email address you want to use, and select Add.
For example:
You can leave out this argument if your service only has one email reply-to address, or you want to use the default email address.
Response
If the request to the client is successful, the client returns an array:
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
email_address Not a valid email address
Provide a valid recipient email address.
one_click_unsubscribe_url is not a valid https url
Provide a valid https url for your unsubscribe link.
BadRequestError (status code 400)
email_reply_to_id <reply to id> does not exist in database for service id <service id>
Go to your service Settings and copy a valid email_reply_to_id. Double check that the API key you are using and the email_reply_to_id belong to the same service.
Emails cannot be longer than 2000000 bytes. Your message is <rendered template size in bytes> bytes.
Shorten your email message.
Cannot send to this recipient when service is in trial mode - see https://admin.notifynl.nl/trial-mode
Your service cannot send this email in trial mode. To fix, you need to request for your service to go live.
Reducing the risk of malicious content injection in placeholders
NotifyNL lets you personalise messages using placeholders.
You can format content or add links and urls into placeholders using Markdown.
If you pass in information from untrusted sources (such as online forms) into your Notify template using personalisation, this may be used to add malicious content and links to notifications you send via Notify.
The malicious content could be:
Markdown syntax intended to be rendered into HTML
a plain text URL which would be rendered into a clickable phishing link
An example of how malicious content can be injected into NotifyNL personalisation:
Template in NotifyNL:
Personalisation:
Email will appear as:
We recommend you sanitise all input from untrusted sources to prevent the injection of malicious content. You can use a backslash to escape individual characters. The characters of most concern are those that could be used to add a URL link such as [, ], ( or ).
Send a file by email
To send a file by email, add a placeholder to the template then upload a file. The placeholder will contain a secure link to download the file.
The links are unique and unguessable. NotifyNL cannot access or decrypt your file.
Your file will be available to download for a default period of 26 weeks (6 months).
To help protect your files you can also:
ask recipients to confirm their email address before downloading
choose the length of time that a file is available to download
Add contact details to the file download page
Go to the Settings page.
In the Email section, select Manage on the Send files by email row.
Enter the contact details you want to use, and select Save.
Add a placeholder to the template
Go to the Templates page and select the relevant email template.
Select Edit.
Add a placeholder to the email template using double brackets. For example: “Download your file at: ((link_to_file))”
Your email should also tell recipients how long the file will be available to download.
Upload your file
You can upload the following file types:
CSV (.csv)
image (.jpeg, .jpg, .png)
Microsoft Excel Spreadsheet (.xlsx)
Microsoft Word Document (.doc, .docx)
PDF (.pdf)
text (.json, .odt, .rtf, .txt)
Your file must be smaller than 2MB.. Contact the NotifyNL team if you need to send other file types.
Pass the file object as a value into the personalisation argument. For example:
Set the filename
To do this you will need version 6.0.0 of the PHP client library, or a more recent version.
You should provide a filename when you upload your file.
The filename should tell the recipient what the file contains. A memorable filename can help the recipient to find the file again later.
The filename must end with a file extension. For example, .csv for a CSV file. If you include the wrong file extension, recipients may not be able to open your file.
If you do not provide a filename for your file, NotifyNL will:
generate a random filename
try to add the correct file extension
If NotifyNL cannot add the correct file extension, recipients may not be able to open your file.
Ask recipients to confirm their email address before they can download the file
When a recipient clicks the link in the email you’ve sent them, they have to enter their email address. Only someone who knows the recipient’s email address can download the file.
This security feature is turned on by default.
Turn off email address check (not recommended)
If you do not want to use this feature, you can turn it off on a file-by-file basis.
To do this you will need version 4.2.0 of the PHP client library, or a more recent version.
You should not turn this feature off if you send files that contain:
personally identifiable information
commercially sensitive information
information classified as ‘OFFICIAL’ or ‘OFFICIAL-SENSITIVE’ under the Government Security Classifications policy
To let the recipient download the file without confirming their email address, set the confirm_email_before_download flag to false.
Choose the length of time that a file is available to download
Set the number of weeks you want the file to be available using the retentionPeriod key.
To use this feature will need version 4.2.0 of the PHP client library, or a more recent version.
You can choose any value between 1 week and 78 weeks. When deciding this, you should consider:
the need to protect the recipient’s personal information
whether the recipient will need to download the file again later
If you do not choose a value, the file will be available for the default period of 26 weeks (6 months).
Files sent before 12 April 2023 had a longer default period of 78 weeks (18 months).
Response
If the request to the client is successful, the client returns an array:
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
BadRequestError (status code 400)
Unsupported file type '(FILE TYPE)'. Supported types are: '(ALLOWED TYPES)'
Wrong file type. You can only upload .csv, .doc, .docx, .jpeg, .jpg, .odt, .pdf, .png, .rtf, .txt or .xlsx files
filename cannot be longer than 100 characters
Choose a shorter filename
filename must end with a file extension. For example, filename.csv
Include the file extension in your filename
Unsupported value for retention_period '(PERIOD)'. Supported periods are from 1 to 78 weeks.
Choose a period between 1 and 78 weeks
Unsupported value for confirm_email_before_download: '(VALUE)'. Use a boolean true or false value.
Use either True or False
File did not pass the virus scan
The file contains a virus
Send files by email has not been set up - add contact details for your service at https://admin.notifynl.nl/services/(SERVICE ID)/service-settings/send-files-by-email
Can only send a file by email
Make sure you are using an email template
Client error (no status code)
ValueError('File is larger than 2MB')
The file is too big. Files must be smaller than 2MB.
Send a letter
When you add a new service it will start in trial mode. You can only send letters when your service is live.
To send Notify a request to go live:
Go to the Settings page.
In the Your service is in trial mode section, select request to go live.
Method
For example:
Arguments
templateId (required)
To find the template ID:
Go to the Templates page and select the relevant template.
Select Copy template ID to clipboard.
personalisation (required)
The personalisation argument always contains the following parameters for the letter recipient’s address:
address_line_1address_line_2address_line_3address_line_4address_line_5address_line_6address_line_7
The address must have at least 3 lines.
The last line needs to be a real UK postcode or the name of a country outside the UK.
Notify checks for international addresses and will automatically charge you the correct postage.
The postcode personalisation argument has been replaced. If your template still uses postcode, Notify will treat it as the last line of the address.
Any other placeholder fields included in the letter template also count as required parameters. You need to provide their values in a dictionary with key value pairs. For example:
reference (optional)
A unique identifier you can create if necessary. This reference identifies a single unique notification or a batch of notifications. It must not contain any personal information such as name or postal address. For example:
Response
If the request to the client is successful, the client returns an array:
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
personalisation address_line_1 is a required property
Ensure that your template has a field for the first line of the address, check personalisation for more information.
Must be a real NL postcode
Ensure that the value for the last line of the address is a real NL postcode.
Must be a real address
Provide a real recipient address. We do not accept letters for “no fixed abode” addresses, as those cannot be delivered.
Last line of address must be a real NL postcode or another country
Ensure that the value for the last line of the address is a real NL postcode or the name of a country outside the NL.
The last line of a BFPO address must not be a country.
The last line of a BFPO address must not be a country.
Address must be at least 3 lines
Provide at least 3 lines of address.
Address must be no more than 7 lines
Provide no more than 7 lines of address.
Address lines must not start with any of the following characters: @ ( ) = [ ] ” \ / , < >
Change the start of an address line, so it doesn’t start with one of these characters. This is a requirement from our printing provider.
postage invalid. It must be either first, second or economy.
Specify valid postage option.
BadRequestError (status code 400)
Cannot send letters when service is in trial mode - see https://admin.notifynl.nl/trial-mode
Your service cannot send this letter in trial mode.
Service is not allowed to send letters
Turn on sending letters in your service Settings on NotifyNL webpage
letter_contact_id <letter_contact_id> does not exist in database for service id <service id>
Go to your service Settings and copy a valid letter_contact_id. Check that the API key you are using and the letter_contact_id belong to the same service.
BadRequestError (status code 403)
Cannot send letters with a team api key
Use the correct type of API key.
Send a precompiled letter
Method
Arguments
reference (required)
A unique identifier you create if necessary. This reference identifies a single unique notification or a batch of notifications. It must not contain any personal information such as name or postal address.
pdf_data (required)
The precompiled letter must be a PDF file which meets the GOV.UK Notify letter specification. The method sends the contents of the file to NotifyNL.
postage (optional)
You can choose first class, second class or economy mail postage for your precompiled letter. Set the value to first for first class, second for second class or economy for economy mail. If you do not pass in this argument, the postage will default to second class.
Response
If the request to the client is successful, the client returns an array:
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
reference is a required property
Add a reference argument to the method call
postage invalid. It must be either first, second or economy.
Change the value of postage argument in the method call to either "first", "second" or "economy"
BadRequestError (status code 400)
Letter content is not a valid PDF
PDF file format is required.
Cannot send letters when service is in trial mode - see https://admin.notifynl.nl/trial-mode
Your service cannot send this precompiled letter in trial mode.
BadRequestError (status code 403)
Cannot send letters with a team api key
Use the correct type of API key.
Get message data
Get the data for one message
You can only get the data for messages sent within the retention period. The default retention period is 7 days.
Method
For example:
Arguments
notificationId (required)
The ID of the notification. To find the notification ID, you can either:
check the response to the original notification method call
sign in to NotifyNL and go to the API integration page
Response
If the request to the client is successful, the client returns an array:
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
id is not a valid UUID
Check the notification ID.
NoResultFound (status code 404)
No result found
If it’s outside the retention period, you may no longer get the status of the message. The default retention period is 7 days.
Get the data for multiple messages
This API call returns one page with data for up to 250 messages. You can get either the most recent messages, or get older messages by specifying a particular notification ID in the older_than argument.
You can only get messages that are within your data retention period. The default data retention period is 7 days. It can be changed in your Service Settings.
Method
You can leave out the older_than argument to get the 250 most recent messages.
To get older messages, pass the ID of an older notification into the older_than argument. This returns the next 250 oldest messages from the specified notification ID.
Arguments
You can leave out any of these arguments to ignore these filters.
template_type (optional)
You can filter by:
emailsmsletter
You can leave out this argument to ignore this filter.
status (optional)
You can filter by each:
You can leave out this argument to ignore this filter.
reference (optional)
A unique identifier you can create if necessary. This reference identifies a single unique notification or a batch of notifications. It must not contain any personal information such as name or postal address.
You can leave out this argument to ignore this filter.
older_than (optional)
Input the ID of a notification into this argument. If you use this argument, the method returns the next 250 received notifications older than the specified 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.
Response
If the request to the client is successful, the client returns an array.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
status ‘elephant’ is not one of [cancelled, created, sending, sent, delivered, pending, failed, technical-failure, temporary-failure, permanent-failure, pending-virus-check, validation-failed, virus-scan-failed, returned-letter, accepted, received]
Change the status argument.
‘Apple’ is not one of [sms, email, letter]
Change the template_type argument.
Email status descriptions
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.
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.
delivered
The message was successfully delivered.
permanent-failure
The provider could not deliver the message because the email address was wrong. You should remove these email addresses from your database.
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 before you try to send the message again.
technical-failure
Your message was not sent because there was a problem between Notify and the provider. You’ll have to try sending your messages again.
Text message status descriptions
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.
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.
pending
NotifyNL is waiting for more delivery information. NotifyNL received a callback from the provider but the recipient’s device has not yet responded. Another callback from the provider determines the final status of the text message.
sent
The message was sent to an international number. The mobile networks in some countries do not provide any more delivery information. The NotifyNL website displays this status as 'Sent to an international number'.
delivered
The message was successfully delivered.
permanent-failure
The provider could not deliver the message. This can happen if the phone number was wrong or if the network operator rejects the message. If you’re sure that these phone numbers are correct, you should contact NotifyNL support. If not, you should remove them from your database. You’ll still be charged for text messages that cannot be delivered.
temporary-failure
The provider could not deliver the message. This can happen when the recipient’s phone is off, has no signal, or their text message inbox is full. You can try to send the message again. You’ll still be charged for text messages to phones that are not accepting messages.
technical-failure
Your message was not sent because there was a problem between Notify and the provider. You’ll have to try sending your messages again. You will not be charged for text messages that are affected by a technical failure.
Letter status description
accepted
NotifyNL has sent the letter to the provider to be printed.
received
The provider has printed and dispatched the letter.
cancelled
Sending cancelled. The letter will not be printed or dispatched.
technical-failure
NotifyNL had an unexpected error while sending the letter to our printing provider.
permanent-failure
The provider cannot print the letter. Your letter will not be dispatched.
Precompiled letter status descriptions
accepted
NotifyNL has sent the letter to the provider to be printed.
received
The provider has printed and dispatched the letter.
cancelled
Sending cancelled. The letter will not be printed or dispatched.
pending-virus-check
NotifyNL has not completed a virus scan of the precompiled letter file.
virus-scan-failed
NotifyNL found a potential virus in the precompiled letter file.
validation-failed
Content in the precompiled letter file is outside the printable area. See the NotifyNL letter specification for more information.
technical-failure
NotifyNL had an unexpected error while sending the letter to our printing provider.
permanent-failure
The provider cannot print the letter. Your letter will not be dispatched.
Get a PDF for a letter notification
Method
This returns the PDF contents of a letter notification.
Arguments
notificationId (required)
The ID of the notification. To find the notification ID, you can either:
check the response to the original notification method call
sign in to NotifyNL and go to the API integration page
Response
If the request to the client is successful, the client will return a string containing the raw PDF data.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
ValidationError (status code 400)
id is not a valid UUID
Check the notification ID.
Notification is not a letter
Check that you are looking up the correct notification.
PDFNotReadyError (status code 400)
PDF not available yet, try again later
Wait for the letter to finish processing. This usually takes a few seconds.
BadRequestError (status code 400)
File did not pass the virus scan
You cannot retrieve the contents of a letter that contains a virus.
PDF not available for letters in technical-failure
You cannot retrieve the contents of a letter in technical-failure.
Notification is not a letter
Check that you are looking up the correct notification.
NoResultFound (status code 404)
No result found
Check the notification ID.
Get a template
Get a template by ID
Method
This returns the latest version of the template.
Arguments
templateId (required)
The ID of the template. Sign in to NotifyNL and go to the Templates page to find it.
Response
If the request to the client is successful, the client returns an array.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
NoResultFound (status code 404)
No Result Found
Check your template ID.
Get a template by ID and version
Method
Arguments
templateId (required)
The ID of the template. Sign in to NotifyNL and go to the Templates page to find it.
version (required)
The version number of the template.
Response
If the request to the client is successful, the client returns an array.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
NoResultFound (status code 404)
No Result Found
Check your template ID.
Get all templates
Method
This returns the latest version of all templates.
Arguments
template_type (optional)
If omitted, the method returns all templates. Otherwise you can filter by:
emailsmsletter
Response
If the request to the client is successful, the client returns an array.
If no templates exist for a template type or there no templates for a service, the client returns a dict with an empty templates list element:
Generate a preview template
Method
This generates a preview version of a template.
The parameters in the personalisation argument must match the placeholder fields in the actual template. The API notification client will ignore any extra fields in the method.
Arguments
templateId (required)
The ID of the template. Sign in to NotifyNL and go to the Templates page to find it.
personalisation (required)
If a template has placeholder fields for personalised information such as name or reference number, you need to provide their values in a dictionary with key value pairs. For example:
Response
If the request to the client is successful, the client returns an array.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
BadRequestError (status code 400)
Missing personalisation: [PERSONALISATION FIELD]
Check that the personalisation arguments in the method match the placeholder fields in the template.
NoResultFound (status code 404)
No Result Found
Check your template ID.
Get received text messages
This API call returns one page of up to 250 received text messages. You can get either the most recent messages, or get older messages by specifying a particular notification ID in the older_than argument.
You can only get the data for messages that are 7 days old or newer.
You can also set up callbacks for received text messages.
Enable received text messages
To receive text messages:
Go to the Text message settings section of the Settings page.
Select Change on the Receive text messages row.
Get a page of received text messages
Method
To get older messages, pass the ID of an older notification into the older_than argument. This returns the next 250 oldest messages from the specified notification ID.
If you leave out the older_than argument, the client returns the most recent 250 notifications.
Arguments
older_than (optional)
Input the ID of a received text message into this argument. If you use this argument, the client returns the next 250 received text messages older than the given ID. For example:
If you leave out the older_than argument, the client 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 collection response.
Response
If the request to the client is successful, the client returns an array.
Error codes
If the request is not successful, the client returns an error. To learn more about error structure, go to Errors section.
There are no errors specific to this endpoint, but you may encounter:
various schema validation errors, for example when you forget to pass in an argument, or pass in an argument of a wrong type.
errors that are not related to generating a preview template, but instead are related to things like authentication and rate limits. You can find a list of these errors in General errors
Errors
Error handling
If the request is not successful, the client raises an Alphagov\Notifications\Exception\ApiException object.
This error consists of:
a status code, for example
400an error type, for example
BadRequestErrora message, for example
Mobile numbers can only include: 0 1 2 3 4 5 6 7 8 9 ( ) + -
To access these details about the error, read its $e->getCode() and $e->getErrors() fields, for example:
Error’s $e->getErrors() field is a Array of arrays, for example:
Do not use the content of the messages in your code. These can sometimes change, which may affect your API integration.
Use the status code or the error type instead, as these will not change.
General errors
You may encounter following errors when making requests to a number of NotifyNL’s API endpoints.
BadRequestError (status code 400)
Cannot send to this recipient using a team-only API key.
Use a live API key, or add recipient to Guest list (located in API Integration section)
Cannot send to this recipient when service is in trial mode – see https://admin.notifynl.nl/trial-mode
You need to request for your service to go live before you can send messages to people outside your team.
BadRequestError (status code 403)
Error: Your system clock must be accurate to within 30 seconds
Check your system clock
Invalid token: API key not found
Use the correct API key. Refer to API keys for more information
RateLimitError (status code 429)
Exceeded rate limit for key type <team/test/live> of 3000/<custom limit> requests per 60 seconds
Refer to API rate limits for more information
TooManyRequestsError (status code 429)
Exceeded send limits (<sms/email/letter/international_sms>: <LIMIT SIZE>) for today
Refer to service limits for the limit size
Exception (status code 500)
Internal server error
Notify was unable to process the request, resend your notification.
Schema validation errors
The following are a few examples of schema validation errors you may encounter when making a request to a Notify endpoint.
ValidationError (status code 400)
template_id is a required property
Provide the missing argument.
sms_sender_id is not a valid UUID
Check the argument to make sure that it is valid for the given data type.
personalisation <data type of argument you sent> is not of type object
Provide argument in the correct type.
reference <reference string you provided> is too long
Provide a shorter string.
type <invalid type> is not one of [sms, email, letter]
Make sure that the argument matches one of the items in the list.
Additional properties are not allowed (<list of unexpected properties> was unexpected)
Only provide allowed arguments for the endpoint.
Endpoint-specific errors
In addition to the above, you may also encounter endpoint-specific errors, which are listed under each relevant API endpoint section.
Find references for endpoint-specific errors in:
Last updated