> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/olo-integration-setup.md).

# Olo Integration Setup

To setup your [Olo integration with Solink](/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/olo-integration-overview.md), a **Brand Administrator** will need access to the **Developer Portal** on your [**Olo Dashboard**](https://my.olo.com/All/Account/LogOn).

**Note**: If you cannot access Developer Tools, please work with your corporate team or help desk to configure the Webhook.

Follow the steps below to get started:

1. Login to your Olo Dashboard.
2. Navigate to **Developer Tools** > select **Add Webhook**.

![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-4558c75175a63ab9d090ba533cbad3b2b2aaa893%2F0820c0a8868adcc3.png?alt=media)

3. Enter the following information:
   1. **Webhook Name**: Solink Webhook
   2. **Destination URL**: [https://integrations.solinkcloud.com/olo/webhook/*customer-id-from-manage*](https://integrations.solinkcloud.com/olo/webhook/customer-id-from-manage)(Your Solink Customer Success representative should provide you with the correct URL - each user will have unique text for the "customer-id-from-manage" part of the URL)
   3. **Developer Partner**: Solink
4. Toggle "**on**" the following **Order Events**:

   1. OrderAdjusted
   2. OrderCancelled
   3. OrderClosed
   4. OrderPlaced
   5. OrderPickedUp
   6. DispatchStatusUpdate

   ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-f0019b2c8b04731fac9ea029e5d888c9c7c2a286%2Fba6662559810ac33.png?alt=media)
5. Once you are ready to publish, select **Test Webhook**. This will bring up the **Shared Secret** which **can only be retrieved at this step**.
6. Copy the **Shared Secret** and provide it to Solink so they can recognize the webhook as coming from Olo:

![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-f75f6002d5bed40e1401b1a39a9497ca9b38f004%2F75352455b149a950.png?alt=media)

7. Once Solink has confirmed they have stored the shared secret, select the **Test Webhook** button. If the test succeeds, select **Publish Webhook** to complete the process.

If you run into any errors while completing these steps, please reach out to your Solink Customer Success representative.


---

# 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://help.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/olo-integration-setup.md?ask=<question>&goal=<user_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.