Documentation Mercado Libre

Check out all the necessary information about APIs Mercado Libre.
circulos azuis em degrade

Documentation

Last update 06/04/2026

Security practices, validations and requirements for integrators

The purpose of this document is to share and maintain a set of security requirements that must be taken into account throughout the entire integration development lifecycle. The points mentioned below aim to protect your application/integration from common threats, such as credential theft, information leakage, and commercial fraud. We encourage our integrators to build solutions aligned with cybersecurity best practices, thus ensuring the integrity and protection of confidential information of Mercado Libre sellers.

The absence of these controls compromises the operational continuity of your integration, from non-compliance with Mercado Libre audits to the possible revocation of API permissions. Beyond the administrative aspect, it would leave your infrastructure and the critical information of sellers vulnerable to external threats.

How to read this documentation

Each section includes:

Element Description
Why is it important? Explanation of the risk and importance of using the best practice
Examples: correct vs incorrect Visual comparison of what is right and wrong
How to verify? Concrete steps to check whether you comply with the best practice
Self-diagnosis questions Answer Yes/No to evaluate the adoption of the practice in your integration

Governance and compliance

Introduction

In the Mercado Libre ecosystem, the trust of sellers and buyers is our hallmark of confidence, and the role of the integrator is critical to maintaining the integrity of this chain. By developing applications that interact with the marketplace APIs, the integrator not only manages operational data, but becomes a custodian of the seller's experience and the privacy of their transactions.

This guide establishes the security standards necessary for external integrations not only to function efficiently, but to act as a robust and secure extension of our infrastructure, controlling risks so that no external vulnerability impacts organizational stability or the trust of our end users.

Security Responsibility

Security in a service- and API-oriented architecture does not rest on a single actor, but is distributed under a shared responsibility model that delimits the obligations of Mercado Libre and those of the integrator. Mercado Libre assumes responsibility for platform security, which involves protecting the global infrastructure, data centers, network protocols, and the availability of API endpoints. This responsibility spans from the physical layer to the digital layer that hosts the marketplace services.


For its part, the integrator is responsible for security within its application and for managing the data it extracts or processes. This includes the security of their applications, the operating system configurations of their servers, the installation of security patches, the management of their databases, and access control to their internal systems. A security failure on the integrator's side, such as a misconfigured database or code vulnerable to injections, is the direct responsibility of the integrator. Transparency in this division allows both parties to focus their security resources effectively, ensuring that the protection of seller information is airtight throughout the entire data journey.



Next: Infrastructure: Encryption and transport security.