# EasyEcom MCP connector

The EasyEcom connector brings business orders, inventory, carriers, B2B invoices and customers into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can read and update them as the person who signed in.

Source: https://elaichi.ai/connectors/easyecom/

## Facts

| | |
| --- | --- |
| Application | EasyEcom |
| Category | Ecommerce |
| AI tools | 99 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once EasyEcom is connected

- Set SKU ABC123 to 40 units at the Delhi warehouse.
- Create a business order for Metro Stores, 200 units of SKU 4471.
- Reassign order 10482 to a new carrier and get the delivery date.

## Connect EasyEcom in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick EasyEcom.
2. Optionally set Share with, then press Connect.
3. Paste an EasyEcom API key. One person generates a token in EasyEcom and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which EasyEcom tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## EasyEcom MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## EasyEcom MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## EasyEcom MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## EasyEcom MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## EasyEcom MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect EasyEcom to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a EasyEcom tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with EasyEcom through Elaichi

### Push a stock correction across every location

Operations. After a cycle count, give the agent the new quantities and it files a batch or bulk inventory update in EasyEcom instead of someone editing rows by hand. Ask for a consolidated inventory report first to see where the gaps are.

### Raise an ASN before the truck arrives

Warehouse. Describe the inbound shipment and the agent creates the advance shipping notice in EasyEcom, so receiving knows what is coming and which child location it is headed to.

### Move a stuck order to another carrier

Logistics. When a courier misses a pickup, ask the agent to unassign the carrier, reassign the order, and fetch the new estimated delivery date to pass on to the customer.

### Book a wholesale order and get it approved

B2B sales. Turn a buyer's email into a business order in EasyEcom, send it for approval and assign it, without switching screens during the call.

### Raise the B2B invoice and close the credit note

Finance. Create the invoice and its line details for a wholesale order, then set the credit note status so the ERP stays in step with EasyEcom.

### Add a new buyer and update their tracking

Customer service. Create the customer record in EasyEcom when a first order lands, then post the latest tracking status on their B2B order so the answer lives in the system, not in a chat thread.

## Elaichi vs Zapier MCP vs Composio for EasyEcom

All three can connect EasyEcom to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over EasyEcom tools | Allow or restrict single EasyEcom tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per EasyEcom call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect EasyEcom to Claude?

Two steps. In Elaichi, choose EasyEcom and paste your EasyEcom API key, which is the only sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in as yourself and EasyEcom is available in the chat.

### Does EasyEcom work with ChatGPT and Cursor as well as Claude?

Yes. Connect EasyEcom once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. There is nothing to set up again per client.

### What can an AI agent actually do with my EasyEcom data?

It can update stock in bulk, raise an ASN for an inbound shipment, create a business order and push it through approval and assignment, reassign a carrier and fetch the new delivery estimate, raise B2B invoices, set credit note status, and look up or create customers in EasyEcom. It can also list your locations, channel statuses, company groups and custom fields when you ask. Short, concrete asks such as reassign order 10482 to a new carrier work better than long paragraphs.

### Does connecting EasyEcom give the AI access to everything in my account?

No. Every call to EasyEcom runs with the access of the person who signed in, so the agent sees the locations, orders and customers that person can already see. Elaichi can narrow that further with roles and restrictions, and it never widens what EasyEcom itself allows.

### Can my team share one EasyEcom connection?

Yes. One person connects EasyEcom with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who updated stock or created the order, not the account owner.

### Can I stop an agent from changing inventory or orders in EasyEcom?

Yes. Restrictions in Elaichi work per action, so you can restrict bulk inventory updates or carrier reassignment in EasyEcom for a role or for one person while leaving lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an EasyEcom connection when someone leaves?

Offboarding them in Elaichi ends their access to EasyEcom through every client at once. If they shared the EasyEcom connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnect EasyEcom once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the EasyEcom MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. EasyEcom is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for EasyEcom?

Yes. Both let Claude, ChatGPT or Cursor use EasyEcom. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every EasyEcom call.

### How is Elaichi different from Composio for EasyEcom?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to EasyEcom: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 99 EasyEcom tools

Every tool below is callable through https://api.elaichi.ai/mcp once EasyEcom is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a EasyEcom access token** (Create). Get an API JWT (valid 90 days) with the stored email, password and location key. The connector does this on connect and every week; you rarely need it directly.
- **Create a EasyEcom asn** (Create). create asn. (EasyEcom V2.1: POST /wms/createASNSummaryAndASNDetails; docs: Inventory / Create ASN.) Required: po_id, vendor_token, asn_details.
- **Create a EasyEcom b 2 b invoice detail** (Create). This API is used to update invoice details for an order in OMS. Either Pass base64url OR invoicePdf , there is no requirement for passing the both the keys at once. (EasyEcom V2.1: POST /oms/b2b/v1/save-invoice-details; docs: Order / OMS B2B – Save Invoice Details.) Required: invoice_id, base64url.
- **Create a EasyEcom b 2 b invoice** (Create). It is used to generate a B2B invoice. (EasyEcom V2.1: POST /orders/generateB2BInvoiceAPI; docs: Order / B2B Generate Invoice.) Required: invoiceId.
- **Create a EasyEcom b 2 b order approval** (Create). This API is used to approve B2B orders, similar to the approval process available in the EasyEcom UI: Orders → B2B Orders → Unapproved Orders → Approve Order . API supports both: Full order approval Partial order approval (by providing confirmed quantities per order item If confirmed quantities are not provided, the ordered quantity should be considered as the confirmed quantity for all order items. (EasyEcom V2.1: POST /oms/b2b/v1/orders/approveBulkOrder; docs: Order / B2B Order Approval.) Required: reference_code.
- **Create a EasyEcom b 2 b order assignment** (Create). This API is used to assign inventory to the respective SKU/order via API. (EasyEcom V2.1: POST /order/assign-approveB2bOrder; docs: Order / B2B Order Assign.) Required: order_items.
- **Create a EasyEcom b 2 b tracking status** (Create). Updates the tracking/shipping status of a B2B order (AWB). Required Fields Optional Fields Current Shipment Status Table:-. (EasyEcom V2.1: POST /Carrier/V2/updateTrackingStatusB2B; docs: Shipment / UpdateTrackingStatusB2B.) Values - / current_shipment_status_id / Note: Pickup Scheduled/Generated=18=After status id=18, you have to send as status id=19 only.; Out For Pickup=19=After status id=19, you have to send status id=2.; Shipped/In Transit/Delayed/Reached at Destination/Misrouted/Picked Up=2=After status id=2, either send status id=20 or 17.; Out For Delivery=20=After status id=20, either send status id=16 or 3.; Undelivered=16=After status id=16, either send status id=3 or 17.; Delivered=3=After status id=3, shipment can not be moved to any other status.; RTO Initiated=17=After status id=17, you have to send status i
- **Create a EasyEcom batch inventory update** (Create). This Asynchronous API is used to update/overwrite the EasyEcom inventory for the mentioned SKUs with batch code and expiry. Please note: This API only works for the Non-WMS plan . _For updating the current Plan against your current location,_ Please reachout to us at care@easyecom.io Please Note: The Expiry Enabled products can be identified with the Given Key: "expiry_type" in the Get Master Product API Response Data. (EasyEcom V2.1: POST /inventory/bulkInventoryUpdateWithBatchCodeAndExpiry; docs: Inventory / Bulk Inventory Update With BatchCode And Expiry.)
- **Create a EasyEcom bulk inventory update** (Create). This Asynchronous API is used to update/overwrite the EasyEcom inventory for the mentioned SKUs. Please note: This API only works for the Non-WMS plan . For updating the current Plan against your current location, Please reachout to us at care@easyecom.io The configuration for the Inventory Updates sent via the given API call can be configured from Account settings &gt;&gt; Other Settings&gt;&gt; Method to update inventory in the Manage inventory page. (EasyEcom V2.1: POST /inventory/bulkInventoryUpdate; docs: Inventory / Bulk Inventory Update.)
- **Create a EasyEcom business order** (Create). We have one API to create multiple types of orders as below : B2C - B2C stands for Business-to-Consumer, a model where businesses sell products or services directly to individual consumers. This model encompasses various sectors, including retail and online commerce, focusing on direct interactions between companies and end-users. (EasyEcom V2.1: POST /create-business-order; docs: Order / Create Order.) Values - Order type / Order Type Value / Customer Id: B2C=retailorder=Should not be present; B2B=businessorder=Mandatory; STN=stocktransferorder=Mandatory; Production Order=productionorder=Should not be present | Payment Mode / Payment Mode Id: COD=2; Prepaid=5 | Shipping Method / Shipping Method Id: Standard COD=1; Standard Prepaid=3 Required: orderType, orderNumber, orderDate, paymentMode, is_market_shipped, OrderItemId, shippingMethod.
- **Create a EasyEcom carrier credential** (Create). It is used to integrate the carrier with Easyecom. NOTE:-Refer our Knowledgebase, which is given below, to know which field is required and it varies with carriers and aggregators. Knowledgebase URL- https://support.easyecom.io/portal/en/kb/campaigngroup1450092794169. (EasyEcom V2.1: POST /Credentials/addCarrierCredentials; docs: Shipment / Add Carrier Credentials.) Required: carrier_id, username, password.
- **Create a EasyEcom carrier estimated delivery date** (Create). Deprecated by EasyEcom: use estimated_delivery_dates.create (POST /Carrier/predict-estimate-deliverydateV2). It is used to get Estimated delivery date. EasyEcom Internally calls carrier APIs to fetch the Estimate delivery date. Required: SKU, drop_pincode.
- **Create a EasyEcom carrier reassignment** (Create). Note : At least one of reference_code or invoice_id must be provided. (EasyEcom V2.1: GET /Orders/reassignCarrier; docs: Shipment / Reassign Carrier.) Note: this GET changes data in EasyEcom. An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: company_carrier_id.
- **Create a EasyEcom carrier unassignment** (Create). It is used to Un-assigning the carrier. (EasyEcom V2.1: POST /Orders/unAssignCourier; docs: Shipment / Unassign Carrier.) Required: invoice_id.
- **List all EasyEcom channel statuses** (List). This API returns the list of marketplaces that have been integrated in the location, along with the status of the integrated marketplaces. The following information can be retrieved; Marketplace Name Marketplace ID Status = Active/Inactive. (EasyEcom V2.1: GET /current-channel-status; docs: Miscellaneous / Validate credentials of integrated marketplaces.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **List all EasyEcom child locations** (List). Locations are physical entities where stock is stored to fulfill orders. These could be your physical store, warehouse, or any other storage facility. You can use this API to fetch the details related to loaction. Authorization Bearer - jwt_token. (EasyEcom V2.1: GET /account/v1/api/locations; docs: Authorization.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **List all EasyEcom company attributes** (List). Returns the payment or delivery term names and code which will be useful in other API calls. (EasyEcom V2.1: GET /Maintenance/getCompanyAttributes; docs: Miscellaneous / Get Payment And DeliveryTerm Details.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: type.
- **List all EasyEcom company groups** (List). Returns the invoice or pricing group values and code which will be useful in other API calls. (EasyEcom V2.1: GET /Maintenance/getCompanyGroupDetails; docs: Miscellaneous / Get Company Group Details.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: type.
- **Create a EasyEcom consolidated inventory report** (Create). Consolidated Inventory Report. (EasyEcom V2.1: POST /inventory/ConsolidatedInventoryJob; docs: Reports / Consolidate Invenotry Report.)
- **List all EasyEcom countries** (List). It is used to get country details. (EasyEcom V2.1: GET /getCountries; docs: Miscellaneous / Get Countries.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **Create a EasyEcom credit note erp status** (Create). It is used to update the Sales ERP transaction ID (Invoice no. of ERP) in EasyEcom. ERP Status ID table:. (EasyEcom V2.1: POST /erp/update_credit_note_erp_status; docs: ERP And Reconcillation / Return order ERP order updation.) Values - erp_status / erp_status_id: not synced=1; error=2; synced=3; in progress=4 Items EasyEcom couldn't update are listed in `errors` (a partial success is still a success). Required: items.
- **List all EasyEcom custom fields** (List). It return the custom fields from account. Custom Field Type Table:-. (EasyEcom V2.1: GET /CustomFields/GetCustomFields; docs: Miscellaneous / Get Custom Fields.) Values - Type / Value: product=5; order=1; create order=2 An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: type.
- **Create a EasyEcom customer** (Create). It is used to create a Wholesale(B2B) customer in the account. (EasyEcom V2.1: POST /Wholesale/CreateCustomer; docs: Company and Locations / Create Customer Master.) Required: companyName, email, password, taxIdentificationNumber, country, billingStateId, billingPostalCode, currency, dispatchStateId.
- **List all EasyEcom customers** (List). It is used to get all customer details that are available in the account. (EasyEcom V2.1: GET /Wholesale/v2/UserManagement; docs: Company and Locations / Get Customers.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: type.
- **Update a EasyEcom customer by ID** (Update). It is used to update wholesale customer details and in response customer_id will be returned. (EasyEcom V2.1: POST /Wholesale/UpdateCustomer; docs: Company and Locations / Update Customer Master.) The id is EasyEcom's `customerId`; It is sent in the JSON body. Required: id.
- **Create a EasyEcom estimated delivery date** (Create). It is used to get Estimated delivery date. EasyEcom Internally calls carrier APIs to fetch the Estimate delivery date. This API is supported for Clickpost and Shiprocket carrier. (EasyEcom V2.1: POST /Carrier/predict-estimate-deliverydateV2; docs: Shipment / Estimated Delivery Date.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: SKU, drop_pincode.
- **List all EasyEcom grn statuses** (List). It is used to create an Auto GRN in EasyEcom. CheckGrnStatus:-. (EasyEcom V2.1: GET /wms/CheckGrnStatus; docs: Inventory / Auto Grn.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: queue_id.
- **List all EasyEcom grns** (List). It returns the created GRN along with details between the given date range. Note:- If none of the optional parameters are passed, by default last 7 days of GRN data will be received in the Response according to the GRN created date. GRN Status and ID table:- Get GRN Details API response Description: https://docs.google.com/spreadsheets/d/1WkiO38A_rsERsvXyXKeBi_ae8IGsDTwoDLzfCBr5CcA/edit?gid=175275610#gid=175275610. (EasyEcom V2.1: GET /Grn/V2/getGrnDetails; docs: Inventory / Get Grn Details.) Values - Status / ID: CREATED=1; QC Pending=2; QC Complete=3; Deleted=4 EasyEcom's nextUrl is followed page by page; limit = page size (up to 10, EasyEcom's default 5). An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **Create a EasyEcom grn** (Create). It is used to create an Auto GRN in EasyEcom. CheckGrnStatus:-. (EasyEcom V2.1: POST /wms/QueueGrnApi; docs: Inventory / Auto Grn.) Required: vendor_id, purchase_order_id.
- **Create a EasyEcom inventory** (Create). This API is used to update/overwrite the EasyEcom inventory one SKU at a time. Please note: This API only works for the Non-WMS plan . For updating the current Plan against your current location, Please reach out to us at care@easyecom.io The configuration for the Inventory Updates sent via the given API call can be configured from Account settings &gt;&gt; Other Settings&gt;&gt; Method to update inventory in the Manage inventory page. (EasyEcom V2.1: POST /inventory; docs: Inventory / Update Inventory.) Required: quantity.
- **List all EasyEcom inventory** (List). It is used to get inventory details. (EasyEcom V2.1: GET /getInventoryDetailsV3; docs: Inventory / Get Inventory Details.) EasyEcom's nextUrl is followed page by page; limit = page size (up to 20, EasyEcom's default 10). An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: includeLocations.
- **Create a EasyEcom inventory hold** (Create). The Given API is used to update Hold Inventory. The Hold qty will be deducted while the inventory is pushed to Marketplace channels. (EasyEcom V2.1: POST /holdUnHoldInventory; docs: Inventory / Bulk Hold Inventory Update.)
- **List all EasyEcom inventory serials** (List). It is used to fetch inventory along with the serial number if available. Inventory Status Table:-. (EasyEcom V2.1: GET /inventory/getInventorySerialsBySku; docs: Inventory / Get Inventory Serial By SKU.) Values - Inventory Status / Inventory Status ID: Available=1; Repair=2; Lost=3; Damaged=4; Gifted=5; Reserved=6; Sold=7; Questionable=8; Returned to Source=10; Return Available=11; QC Pending=12; QC Pass=13; QC Fail=14; Discard=16 An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: sku, status.
- **List all EasyEcom inventory snapshots** (List). It is used to get an Inventory Snapshot. (EasyEcom V2.1: GET /inventory/getInventorySnapshotApi; docs: Inventory / Get Inventory Snapshot.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: start_date, end_date.
- **Create a EasyEcom kit** (Create). It is used to create a Kit product, and the product ID will be generated in the successful response. (EasyEcom V2.1: POST /Products/CreateKittingProduct; docs: Product / Create Kitting Product.) Required: Sku.
- **List all EasyEcom kits** (List). It is used to get all Kit Products. (EasyEcom V2.1: GET /Products/getKits; docs: Product / Get Kit.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **List all EasyEcom listing imports** (List). It is used to import the listings for the selected marketplace/channel. (EasyEcom V2.1: GET /fetchListingGenericPriority; docs: Product / Import Listing.) Note: this GET changes data in EasyEcom. An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: marketplaceId.
- **Create a EasyEcom listing mapping** (Create). It is used to map the channel listings with the master SKU in EasyEcom. * Some of the identifiers for the marketplaces are given below *. (EasyEcom V2.1: POST /Products/mapListings; docs: Product / Map Listing.) Values - Marketplace / Identifier: Flipkart=FSN; Amazon=ASIN; Snapdeal=SUPC; Paytm=Paytm SKU Required: channelId, identifier, masterSku.
- **Create a EasyEcom listing** (Create). It is used to create listings in EasyEcom. (EasyEcom V2.1: POST /Products/createListings; docs: Product / Create Listing.) Required: marketplaceId, sku, listingRefNum, guid, mrp, identifier.
- **List all EasyEcom locations** (List). It is used to get all locations against the primary location. (EasyEcom V2.1: GET /getAllLocation; docs: Company and Locations / Get Locations.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **Create a EasyEcom manifest document** (Create). It is used to update the external manifest document against a specific manifest number. (EasyEcom V2.1: POST /manifest/update-document; docs: Shipment / Update Manifest Document.) Required: manifest_number, manifest_url.
- **Create a EasyEcom manifest** (Create). It is used to create Manifest. (EasyEcom V2.1: POST /Manifest/Generate; docs: Shipment / Generate Manifest.) Required: carrier_id, marketplace_id, awb_numbers.
- **Create a EasyEcom marketplace listing** (Create). This API is used to create the channel listings against any specific marketplace channel and map it against the master SKU. Please Note: Maximum number of supported listing values in a single API call: 20 Currently only supported for the given marketplaces: Flipkart Amazon Myntra PPMP Amazon Smart Connect. (EasyEcom V2.1: POST /Products/V2/createListings; docs: Product / Create Listing against Marketplace.)
- **EasyEcom marketplace listings search** (Search). Returns the Marketplace listings. If MasterSKu is not present, then the listing is not mapped to any master. Keep increasing the page number till it gives an empty array to get all the listings. Page size increment is not recommended. (EasyEcom V2.1: POST /Listings/getMarketPlaceListingV1; docs: Miscellaneous / Get MarketPlace Listing.) Pass pageNumber / pageSize in the body to page. An empty result can come back as HTTP 400 'No Data Found' (returned as 404). Required: marketPlaceID.
- **List all EasyEcom marketplaces** (List). It is used to get all marketplace list of Easyecom. (EasyEcom V2.1: GET /marketplaces/list; docs: Miscellaneous / Get Marketplace List.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- **Create a EasyEcom order address update** (Create). It is used to update billing and shipping address to pending and assigned order status. (EasyEcom V2.1: POST /orders/updateOrderAddress; docs: Order / Update order Address.) Required: order_id, shipping_pin_code.
- **Create a EasyEcom order cancel rename** (Create). This is for cancelling order and renaming it, in order to create a new order with same name as previous order. (EasyEcom V2.1: POST /orders/CancelOrders; docs: Order / Cancel and Rename Order.) Required: invoices, rename.
- **Create a EasyEcom order cancellation** (Create). It is used to cancel an order. The following parameters can be used to process the cancellation. (EasyEcom V2.1: POST /orders/cancelOrder; docs: Order / Cancel Order.) Required: reference_code, invoice_id, suborder_num, m_id.
- **Create a EasyEcom order confirmation** (Create). This API is used to confirm the order in Easyecom, and it returns the order ID or invoice ID in the successful response. The Invoice ID parameter is generally used when the order is a split order. In this case, the order ID is the same for the two different orders. So, in order to differentiate the split orders, the invoice ID is used. If the order is processed without splitting, orders can be confirmed using the "Order ID" parameter. (EasyEcom V2.1: POST /orders/confirm_order; docs: Order / Confirm Order.)
- **List all EasyEcom order counts** (List). It is used to get the order count in the given date range. (EasyEcom V2.1: GET /orders/getAllOrdersCount; docs: Order / Get Order Count.) An empty result can come back as HTTP 400 'No Data Found' (returned as 404).
- ...and 49 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
