> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/patchworks-services/service-systems/supported-service-systems/veeqo/finding-service-connector-credentials-for-veeqo.md).

# Finding service connector credentials for Veeqo

## Required credentials

To [add a Patchworks connector](/product-documentation/patchworks-services/service-connectors/adding-a-service-connector.md) for **Veeqo**, the following details are required for authentication:

<table><thead><tr><th>Credential</th><th data-type="checkbox">Required</th><th>Note</th></tr></thead><tbody><tr><td><a href="#token">Token</a></td><td>true</td><td>Available from employee records in Veeqo. </td></tr></tbody></table>

## Obtaining credentials

The credentials listed above are needed so that Patchworks can access the required data in **Veeqo**. To obtain these details, follow the steps below.

### Token

**Step 1**\
Log in to your [Veeqo account](https://app.veeqo.com/login).

**Step 2**\
Navigate to the **employees** page.

**Step 3**\
Click on the required user or - if required - create a **+ new employee**.

{% hint style="info" %}
If you have multiple users, Veeqo recommends creating a **new employee** for each user as this makes the tracking of application activity much easier.&#x20;
{% endhint %}

**Step 4**\
Click **refresh API key**.

**Step 5**\
An API key is generated - this key is stored in Veeqo but we advise adding it to your password manager, ready for use in your Patchworks setup.&#x20;

{% hint style="warning" %}
Treat your API Key like any other password - do not share it with others as anyone who has access to your API Key has full API access to your Veeqo account.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/patchworks-services/service-systems/supported-service-systems/veeqo/finding-service-connector-credentials-for-veeqo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.