# Introduction

Welcome to the Realpad Product Updates hub! Here, you’ll find all the latest updates, improvements, and new features that we’re rolling out to enhance your Realpad experience. Stay informed and get the most out of Realpad with our comprehensive update notes and release information.

## Discover Product Updates

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Monthly Updates</strong></td><td align="center">Monthly summaries of the latest changes and improvements</td><td></td><td><a href="/files/pvGex6e4nJuSmmrlN7QM">/files/pvGex6e4nJuSmmrlN7QM</a></td><td><a href="/pages/A3JXDKfhOQpGf0PL8BT7">/pages/A3JXDKfhOQpGf0PL8BT7</a></td></tr><tr><td align="center"><strong>Releases</strong></td><td align="center">Detailed information on our latest product releases</td><td></td><td><a href="/files/3KFYSTewWssuuFXxEGRM">/files/3KFYSTewWssuuFXxEGRM</a></td><td><a href="/pages/Tf0DGMLrbBybNHIDsGp3">/pages/Tf0DGMLrbBybNHIDsGp3</a></td></tr><tr><td align="center"><strong>API Documentation</strong></td><td align="center">Guides and documentation for API integrations</td><td></td><td><a href="/files/o9aSkRXlo0gEaJ8mqIJ8">/files/o9aSkRXlo0gEaJ8mqIJ8</a></td><td><a href="/spaces/MOqd16Sk9Ap8eTNLWqTG/pages/edU6Imo8vlFriwbh7eY4">/spaces/MOqd16Sk9Ap8eTNLWqTG/pages/edU6Imo8vlFriwbh7eY4</a></td></tr></tbody></table>

## What are we currently working on? <a href="#what-are-we-currently-working-on" id="what-are-we-currently-working-on"></a>

<details>

<summary><strong>Simplified and faster UX of the Deals section</strong></summary>

**Our goal:** Transform Deal section from a tab-heavy, navigation-intensive interface into a clear, action-oriented control center.

* **Today:** Completing core tasks - preparing contracts, creating payment schedules, adding customers and discounts - requires excessive navigation. Users jump between tabs, struggle to locate actions, and waste time on repetitive clicking - or even make mistakes.
* **Future:** Deal is understandable and overviewable. The most common tasks on a deal are clear and follow actual business procedures and flows. Users (Sales agents, lawyers, accountants) complete tasks in fewer clicks with clear context and predictable outcomes.

</details>

<details>

<summary><strong>New REST APIs</strong></summary>

We are aware of a wide range of problems with our current set of API endpoints, and we are designing the next generation of our APIs.

#### Suboptimal architecture

Our endpoints are oriented around particular use cases; their naming implies specific actions and intents. For example, [`get-all-projects`](https://dev.realpadsoftware.com/integrations/landing-page/fetching-pricelist-data) retrieves detailed price list information for all the projects, in an atomic way suitable for loading a mobile application that should then be able to work offline.

Endpoints reading from or writing to many different entities, and opaquely handling rich business logic, such as [`create-lead`](https://dev.realpadsoftware.com/integrations/landing-page/sending-leads), are the norm at the moment.

A vast majority of the entities in our CRM are not exposed to any external manipulation.

The design of the endpoints for retrieving the price list information and [Takeout](https://dev.realpadsoftware.com/integrations/data-takeout) data makes it hard to achieve the expected performance. Lacking a good automated rate-limiting mechanism, we are discovering troublesome clients and have to negotiate with them only retrospectively.

Our plans for the next generation are to build the endpoints around entities in a RESTful manner, and include means for the integrations to be notified of changes to the relevant entities (change the pull model to push). Access to full entities in a paginated manner, including bulk operations, is also planned.

#### Problematic authentication model

To use our existing endpoints, a login & password of a CRM user with particular permissions need to be passed as parameters in the request. The user experience of setting this up is very poor, with little to no self-service available to our clients and their integrators.

We are looking at options like API tokens, OAuth, and others for the next generation of APIs. We are considering providing a self-service playground for our integrators to build and test their solutions.

#### Input and output formats

Our typical endpoint expects a `multipart/form-data` POST request. The output types range from XML (the oldest, but also very widely used), through JSON for certain endpoints, through plaintext for endpoints that create and modify records, all the way to Excel files in the [Takeout API](https://dev.realpadsoftware.com/integrations/data-takeout) range.

Most use cases needing to read data from the CRM are forced to use the Takeout API and parse Excel files, having to deal with configurable (and thus unstable) columns.

Our goal is to settle on JSON on the input and output side for the vast majority of the future endpoints.

#### Documentation

While [public documentation](https://dev.realpadsoftware.com/) is available, and a subset of our API integrators is subscribed to a technical newsletter, the current situation leaves much to be desired compared to the state of the art. Considering the fact that our clients are typically non-technical, we recognize the need to be in a dialog with them and their integrators when it comes to evolving the APIs, especially when it comes to breaking changes. This is currently hard to achieve due to a combination of product and organizational factors.

We expect to build the next set of endpoints in a way that makes it extremely easy to build solutions integrating with our APIs. We look to the best practices of companies like MailChimp and Stripe for inspiration in documentation, status pages, incident management, etc.

</details>

<details>

<summary><strong>Automated invoicing (Integration with ERP)</strong></summary>

**Problem**: After sales person signs a deal, and creates a payment schedule in Realpad, invoice data are manually re-typed to ERP systems such as Microsoft Business Central for the purpose of invoicing.

**Solution**: An integration that automatically transfers complete invoicing data (buyer, unit, amount, due date, ...) from Realpad to your ERP system with one click.

</details>

## Support

If you have any questions, please contact us on [support@realpadsoftware.com.](mailto:support@realpadsoftware.com)

{% hint style="info" %}
**Would you like to receive an email notification about regular product updates?**&#x20;

We’re building a community of power users who can shape our decisions and get access to early releases in exchange for their feedback. Are you a Realpad champion? Let us know!\
[Join Realpad Champions](https://forms.gle/KktWc1XQgwAnjsZX7).
{% endhint %}


---

# 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://product.realpadsoftware.com/en/introduction.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.