> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/alasco.md).
# Alasco
Set up the Alasco connector in Pandium using your API key and API token so tenants can authenticate securely and sync construction financial data without extra provisioning.
## **Connector Overview**
Alasco is a construction financial management platform that helps project teams manage budgets, track expenses, and streamline financial workflows to ensure projects stay on track and on budget.
## **Authentication Type**
Basic
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_ALASCO\_API\_KEY
* PAN\_SEC\_ALASCO\_API\_TOKEN
## **API Client Supported**
No
## **Requirements for Provisioning**
No provisioning is required for this connector.
## **How to Connect Your Integration**
Upon successfully creating a tenant, you will use the following information to connect to Alasco:
* API Key
* API Token
To obtain the information required for connecting, perform the following steps:
1. Log into
## **API Resources**
For more information on how to utilize the Alasco API, feel free to reference the following [documentation](https://developer.alasco.de/).
---
# 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://docs.pandium.com/connectors/connectors-101/alasco.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.
