# Landing page

This guide is designed for web developers who are integrating a real estate development project website with Realpad CRM in two specific areas:

* [**Fetching pricelist data**](/integrations/landing-page/fetching-pricelist-data.md) (units, their prices, and status, links to their floorplans, ...).
* [**Sending leads**](/integrations/landing-page/sending-leads.md) from the contact form (name, surname, email, phone, additional info).

Two currently experimental areas are:

* [**Updating pricelist data**](/integrations/landing-page/updating-pricelist-data.md) (set price for one or more units).
* [**Uploading project media**](/integrations/landing-page/uploading-project-media.md) (floorplans, gallery photos, ...).

## OpenAPI specification

Lives [here](https://openapi.gitbook.com/o/UuR2VSBNcvrkwmPVWwiM/spec/realpad-api-landing-page.yaml).

## Top-level summary

1. To do this integration obtain login credentials for your account from the tenant administrators. You'll typically receive one pair of credentials per project - one for fetching pricelist, one for sending leads.
   * *Example: for **My New Project** you'd receive*
   * `my-new-project-pricelist / some_password`
   * `my-new-project-leads / some_other_password`
2. Write **backend** code that will invoke an HTTP POST request to the endpoints mentioned below and process the API response appropriately.
3. Test the whole solution together with our support team on a **test environment of the project website**.
4. After a **3-way confirmation** that all is running correctly deploy the solution to the **production website**.

{% @mailchimp/mailchimpSubscribe cta="Sign up to receive updates!" %}


---

# Agent Instructions: 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:

```
GET https://dev.realpadsoftware.com/integrations/landing-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.