Why WhatsApp Business API rejects your template for 'invalid date format'

When WhatsApp Business API rejects a template for 'invalid date format,' it usually means that the text inside the template contains a date, time, or expiration written in a way that Meta cannot interpret for the language you declared. It is not an account error, it is not a ban, and it is not a billing issue: it is a content format problem. The good news is that it can almost always be fixed by editing the template text and resubmitting it for review. The bad news is that Meta does not publish the exact details of what it considers a 'valid format' for each language, so you often have to test. This article gives you the practical criteria to stop struggling with that rejection.

Is it serious, or can I fix it myself?

It is a content rejection, not an account rejection. The template is not approved, but your number keeps working, your other templates remain active, and you do not lose API access. You can fix it yourself if you have permission to edit templates in WhatsApp Business Manager or in the tool you use to manage them. The correction time depends on how many templates are affected and how many times you have to iterate: each resubmission goes through a new Meta review that can take up to 48 hours. There is no guaranteed shorter deadline.

Why it appears: the most common causes

The rejection message points to the date format, but the specific cause changes depending on how you wrote the text. These are the situations that most often generate that rejection:

• You wrote the date in a format that does not match the declared language. For example, a Spanish template with '05/12/2026' can be read as December 5 or May 12, and Meta has no way to disambiguate it.
• You used your country's format without clarifying it. '12/05/26' is ambiguous even for a human; for the review system too.
• You put the date as a variable and the example you uploaded has a different format than the fixed text. If in the body you write 'Expires on {{1}}' and in the variable example you put 'coming soon,' the reviewer does not see a date.
• You mixed formats within the same template: a long date in the header and a short one in the body, or one with the month spelled out and another with the month as a number.
• You wrote the time without indicating time zone or format (12 vs 24 hours). 'At 8' does not say whether it is AM, PM, or in which time zone.
• You used abbreviations or regional formats that are not standard, such as 'Mon Dec 5' without a year, or 'December 5' in the English style inside a Spanish template.
• The template is declared in one language but the content has date references in another. For example, an English template with '5 de diciembre.'

How to fix it, step by step

1. 1Open the rejected template and read the exact reason shown by Meta. Save a screenshot: if the rejection mentions 'invalid date format', the problem is in the text, not in the account configuration.
2. 2Check the declared language of the template. It must match the language of the text. If you are going to send in Spanish, the template goes in Spanish, not in English with Spanish text.
3. 3Choose a single date format for the entire template and write it in full: day with two digits, month with letters or numbers, and year with four digits. A clear and unambiguous example is 'December 5, 2026'.
4. 4If the date goes as a variable, enter in the variable example a real date written with the same format you would use in the fixed text. Do not put 'coming soon', 'to be confirmed' or generic text.
5. 5Check the time if the template mentions it. Indicate the format (for example, '14:30 hs') or clarify it in the text ('14:30, Argentina time'). Do not leave 'at 8' alone.
6. 6Look for abbreviations and regional formats inside the body, header, and footer. Replace them with the complete and consistent format you chose.
7. 7Save the changes and submit the template for review again. Approval can take up to 48 hours; there is no guaranteed shorter timeframe.
8. 8If after two attempts it is still rejected for the same reason, check if the problem is not in a variable that is filled on the side of the system that sends the messages. In that case, the template text is fine but the value that arrives in production does not respect the example format.

How to prevent it from happening again

• Define a single date format for all your templates and document it in your team. Changing it per template is the number one cause of repeated rejections.
• Write dates in full. Saving characters does not compensate for a rejection.
• Always enter variable examples with real data and with the same format you use in the fixed text.
• If your template is used in several countries, check that the chosen format is understood in all of them. In case of doubt, month with letters is safer than month with numbers.
• Before sending a batch of new templates, test one with the format you plan to use. If it passes, replicate it.
• If you use a tool to manage templates, check if it has a preview with sample data: it helps to detect the problem before submitting for review.

When the real problem is different and this error is only the symptom

Sometimes the rejection for date format appears as a consequence of something deeper. Three typical cases:

• The system that sends the messages is filling the variable with a different format than the approved example. The template is approved, but the messages in production may fail or arrive with strange data. There the problem is not the template, it is the system that uses it.
• You are reusing an old template for a new case. The text is outdated, the date format no longer applies, and the rejection is the signal that it needs to be rewritten, not patched.
• The real rejection is for another reason and Meta's message mentions the date format as a secondary detail. If after correcting the format it is still rejected, check if there are misdeclared variables, promotional text where it does not belong, or the wrong category chosen.

What this error is NOT

It is not an expired token problem, it is not an unverified number problem, and it is not a messaging limit reached. Each of those has its own symptom and its own solution path. If your template is rejected for date format, the rest of the account is working fine and there is no need to touch the technical configuration.

If you use a platform to manage WhatsApp

If instead of calling the API directly you use a platform that handles templates for you, editing and resubmitting for review are done from that platform's dashboard, not from WhatsApp Business Manager. In that case, appealing the rejection and resubmitting are up to the platform. Wando, for example, lets you create and submit templates for review from its dashboard, with AI suggestions for the text, and notifies you when Meta responds. If you want to see how it works, you can try it for 14 days without a card.

Checklist before resubmitting

• Declared language = language of the text.
• A single date format throughout the template, written out in full.
• Variables with a real example and the same format as the fixed text.
• Time with an explicit format and, if applicable, time zone.
• No regional abbreviations or ambiguous formats.
• You checked the header, body, and footer, not just the body.