{"files":{"SKILL.md":"---\nname: ecommerce-api\ndescription: \"Ecommerce API skill. Use when working with Ecommerce for ecommerce. Covers 7 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Ecommerce API\nAPI version: 10.24.12\n\n## Auth\nApiKey Authorization in header\n\n## Base URL\nhttps://unify.apideck.com\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /ecommerce/orders -- list orders\n3. Explore available endpoints below\n\n## Endpoints\n7 endpoints across 1 group. See references/api-spec.lap for full details.\n\n### Ecommerce\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /ecommerce/orders | List Orders |\n| GET | /ecommerce/orders/{id} | Get Order |\n| GET | /ecommerce/products | List Products |\n| GET | /ecommerce/products/{id} | Get Product |\n| GET | /ecommerce/customers | List Customers |\n| GET | /ecommerce/customers/{id} | Get Customer |\n| GET | /ecommerce/store | Get Store |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all orders?\" -> GET /ecommerce/orders\n- \"Get order details?\" -> GET /ecommerce/orders/{id}\n- \"List all products?\" -> GET /ecommerce/products\n- \"Get product details?\" -> GET /ecommerce/products/{id}\n- \"List all customers?\" -> GET /ecommerce/customers\n- \"Get customer details?\" -> GET /ecommerce/customers/{id}\n- \"List all store?\" -> GET /ecommerce/store\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Paginated endpoints accept limit/offset or cursor parameters\n- Error responses include status codes and descriptions in the spec\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Ecommerce API\n@base https://unify.apideck.com\n@version 10.24.10\n@auth ApiKey Authorization in header\n@common_fields {x-apideck-consumer-id: str # ID of the consumer which you want to get or push data from, x-apideck-app-id: str # The ID of your Unify application, raw: bool=false # Include raw response. Mostly used for debugging purposes, x-apideck-service-id: str # Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API., fields: str # The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city`In the example above, the response will only include the fields \"name\", \"email\" and \"addresses.city\". If any other fields are available, they will be excluded.}\n@endpoints 7\n@toc ecommerce(7)\n\n@endpoint GET /ecommerce/orders\n@desc List Orders\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20, filter: map # Apply filters, sort: map # Apply sorting, pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Orders\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/orders/{id}\n@desc Get Order\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, order_number: str?, currency: str?, discounts: [map], sub_total: str?, shipping_cost: str?, coupon_discount: str?, total_discount: str?, total_tax: str?, total_amount: str?, refunded_amount: str?, status: str?, payment_status: str?, fulfillment_status: str?, payment_method: str?, customer: map{id: str?, name: str?, first_name: str?, last_name: str?, company_name: str?, phone_numbers: [map]?, emails: [map]?}, billing_address: map{line1: str?, line2: str?, company_name: str?, city: str?, state: str?, postal_code: str?, country: str?}, shipping_address: map{line1: str?, line2: str?, company_name: str?, city: str?, state: str?, postal_code: str?, country: str?}, tracking: [map], line_items: [map], note: str?, refunds: [map], custom_mappings: map?, created_at: str(date-time)?, updated_at: str(date-time)?}, _raw: map?} # Orders\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/products\n@desc List Products\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20, pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads, filter: map # Apply filters}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Products\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/products/{id}\n@desc Get Product\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, name: str?, description: str?, status: str?, price: str?, sku: str?, inventory_quantity: str?, images: [map]?, weight: str?, weight_unit: str?, options: [map], variants: [map], tags: [str], categories: [map], custom_mappings: map?, created_at: str(date-time)?, updated_at: str(date-time)?}, _raw: map?} # Products\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/customers\n@desc List Customers\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20, filter: map # Apply filters, pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Customers\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/customers/{id}\n@desc Get Customer\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, name: str?, first_name: str?, last_name: str?, company_name: str?, status: str?, currency: str?, emails: [map]?, phone_numbers: [map]?, addresses: [map], orders: [map], custom_mappings: map?, created_at: str(date-time)?, updated_at: str(date-time)?}, _raw: map?} # Customers\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ecommerce/store\n@desc Get Store\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, name: str?, store_url: str(uri)?, admin_url: str(uri)?, custom_mappings: map?, created_at: str(date-time)?, updated_at: str(date-time)?}, _raw: map?} # Stores\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@end\n"}}