Application blocking

To ensure platform security and stability, follow our Best practices when integrating with iFood APIs. Inappropriate use may result in temporary or permanent blocking of your account.Our systems monitor API usage. If we detect violations, we will send an email with:

Type of infraction and evidence
Deadline for correction
Consequences if not corrected within the deadline

Updated data

Keep your data updated (email, phone) to receive notifications about infractions. Outdated data may result in blocks without prior notice.

Blocking levels

Level	Restriction
I	The Integrator's application will be removed from the Marketplace area in the Partner Portal. If it's a Super Integrator, they will lose the program seal.
II	The integration will be prevented from requesting new merchant authorizations for their application.
III	Application blocked from consuming iFood APIs

Level I

At this blocking level, the Integrator's application will be removed from the Partner Portal Marketplace list, making it impossible for Merchants to view the application. This action will directly impact the realization of new integrations with Merchants.

Level I correction deadline

Correction deadline: 15 calendar days, counted from the date of sending the first communication.

Level II

At this blocking level, the integration will be subject to all sanctions provided for in level I blocking. Additionally, it will not be possible to request new merchant authorizations for the application. Merchants that already use the POS will also not be able to reauthorize the application if the session expires.The integrator will also lose eligibility for the Super Integrator program in the next award cycle at this level II blocking.

Level II correction deadline

Deadline for level II blocking correction: 15 calendar days after the first communication.

Level III

At this blocking level, the integration will be subject to all sanctions provided for in level I and level II blocking. Additionally, the application will be completely blocked from consuming iFood APIs, meaning no merchant integrated to this integrator's system will be able to use the integration with iFood. Initially, a temporary 24-hour block will be applied during a period of lower order volume. If the integrator does not present an action plan within the established deadline, the application will be blocked again and for an indefinite period, without time restrictions.

Level III correction deadline

Deadline to present action plan: 10 calendar days after the 24-hour temporary block.

Resolution deadline

iFood reserves the right to define/update the resolution deadline for infractions committed by the integrator. This deadline will be stipulated and formally communicated to the integrator.

Types of infractions

Not sending ack for polling events
Sending requests with invalid format (Error 400)
Using invalid or expired tokens (Error 401)
Querying details of non-existent orders (Error 404)
Querying unauthorized Merchants (Error 403)
Polling with intervals less than 30 seconds
Querying the same order more than 10 times
Exceeding the maximum requests that a single application can make in a given time period (Rate Limit)
Improperly exposing credentials in the url
Keeping the application inactive without API calls for 90 consecutive days

The endpoints listed below will have more rigorous monitoring, leading to the application of sanctions when abusive use is identified, including reflecting on the eligibility requirements of the Super Integrators Program.

Endpoint	Limits
/orders/{id}	Maximum error rate <= 2%
/orders/{id}/confirm	Maximum error rate <= 2%
/orders/{id}/requestCancellation	Maximum error rate <= 2%
/events:polling	Maximum error rate <= 1%
/merchants/{merchantId}/status	Maximum error rate <= 1%
/merchants/{merchantId}	Maximum error rate <= 2%
/merchants	Maximum error rate <= 2%
/merchants/{merchantId}/interruptions	Maximum error rate <= 2%
/events/acknowledgment	Minimum ack rate >= 95%