Integrations (iPaaS)
Connect your ERP and your providers to Mercado Eletrônico without building an integration from scratch.
ℹ️ Note
In the Partner's Portal, iPaaS is the Integrations area of the top menu, with Templates, My integrations and, under Settings, Connectors. Integration executions are in Monitoring > Executions.
iPaaS (Integration Platform as a Service) is Mercado Eletrônico's integration platform. It sits between your system (ERP, middleware or external provider) and ME and takes care of receiving the data, converting the format, delivering it to the target and recording every step of the execution.
Instead of adapting your ERP to the format of the ME APIs, or the other way around, you create an integration from a template, provide a sample of your system's format and review the AI-suggested field mapping. From then on, the platform performs the conversion every time the integration runs.
What iPaaS solves
- Less development: your system keeps sending and receiving JSON in the format it already knows. The conversion to the ME format, or of the queried data (from ME or from an external REST provider) to the format you use, is done by the platform.
- AI-assisted mapping: the AI analyzes a sample of your payload and suggests how the fields connect, with a confidence percentage. You review, adjust and publish.
- Validation before publishing: every integration goes through a real test before it is activated.
- Traceability: every execution is recorded, with the status of each step, the errors and the Correlation ID you can provide to find the execution later.
- Dedicated credential per integration: each integration has its own access key, which only runs that integration.
Concepts
| Concept | What it is |
|---|---|
| Integration (flow) | A published configuration that performs one type of data exchange, for example "create orders in ME from my ERP". Each integration has an execution address (Endpoint URL) and its own credential. |
| Template | The model used to create the integration. It defines the direction, the type of operation and the configuration steps. See Templates. |
| Direction | Inbound (your system sends data to ME) or Outbound (a query: the caller fetches data from ME or from an external REST provider, through a connector, and gets the result back in the response, already in the format it will use). |
| Document type | The ME document involved in the integration, for example order, invoice or contract. |
| Mapping | The rule that says where each target field comes from. It is suggested by the AI and reviewed by you. See AI mapping. |
| Connector | The registration of an external REST API (URL, authentication and resources). Some templates may require it. See Connectors. |
| Execution | Each call made to the integration. It generates a record with status, duration and the detail of each step. See Executions. |
Flow directions
| Direction | Way | Example |
|---|---|---|
| Inbound | Your system → ME | The ERP sends a purchase order, and iPaaS creates the order in ME. |
| Outbound | Query (ME or external REST provider → response) | Your system provides the identifier of an ME document and gets that document back in the response, already in the ERP format. Or ME queries an external REST provider, through a connector, to search for products. iPaaS does not send data to your system: the result comes back in the response to the call. |
Available templates
| Template | Direction | What it does |
|---|---|---|
| Document Creation (Inbound) | Inbound | Receives a document from your ERP, converts it to the ME format and creates the document in ME. |
| Document Search (Outbound) | Outbound | Fetches an ME document by its identifier and returns the document converted to your ERP format. |
| Product Search | Outbound | Connects a catalog REST provider so that ME can search products and offers in real time. |
Journey at a glance
- Choose a template in the Partner's Portal, under Integrations > Templates.
- Configure the parameters: ERP, document type and, in Product Search, the connector.
- Provide the document structure: paste a sample of your system's JSON.
- Review the mapping suggested by the AI.
- Test the integration with a real execution.
- Publish. The integration becomes Active. In Document Creation (Inbound) and Document Search (Outbound), the final screen shows the credential (Key and Secret): copy the Secret before leaving the wizard. In Product Search, the caller of the integration is ME itself, and there is no credential to copy.
- Run it by calling the integration's Endpoint URL with a token generated from that credential.
- Track the executions in Monitoring > Executions.