syncing market data_
Public API imported from APIs.guru (cloud-elements.com:ecwid)
Public API proxied through Ozma. Discover and call via one Ozma key. --- Public API proxied through Ozma. **Claim this listing** to monetize and manage pricing.
No score data yet
| Method | Path | Summary | Price |
|---|---|---|---|
| POST | /bulk/download | Create a new bulk download job (asynchronous) | 1c |
| GET | /bulk/jobs | Fetch all the bulk jobs for an instance | 1c |
| POST | /bulk/query | Create an asynchronous bulk query job. | 1c |
| PUT | /bulk/{id}/cancel | Cancel an asynchronous bulk query job. | 1c |
| GET | /bulk/{id}/errors | Retrieve the errors of a bulk job. | 1c |
| GET | /bulk/{id}/status | Retrieve the status of a bulk job. | 1c |
| GET | /bulk/{id}/{objectName} | Retrieve the results of an asynchronous bulk query. | 1c |
| POST | /bulk/{objectName} | Upload a file of objects to be bulk uploaded to the provider. | 1c |
| GET | /customers | Find customers in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrieved | 1c |
| POST | /customers | 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 customer | 1c |
| DELETE | /customers/{id} | 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 message | 1c |
| GET | /customers/{id} | 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 response | 1c |
| PATCH | /customers/{id} | 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 response | 1c |
| GET | /customers/{id}/orders | 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 returned | 1c |
| GET | /objects | Get a list of all the available objects. | 1c |
| GET | /objects/{objectName}/docs | Get swagger docs for an object. | 1c |
| GET | /objects/{objectName}/metadata | Get a list of all the field for an object. | 1c |
| GET | /orders | Find orders in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrieved | 1c |
| POST | /orders | 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_PROCESSING | 1c |
| DELETE | /orders/{id} | 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 message | 1c |
| GET | /orders/{id} | 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 response | 1c |
| PATCH | /orders/{id} | 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> | 1c |
| GET | /orders/{orderId}/payments | Retrieve the payments in the eCommerce system for the specified order | 1c |
| GET | /orders/{orderId}/refunds | Retrieve the refunds in the eCommerce system for the specified order | 1c |
| GET | /ping | Ping the Element to confirm that the Hub Element has a heartbeat. If the Element does not have a heartbeat, an error message will be returned. | 1c |
| GET | /products | 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 retrieved | 1c |
| POST | /products | 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 product | 1c |
| DELETE | /products/{id} | 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 message | 1c |
| GET | /products/{id} | 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 response | 1c |
| PATCH | /products/{id} | Update a product associated with a given ID in the eCommerce system. The update API uses the PATCH HTTP verb, so only those fields provided in the product object will be updated, and those fields not provided will be left alone. Updating a product with a specified ID that does not exist will result in an error response. <p><strong>Update supports the following fields: sku, quantity, trackQuantity, quantityDelta, warningLimit, name, price, weight, tangible, enabled, fixedShippingRateOnly, fixedShippingRate, description, wholesalePrices, compareAtPrice, productClassId</strong> | 1c |
| GET | /{objectName} | Search for {objectName} | 1c |
| POST | /{objectName} | Create an {objectName} | 1c |
| DELETE | /{objectName}/{objectId} | Delete an {objectName} | 1c |
| GET | /{objectName}/{objectId} | Retrieve an {objectName} | 1c |
| PATCH | /{objectName}/{objectId} | Update an {objectName} | 1c |
| PUT | /{objectName}/{objectId} | Update an {objectName} | 1c |
| GET | /{objectName}/{objectId}/{childObjectName} | Search for {childObjectName} | 1c |
| POST | /{objectName}/{objectId}/{childObjectName} | Create an {objectName} | 1c |
| DELETE | /{objectName}/{objectId}/{childObjectName}/{childObjectId} | Delete an {childObjectName} | 1c |
| GET | /{objectName}/{objectId}/{childObjectName}/{childObjectId} | Retrieve an {childObjectName} | 1c |
| PATCH | /{objectName}/{objectId}/{childObjectName}/{childObjectId} | Update an {childObjectName} | 1c |
| PUT | /{objectName}/{objectId}/{childObjectName}/{childObjectId} | Update an {childObjectName} | 1c |
ozma register && ozma call ecwid /bulk/download --jsoncurl -H "Authorization: Bearer $OZMA_KEY" \
https://gateway.ozma.app/v1/proxy/ecwid/bulk/download# Python
client.proxy_call("ecwid", "/bulk/download")Own this API? Claim the listing to manage pricing and receive payouts.