WhatsApp AI Access: One Year On, Meta Faces Binding Orders

One year ago today, on 15 October 2025, Meta’s WhatsApp access policy took effect for new AI providers. That anniversary now marks a competition dispute in which binding European Commission orders—not Meta’s original restrictions—govern access for competing general-purpose AI assistants in the territory covered by the investigation.

What's changing

The central issue is whether Meta unfairly restricted rival AI providers’ access to the WhatsApp Business Application Programming Interface, or API, while keeping its own Meta AI service fully integrated. The API is the connection that lets providers deliver services through WhatsApp; restricting it can limit their ability to reach customers on the platform.

This is an investigation into a company policy, not a new EU AI regulation. The policy became effective for new AI providers on 15 October 2025 and for existing providers on 15 January 2026. Today’s anniversary concerns the first effective date, not an enactment or signing date.

The European Commission opened its formal antitrust investigation on 4 December 2025. It subsequently issued a Statement of Objections concerning potential interim measures on 9 February 2026. Those steps concerned a possible competition violation; they did not establish a final finding that Meta had broken competition rules.

Meta announced revised, fee-based access on 4 March 2026. The Commission rejected that approach in its Supplementary Statement of Objections on 15 April 2026. On 9 June 2026, it adopted a Decision imposing binding interim measures.

Those measures require Meta to restore free WhatsApp Business API access for competing general-purpose AI assistants and maintain the pre-October 2025 access terms throughout the formal investigation. They are live obligations, not proposals or an approaching deadline.

The distinction matters: Meta’s policy has a year-long history of being in effect, but its original restrictions have not remained unchanged or controlling throughout that period. The June orders override them within the scope of the Commission’s measures.

The investigation remains under review. If the Commission ultimately finds abuse of a dominant market position, it can require permanent changes to Meta’s structure or conduct and impose fines reaching up to 10% of Meta’s total annual worldwide turnover. It can also impose periodic penalty payments for failure to comply with orders. Those potential consequences are separate from the interim access requirements already in force.

Who is affected

The Commission’s investigation targets Meta across the European Economic Area, excluding Italy. Although this is an EU-level proceeding, businesses should use that stated geographic scope rather than assume the interim measures apply identically everywhere.

Italy is the important exception. The Italian Competition Authority, AGCM, opened parallel proceedings on 30 July 2025. The specific EU interim measures described here do not cover Italy, so providers operating there need to assess the separate Italian proceedings rather than rely on the Commission’s access order.

The direct business impact falls on third-party AI assistant developers seeking to reach users through WhatsApp. The interim restoration requirement specifically concerns competing general-purpose AI assistants. That makes the case particularly relevant to providers whose distribution plans depend on WhatsApp Business API access.

No company-size threshold is specified in the supplied requirements. A small assistant developer can therefore have a substantial commercial interest in the outcome, just as a larger provider can. But the access orders bind Meta; they should not be read as imposing the same platform-restoration duty on every developer.

Three things to do this week

1. Preserve the investigation evidence. For Meta and any business involved in the proceedings, identify and retain relevant policy notices, API-access correspondence, contracts, pricing communications and technical records. Keep the chronology clear: the October and January policy dates, March fee proposal and June interim order represent different stages. Developers documenting access problems should preserve original messages and dated records rather than rely only on recollections.

2. Prepare complete, accurate information responses. If your business receives a Commission request for information, assign an owner and bring legal, commercial and technical teams together. Check answers against source records and identify any gaps before submission. The implementation requirements call for full and accurate responses; an unsupported claim that access has been restored is not a substitute for evidence of actual access conditions.

3. Make inspection readiness practical. Businesses subject to necessary Commission inspections should ensure relevant staff know how to contact the response team and locate requested records. The implementation requirements include allowing Commission officials to conduct necessary inspections. Separately, affected developers should review current access arrangements against the free, pre-October 2025 terms required by the interim measures and document any discrepancies.

Related context

The Commission’s guidelines on prohibited AI practices under the AI Act address a different question: prohibited uses of AI, rather than competitive access to a messaging platform. Meeting those expectations does not resolve the access issues in this investigation.

The UK Competition and Markets Authority’s initial report on foundation models offers related competition context, but it is a report from another jurisdiction—not the source of Meta’s EU obligations. For this anniversary, the operational takeaway is immediate: the investigation continues, and the Commission’s interim access orders already bind Meta.

Note: this article was drafted by AI - OpenAI GPT-6.1