> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/daton/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/woocommerce-api-keys.md). # How to find site-id/domain and create WooCommerce Consumer Key and Secret Documentation on finding the site-id/domain and creating consumer key and consumer secret for successful integration of WooCommerce Follow the below instructions to get required information * Sign in to your WordPress account * To get the site id for your website, **For WordPress hosted sites:** * Click the arrow mark under **My Sites** in left corner. Note the **WordPress site id** under the **WordPress site name**

**For self hosted websites:** * Go to **Store Management** section after logging to WooCommerce plugin and note down the **Domain** name * On the navigation menu, select **WooCommerce** and then click **Settings** * In **Advanced** tab, select **REST API** section and click **Add key** button

* Provide **Description** and select a **User** with **Read** permission * Click on **Generate API key**

* Note down the **Consumer key** and **Consumer secret** which will be asked during integration

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/woocommerce-api-keys.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.