WhatsApp API error 368: Temporarily blocked for policy violations
Error 368 is an enforcement error. Meta has restricted or disabled the WhatsApp Business Account behind your app because of a platform policy violation, so the account can't do what you asked.
Quick answer
Your WhatsApp Business Account is restricted or disabled for a policy violation. Find the violation in the account's quality and policy notices, fix the cause, and request a review if you believe it's wrong.What WhatsApp error 368 means
Meta documents 368 as an integrity error: the WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy. Meta points to its policy enforcement guidance for the violation types and how to resolve them.
Why error 368 happens
Enforcement errors follow from how the account has been used. They usually trace back to one of these:
- Messaging people who didn't opt in, which leads to blocks and reports.
- Promoting products or services WhatsApp doesn't allow, such as medicines, alcohol or weapons.
- Content that breaks the Business Messaging Policy, such as misleading claims.
- Repeated template policy violations after warnings.
How to fix error 368
Recovery takes time, so the aim is to stop making it worse and fix the cause meanwhile.
- Open the account's policy and quality notices in WhatsApp Manager or Business Support Home to see the violation and its duration.
- Stop the activity that caused it: the campaign, the content or the audience.
- If you believe the decision is wrong, request a review through Meta's appeal flow with evidence of opt-in and content.
- Document your opt-in process and content checks so the problem doesn't recur.
Should you retry after 368?
Retrying doesn't work while the restriction lasts. Wait out a temporary restriction or get it lifted on review, and only then resume, starting with your most expected messages.
How error 368 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 368, the "(#368)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.