{"note":"OpenAPI conversion -- returning structured metadata","name":"cloud-elements-com-ecwid","description":"ecwid","version":"api-v2","base_url":"https://api.cloud-elements.com/elements/api-v2","endpoints":42,"raw":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api ecwid\n@base https://api.cloud-elements.com/elements/api-v2\n@version api-v2\n@auth ApiKey Authorization in header\n@common_fields {Authorization: any # The authorization tokens. The format for the header value is 'Element , User '}\n@endpoints 42\n@hint download_for_search\n@toc bulk(8), customers(6), objects(3), orders(7), ping(1), products(5), {objectName}(12)\n\n@group bulk\n@endpoint POST /bulk/download\n@desc Create a new bulk download job (asynchronous)\n@required {body: map # The object body}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /bulk/jobs\n@desc Fetch all the bulk jobs for an instance\n@optional {where: any # The CEQL search expression, or the where clause, without the WHERE keyword, in a typical SQL query. For example to get all upload jobs the expression would be where=job_direction='UPLOAD'. The following fields are valid search fields 'object_name', 'job_status', 'job_direction', 'record_count', nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, pageSize: any # The page size for pagination, which defaults to 200 if not supplied, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint POST /bulk/query\n@desc Create an asynchronous bulk query job.\n@optional {Elements-Async-Callback-Url: any # The Url to send the notification to when the Job is completed, q: any # The CEQL query. When this parameter is omitted, all objects of the given type are returned via the bulk job. Endpoint limiters may still apply., lastRunDate: any # The last time this query was run. This is optional. You can also have this parameter in the query and leave this blank - optional eg. '2014-10-06T13:22:17-08:00', from: any # The created/updated date of the object to filter on - optional eg. '2014-10-06T13:22:17-08:00', to: any # The created/updated date of the object to filter on - optional eg. '2014-10-06T13:22:17-08:00', metaData: any # Optional JSON MetaData that contains callback-payload and fileName, ex: {\"callback-payload\" :  , \"fileName\" : \"{Date format}_Name of the file\"}. If the fileName is MyFile then pass metadata as {\"fileName\" : \"{yyyy-MM-dd HH:mm:ss}_MyFile\"}. The valid date formats are \"yyyy-MM-dd'T'HH:mm:ssXXX\", \"yyyy-MM-dd'T'HH:mm:ss'Z'\", \"yyyy-MM-dd'T'HH:mm:ss.SXXX\", \"yyyy-MM-dd'T'HH:mm:ss.SSSXXX\", \"yyyy-MM-dd'T'HH:mm:ss.SSSZ\", \"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'\", \"yyyy-MM-dd HH:mm:ss\", \"yyyy.MM.dd G 'at' HH:mm:ss z\", \"h:mm a\", \"yyyyy.MMMMM.dd GGG hh:mm aaa\" and \"yyMMddHHmmssZ\". callback-payload - is passed back in bulk job notification}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PUT /bulk/{id}/cancel\n@desc Cancel an asynchronous bulk query job.\n@required {id: any # The ID of the bulk job to cancel.}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /bulk/{id}/errors\n@desc Retrieve the errors of a bulk job.\n@required {id: any # The ID of the bulk job to retrieve its errors.}\n@optional {pageSize: any # The page size for pagination, which defaults to 200 if not supplied, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /bulk/{id}/status\n@desc Retrieve the status of a bulk job.\n@required {id: any # The ID of the bulk job to retrieve its status.}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /bulk/{id}/{objectName}\n@desc Retrieve the results of an asynchronous bulk query.\n@required {id: any # The ID of the bulk job, objectName: any # The name of the object}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint POST /bulk/{objectName}\n@desc Upload a file of objects to be bulk uploaded to the provider.\n@required {objectName: any # The name of the object for which data needs to be uploaded.}\n@optional {Elements-Async-Callback-Url: any # The Url to send the notification to when the Job is completed, metaData: any # Optional JSON MetaData that contains callback-payload, path or format, ex: {\"path\" :, \"format\": , \"callback-payload\":}. path - is passed to the endpoint for bulk loading the data into a nested object. Optional JSON Metadata that contains identifierFieldName, action, listId or campaignId. The identifierField name is used for upserts and the optional fields like listId or campaignId. Example: {\"listId\":\"1014\",\"action\":\"upsert\"}. If the Upload format is JSON pass metadata as {\"format\":\"json\"}. callback-payload - is passed back in bulk job notification, file: any # The file of objects to bulk load. If the JSON file upload, each JSON record should be in a single line}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group customers\n@endpoint POST /customers\n@desc 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\n@required {customer: map # The customer object to be created}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /customers\n@desc Find customers in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrieved\n@optional {where: any # The CEQL search expression, or the where clause, without the WHERE keyword, in a typical SQL query (i.e. field='value'). Supported search terms: customer_id and customer_email. All other search criteria are ignored. NOTE: When searching by customer_id, do not quote the value (ex: customer_id=15693430), as the ID is a number rather than a string.  When searching by email, quote the value (ex: customer_email='a@b.c'), as the email parameter is a string, pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PATCH /customers/{id}\n@desc 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\n@required {id: any # The ID of the customer to update in the eCommerce system, customer: map # The customer object to be created}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /customers/{id}\n@desc 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\n@required {id: any # The ID of the customer to retrieve from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint DELETE /customers/{id}\n@desc 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\n@required {id: any # The ID of the customer to delete from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /customers/{id}/orders\n@desc 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\n@required {id: any # The ID of the customer to get orders form in the eCommerce system}\n@optional {pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group objects\n@endpoint GET /objects\n@desc Get a list of all the available objects.\n@optional {Elements-Version: any # Elements Version to be used for getting metadata, possible options are Hydrogen, Helium. Default value is Hydrogen}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /objects/{objectName}/docs\n@desc Get swagger docs for an object.\n@required {objectName: any # The name of the object}\n@optional {discovery: any # Include discovery metadata in definitions, resolveReferences: any # Optionally resolve swagger references for an inline object definition, basic: any # Include only OpenAPI / Swagger properties in definitions, version: any # The element swagger version to get the corresponding element swagger, Passing in \"-1\" gives latest element swagger}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /objects/{objectName}/metadata\n@desc Get a list of all the fields for an object.\n@required {objectName: any # The name of the object}\n@optional {Elements-Version: any # Elements Version to be used for getting metadata, possible options are Hydrogen, Helium. Default value is Hydrogen}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group orders\n@endpoint POST /orders\n@desc 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\n@required {order: map # The order object to be created}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /orders\n@desc Find orders in the eCommerce system, using the provided CEQL search expression. If no search expression is provided, all records will be retrieved\n@optional {where: any # The CEQL search expression, or the where clause, without the WHERE keyword, in a typical SQL query (i.e. field='value'). Supported search terms: date, from_date, to_date, from_update_date, to_update_date, order, from_order, to_order, customer_id, customer_email and statuses. All other search criteria are ignored, pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PATCH /orders/{id}\n@desc 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\n@required {id: any # The ID of the order to update in the eCommerce system, order: map # The order object, with those fields that are to be updated}\n@optional {action: any # An action to perform on the order: cancel, reopen or close. If left blank then the order is updated but no action is taken}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /orders/{id}\n@desc 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\n@required {id: any # The ID of the order to retrieve from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint DELETE /orders/{id}\n@desc 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\n@required {id: any # The ID of the order to delete from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /orders/{orderId}/payments\n@desc Retrieve the payments in the eCommerce system for the specified order\n@required {orderId: any # The ID of the order to retrieve payments from in the eCommerce system}\n@optional {pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /orders/{orderId}/refunds\n@desc Retrieve the refunds in the eCommerce system for the specified order\n@required {orderId: any # The ID of the order to retrieve refunds from in the eCommerce system}\n@optional {pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group ping\n@endpoint GET /ping\n@desc 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.\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group products\n@endpoint POST /products\n@desc 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\n@required {product: map # The product object to be created}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /products\n@desc 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\n@optional {where: any # The CEQL search expression, or the where clause, without the WHERE keyword, in a typical SQL query (i.e. field='value'). Supported search terms: category, hidden_products. All other search criteria are ignored, pageSize: any # The number of results to fetch in a given page. When this parameter is omitted, a maximum of 200 results are returned, nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PATCH /products/{id}\n@desc 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. Update supports the following fields: sku, quantity, trackQuantity, quantityDelta, warningLimit, name, price, weight, tangible, enabled, fixedShippingRateOnly, fixedShippingRate, description, wholesalePrices, compareAtPrice, productClassId\n@required {id: any # The ID of the product to update in the eCommerce system, product: map # The product object, with those fields that are to be updated}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /products/{id}\n@desc 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\n@required {id: any # The ID of the product to retrieve from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint DELETE /products/{id}\n@desc 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\n@required {id: any # The ID of the product to delete from the eCommerce system}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@group {objectName}\n@endpoint GET /{objectName}\n@desc Search for {objectName}\n@required {objectName: any # The name of the object}\n@optional {where: any # The CEQL search expression., pageSize: any # The page size. Defaults to 200 if not provided. Maximum of 5000., nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint POST /{objectName}\n@desc Create an {objectName}\n@required {objectName: any # The name of the object, Body: map # The {objectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint DELETE /{objectName}/{objectId}\n@desc Delete an {objectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /{objectName}/{objectId}\n@desc Retrieve an {objectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PATCH /{objectName}/{objectId}\n@desc Update an {objectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID, Body: map # The {objectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PUT /{objectName}/{objectId}\n@desc Update an {objectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID, Body: map # The {objectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the 'Accept' header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /{objectName}/{objectId}/{childObjectName}\n@desc Search for {childObjectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID, childObjectName: any # The name of the childObjectName}\n@optional {where: any # The CEQL search expression., pageSize: any # The page size. Defaults to 200 if not provided. Maximum of 5000., nextPage: any # The next page cursor, taken from the response header: `elements-next-page-token`, fields: any # The fields to return on the response. Can be a single field or a comma-separated list of fields}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint POST /{objectName}/{objectId}/{childObjectName}\n@desc Create an {objectName}\n@required {objectName: any # The name of the object, objectId: any # The {objectName} ID, childObjectName: any # The name of the object, Body: map # The {childObjectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint DELETE /{objectName}/{objectId}/{childObjectName}/{childObjectId}\n@desc Delete an {childObjectName}\n@required {objectName: any # The name of the object, childObjectName: any # The name of the childObjectName, objectId: any # The {objectName} ID, childObjectId: any # The {childObjectName} ID}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint GET /{objectName}/{objectId}/{childObjectName}/{childObjectId}\n@desc Retrieve an {childObjectName}\n@required {objectName: any # The name of the object, childObjectName: any # The name of the childObjectName, objectId: any # The {objectName} ID, childObjectId: any # The {childObjectName} ID}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PATCH /{objectName}/{objectId}/{childObjectName}/{childObjectId}\n@desc Update an {childObjectName}\n@required {objectName: any # The name of the object, childObjectName: any # The name of the childObjectName, objectId: any # The {objectName} ID, childObjectId: any # The {childObjectName} ID, Body: map # The {objectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endpoint PUT /{objectName}/{objectId}/{childObjectName}/{childObjectId}\n@desc Update an {childObjectName}\n@required {objectName: any # The name of the object, childObjectName: any # The name of the childObjectName, objectId: any # The {objectName} ID, childObjectId: any # The {childObjectName} ID, Body: map # The {objectName}}\n@returns(200) OK - Everything worked as expected\n@errors {400: Bad Request - Often due to a missing request parameter, 401: Unauthorized - An invalid element token, user secret and/or org secret provided, 403: Forbidden - Access to the resource by the provider is forbidden, 404: Not found - The requested resource is not found, 405: Method not allowed - Incorrect HTTP verb used, e.g., GET used when POST expected, 406: Not acceptable - The response content type does not match the \"Accept\" header value, 409: Conflict - If a resource being created already exists, 415: Unsupported media type - The server cannot handle the requested Content-Type, 500: Server error - Something went wrong on the Cloud Elements server, 502: Provider server error - Something went wrong on the Provider or Endpoint's server}\n\n@endgroup\n\n@end\n"}