ecwid

32 actions

Create a new customer in eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Customer' model are those required to create a new customerPOSTv1.0.0
Create a new product in eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Product' model are those required to create a new productPOSTv1.0.0
Create an {objectName}POSTv1.0.0
Create an {objectName}POSTv1.0.0
Create an order in the eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Order' model are those required to create a new order.The paymentStatus can only be AWAITING_PAYMENT or INCOMPLETE.The fulfillmentStatus can only be AWAITING_PROCESSINGPOSTv1.0.0
Delete a customer associated with a given ID from your eCommerce system. Specifying a customer associated with a given ID that does not exist will result in an error messageDELETEv1.0.0
Delete a product associated with a given ID from your eCommerce system. Specifying a product associated with a given ID that does not exist will result in an error messageDELETEv1.0.0
Delete an {childObjectName}DELETEv1.0.0
Delete an {objectName}DELETEv1.0.0
Delete an order associated with a given ID from your eCommerce system. Specifying an order associated with a given ID that does not exist will result in an error messageDELETEv1.0.0
Find customers in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrievedGETv1.0.0
Find orders in the customer associated with a given ID. If the customer does not exist, an error response will be returned. If no orders are found in the given customer then an empty array will be returnedGETv1.0.0
Find orders in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrievedGETv1.0.0
Find products in the eCommerce system, using the provided CEQL search expression. The search expression in CEQL is the WHERE clause in a typical SQL query, but without the WHERE keyword. If no search expression is provided, all records will be retrievedGETv1.0.0
Get a list of all the available objects.GETv1.0.0
Get a list of all the field for an object.GETv1.0.0
Get swagger docs for an object.GETv1.0.0
Retrieve a customer associated with a given ID from the eCommerce system. Specifying a customer with an ID that does not exist will result in an error responseGETv1.0.0
Retrieve a product associated with a given ID from the eCommerce system. Specifying a product with an ID that does not exist will result in an error responseGETv1.0.0
Retrieve an {childObjectName}GETv1.0.0
Retrieve an {objectName}GETv1.0.0
Retrieve an order associated with a given ID from the eCommerce system. Specifying an order with an ID that does not exist will result in an error responseGETv1.0.0
Retrieve the payments in the eCommerce system for the specified orderGETv1.0.0
Retrieve the refunds in the eCommerce system for the specified orderGETv1.0.0
Search for {childObjectName}GETv1.0.0
Search for {objectName}GETv1.0.0
Update an {childObjectName}PUTv1.0.0
Update an {childObjectName}PATCHv1.0.0
Update an {objectName}PUTv1.0.0
Update an {objectName}PATCHv1.0.0
Update an customer associated with a given ID in the eCommerce system.The update API uses the PATCH HTTP verb, so only those fields provided in the customer object will be updated, and those fields not provided will be left alone. Updating a customer with a specified ID that does not exist will result in an error responsePATCHv1.0.0
Update an order associated with a given ID in the eCommerce system. The update API uses the PATCH HTTP verb, so only those fields provided in the order object will be updated, and those fields not provided will be left alone. Updating an order with a specified ID that does not exist will result in an error response</strong>PATCHv1.0.0

E-commerce/ecwid

Update an order associated with a given ID in the eCommerce system. The update API uses the PATCH HTTP verb, so only those fields provided in the order object will be updated, and those fields not provided will be left alone. Updating an order with a specified ID that does not exist will result in an error response</strong>

v1.0.0

Input

{
  "type": "object",
  "properties": {
    "action": {
      "type": "string"
    },
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Output

{
  "type": "object",
  "additionalProperties": true
}