canonical: https://jentic.com/apis/mercadolibre.com/mercadolibre # Mercadolibre Verdi Flows Webhook External API The Verdi Flows Webhook External API receives Solman revision events on Mercado Libre's API host and hands them to a Verdi Flows GenAI workflow. Its single operation accepts a JSON body with exactly two required fields, a solman identifier such as ASUASC2314 and an integer revision number, and rejects any extra properties. The call is authorized with OAuth 2.0 against the api.mercadolibre.com token endpoint, and a 504 response signals that the downstream workflow did not respond in time. ## For AI agents Notify a Mercado Libre Verdi Flows workflow that a Solman change record has a new revision by posting its solman identifier and revision number to the external webhook. ## Scope Does not list Mercado Libre products, manage orders or listings, or read the workflow's results. Use for posting Solman revision events to the Verdi Flows webhook only. ## Capabilities - Post a Solman revision event with the solman identifier and revision number to trigger the Verdi Flows workflow - Detect a timed-out downstream workflow through the 504 response and retry the same revision event - Validate a revision payload against a strict two-field schema that rejects additional properties ## Use cases ### Agent-sent revision notifications through Jentic When a change record in Solman moves to a new revision, an agent can notify the Verdi Flows workflow without anyone wiring the OAuth handshake by hand. Through Jentic it finds the webhook operation, posts the solman identifier and revision number, and reports whether the workflow accepted it. The OAuth token stays in your own Jentic One instance, and the agent never sees it. Example prompt: Call POST `/workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external` with solman 'ASUASC2314' and revision 2, and report success on a 200 response ### Change-management to GenAI workflow handoff Teams that track changes in Solman use this webhook to kick off downstream GenAI processing for each revision. The body carries only the record identifier and the revision number, so the sender stays simple, and the strict schema with additionalProperties set to false means any extra field is rejected rather than silently ignored. Example prompt: Read the latest revision number for change record 'ASUASC2314', then POST it as revision with solman 'ASUASC2314' to the Verdi Flows external webhook ### Timeout-aware retries The webhook waits on the workflow it triggers, and returns 504 when that workflow does not respond in time. A sender that sees 504 can retry the same solman and revision pair, while 401 and 403 indicate the OAuth credentials need attention rather than a retry. Example prompt: POST solman 'ASUASC2314' and revision 3 to the Verdi Flows external webhook, and if the response is 504, wait and resend the same body once ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external` | Receive a Solman revision event | ## Key resources - **Revision events** — Solman identifier and revision number pairs delivered to the Verdi Flows workflow ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 75 / 100 - **Maturity:** AI-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 88 / 100 - AI-Readiness & Agent Experience: 58 / 100 - Agent Usability: 94 / 100 - Security: 90 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/mercadolibre.com/mercadolibre/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Verdi Flows webhook by hand means running the OAuth 2.0 authorization-code flow against api.mercadolibre.com, refreshing the token, and posting to a long path with a fixed workflow id. Through Jentic you install once, import the webhook from the API Directory, store the OAuth credential once, and your agent calls it. - **Permission scoping:** The workflow id is fixed in the URL path of the only operation, so a rule allowing that single POST pins your agent to this one Verdi Flows workflow. Nothing else on the Mercado Libre host is reachable unless you import and allow it. - **Credential handling:** Your Mercado Libre OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a Solman revision event' or 'trigger the Verdi Flows workflow', and Jentic returns the webhook operation with its input schema, including the required solman and revision fields, so the agent calls it correctly. ## Related APIs - **Hookdeck API** — Webhook gateway that queues, retries, and inspects webhook deliveries - **n8n API** — Workflow automation platform whose workflows can be triggered by webhooks - **Pipedream API** — Event-driven workflows triggered by HTTP requests and app events ## FAQ ### What authentication does the Verdi Flows Webhook External API use? Per its OpenAPI spec, the webhook uses OAuth 2.0 with an authorization-code flow whose authorization and token URLs both point at the `/oauth/token` path on api.mercadolibre.com, and it declares no scopes. A 401 response means the credentials were invalid and a 403 means authorization failed. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time. ### What payload does the Verdi Flows webhook expect? A JSON object with two required fields: solman, a non-empty string identifier such as ASUASC2314, and revision, an integer of 0 or more. The schema sets additionalProperties to false, so any extra field is rejected. ### What are the rate limits for the Verdi Flows Webhook External API? The OpenAPI spec does not specify rate limits. It does document a 504 response when the downstream workflow does not respond in time. Check the Mercado Libre developer documentation at https://developers.mercadolibre.com for current limits. ### Is there a Verdi Flows MCP server? You don't need an MCP server to give your agent the Verdi Flows webhook. Jentic connects it directly from the API Directory: import it, store your OAuth credential once, and your agent posts revision events without loading another server's tool definitions into its context. ### How do I send a Solman revision event through Jentic? Search Jentic for 'send a Solman revision event', load the POST `/workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external` operation, and execute it with solman and revision in the body. A 200 response means the webhook received it. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Verdi Flows Webhook External API? Yes. The webhook path already carries a fixed workflow id, so a rule allowing only that one POST operation lets the agent deliver revision events to this workflow and nothing else on the Mercado Libre host. Every call it makes is logged, so you can audit which revisions it sent.