Messenger error 100: Product template not supported below v8
Last verified against Meta for Developers - Messenger Platform error codes
Product template is not supported below version 8. Use API version 8 or higher to use product templates.What error 100 means
Code 100 with subcode 2018328 is a version gate. The message says it plainly: "Product template is not supported below version 8. Use API version 8 or higher to use product templates." The product template guide repeats the requirement as a warning at the top of the page: the template "is only available on Graph API v8.0+."
The version that matters is the one in the request path, as in graph.facebook.com/v7.0/me/messages, or, if the path has no version, the app's default API version in the App Dashboard. Old samples, old SDK releases and hand-built URLs from earlier integrations often still say v2.6 or similar, and every other message type keeps working there, so nobody notices until the first product template goes out.
Nothing is wrong with your catalog, your product IDs, or your permissions. Once the same body is sent to a newer version, it either succeeds or moves on to a different error such as 2018320 if the IDs themselves are bad.
What it looks like
{
"error": {
"message": "(#100) Product template is not supported below version 8. Use API version 8 or higher to use product templates.",
"type": "OAuthException",
"code": 100,
"error_subcode": 2018328,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- A hard-coded Graph API version below v8.0 in the Send API URL.
- Unversioned calls on an app whose default API version is older than v8.0.
- Third-party or legacy SDKs that pin an old version.
- Sample code copied from older Messenger tutorials.
- The request is on v8.0 or later but the Page has no connected product catalog, which the product template also needs; fix the version first, then check the catalog.
How to fix Messenger error 100
- 1Change the request path to a current Graph API version (v8.0 or later; ideally the latest).
- 2Check the app's default API version in the App Dashboard and update it if calls are unversioned.
- 3Upgrade or configure your SDK so it sends an explicit modern version.
- 4Re-test other message types after the upgrade, since newer versions may change field behavior.
- 5Make sure the product IDs you send come from a catalog connected to the Page, as the product template guide requires.
How to stop it recurring
Put the Graph API version in one configuration value used by every call, and schedule upgrades before Meta retires the version you are on. A single integration test that sends a product template to a test user on the configured version catches the problem before customers do.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
Error 100 - quick answers
What does Messenger error 100 mean?
Code 100 with subcode 2018328 is a version gate. The message says it plainly: "Product template is not supported below version 8.
How do I fix Messenger error 100?
1. Change the request path to a current Graph API version (v8.0 or later; ideally the latest). 2. Check the app's default API version in the App Dashboard and update it if calls are unversioned. 3. Upgrade or configure your SDK so it sends an explicit modern version. 4. Re-test other message types after the upgrade, since newer versions may change field behavior. 5. Make sure the product IDs you send come from a catalog connected to the Page, as the product template guide…
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.