canonical: https://jentic.com/apis/revolut.com/merchant-api # Revolut Merchant API Welcome to the Revolut Merchant API - your solution to managing the core aspects of e-commerce and accepting online payments. Whether you're a startup, a growing business, or an established enterprise in the e-commerce industry, our API helps you streamline your operations. As a Revolut Business customer with a Merchant Account, you can use the Merchant API to leverage the following features: - [O. The API exposes 45 endpoints secured with SSL, apiKey authentication. ## For AI agents Programmatically create an order, retrieve an order. Covers 45 operations with SSL, apiKey authentication. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Create an order - Retrieve an order - Update an order - Capture an order - Cancel an order - Refund an order ## Use cases ### Payments Operations Use the Merchant API to perform payments operations programmatically. The API provides 45 endpoints covering core functionality including create an order, retrieve an order, update an order. Example prompt: Call POST /api/orders to create an order ### Automated Orders Management Automate orders operations by combining multiple Merchant API endpoints. Agents can retrieve an order and then update an order in a single workflow. Example prompt: Call GET /api/orders/{order_id} to retrieve an order, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Merchant API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle SSL, apiKey tokens manually. Example prompt: Search Jentic for 'create an order', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /api/orders | Create an order | | GET | /api/orders/{order_id} | Retrieve an order | | PATCH | /api/orders/{order_id} | Update an order | | GET | /api/1.0/orders | Retrieve an order list | | POST | /api/orders/{order_id}/capture | Capture an order | | POST | /api/orders/{order_id}/cancel | Cancel an order | | POST | /api/orders/{order_id}/refund | Refund an order | | POST | /api/orders/{order_id}/payments | Pay for an order | ## Key resources - **Orders** — The Orders resource in the Merchant API offers a comprehensive solution for managing the lifecycle o - **Customers** — The Customers resource in the Merchant API is a pivotal tool for tracking and managing customer-rela - **Payments** — Payment operations enable you to initiate payments, or track payment status transitions. You can use - **Payouts** — Endpoints for retrieving information about payouts, allowing merchants to access details of funds wi - **Disputes** — Endpoints that allow merchants to view customer payment disputes. It provides a robust framework ## Why Jentic - **Setup:** Wiring the Revolut Merchant API by hand means handling its Authorization header API key alongside its SSL and payload-signature requirements, choosing the live merchant.revolut.com or sandbox host, and managing retries yourself. Through Jentic you install once, import the Merchant API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Revolut Merchant puts the order id in the URL path (/api/orders/{order_id}), so a rule can pin your agent to one order: it can read that order and nothing else. You choose the operations it may call, so ones like capturing, cancelling, or refunding an order are not included unless you add them. - **Credential handling:** Your Revolut Merchant API key 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 'create an order' or 'capture a payment', and Jentic returns the matching Merchant API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### What authentication does the Merchant API use? The Merchant API uses SSL, apiKey authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I create an order with the Merchant API? Yes. Use the POST /api/orders endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Merchant API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I create an order through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an order'. Jentic returns the matching Merchant API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Merchant API have? The Merchant API exposes 45 endpoints covering orders, customers, payments operations. ### Can I limit what my agent is allowed to do with the Merchant API? Yes. Jentic One is self-hosted, so your own rules decide which Merchant API operations and credentials the agent may use. Because the order id sits in the URL path (/api/orders/{order_id}), you can pin the agent to a single order and let it only read that order and nothing else. You choose which operations it may call, so sensitive actions like capturing, cancelling, or refunding an order stay off limits unless you explicitly add them.