> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-skyslope.md).

# Integrating with SkySlope

Connect SkySlope to Drivetrain and sync real estate transaction data into models. Covers API credentials and authentication setup.

Drivetrain connects to SkySlope with four credentials: a Client ID and Client Secret, plus an Access Key and Secret Key. Your Drivetrain team sets up the connection with the values you share.

### Before you start <a href="#prerequisites" id="prerequisites"></a>

* An active SkySlope account.
* A SkySlope user with access to the data you want in Drivetrain (see the note below).

{% hint style="info" %}
The Access Key and Secret Key are generated per user and give the same access that user has in SkySlope. For example, an Agent's keys pull only that Agent's Listings and Sales. To pull every file in a brokerage, use the keys of a Broker or Admin who can see all files.
{% endhint %}

### SkySlope setup <a href="#skyslope-setup" id="skyslope-setup"></a>

#### Obtain Client ID and Client Secret <a href="#obtain-client-id-and-client-secret" id="obtain-client-id-and-client-secret"></a>

SkySlope's customer success team sends the Client ID and Client Secret during SkySlope onboarding, in a password-protected zip file. The password goes separately to your primary technical contact. Ask your SkySlope customer success manager if you don't have them.

#### Obtain Access Key and Secret Key <a href="#obtain-access-key-and-secret" id="obtain-access-key-and-secret"></a>

1. Log in to SkySlope and select **My Account** under your profile icon.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-53ce21d7abcf2839315dcf77a7d53b151a80f933%2Fskyslope1.png?alt=media" alt=""><figcaption></figcaption></figure>

2. On the **Integrations** tab, click **Generate New Key**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-0b26e79e241a7b971b73f42813ccb14ed9cbdc79%2Fskyslope2.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you don't see **Generate New Key**, you're probably on your brokerage's Integrations tab in the Admin section. Open **My Account** from the SkySlope menu icon instead.
{% endhint %}

3. Copy or download the Access Key and Secret Key and store them securely. SkySlope won't show them again.

{% hint style="info" %}
Share these four values with your customer success manager through a secure channel:

1. Client ID
2. Client Secret
3. Access Key
4. Secret Key
   {% endhint %}

### What data comes in

Contacts, users, offices, listings and sales, by default from January 1, 2010. Contacts, users and offices reload in full on each sync. Listings sync changes since the last sync, and sales sync newly created sales.


---

# 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://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-skyslope.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.
