calcasa-api 0.0.2

Calcasa Public API

This is a preliminary version of the Calcasa Public API. This service is currently in development.

## Changelog

### 2021-11-11 - Renamed /fundering endpoint to /funderingen to be more in line with other endpoints - Renamed `HerstelType` to `FunderingHerstelType`. - Added `FunderingType` values.

### 2021-11-10 - Adjusted OpenAPI Spec generation to fix some issues with certain generators. This also means that the nullable nature of certain fields is now correctly represented. Please refer to the Generation article for more information, the config files were updated aswell. ### 2021-11-09 - Added `Status` and `Taxatiedatum` to `Taxatiedata` model.

### 2021-11-08

• Renamed `id` field in `AdresInfo` model to `bagNummeraanduidingId`.

• Added `GET /v0/fundering/{id}` endpoint with corresponding models.

• Changed HTTP response code for the `BusinessRulesProblemDetails` error return type of `POST /v0/waardering` from `422 Unprocessable Entity` to `406 Not Acceptable` to fix a duplicate.

### 2021-10-13

• Added `taxatie` field to `Waardering` model.

• Added `Taxatiedata` model containing the `taxatieorganisatie` field for desktop valuations.

### 2021-09-29

• Added `aangemaakt` timestamp field to `Waardering` model.

• Added `WaarderingZoekParameters` model to replace `WaarderingInputParameters` in the `POST /v0/waarderingen/zoeken` endpoint.

• Split `Omgevingsdata` model into a set of separate `Gebiedsdata` models that also contain extra statistics.

• Added `bijzonderheden` field to `VorigeVerkoop` model.

• Renamed `ReferentieBijzonderheden` model to `VerkoopBijzonderheden`.

### 2021-09-22

• Initial release of v0

## Client packages  -  -  ## Client implementation notes Clients should at all times be tolerant to the following:

• Extra fields in responses

• Empty or hidden fields in responses

• Extra values in enumerations

• Unexpected error responses in the form of [Problem Details](https://rfc-editor.org/rfc/rfc7807)

## OpenAPI Specification This API is documented in OpenAPI format version 3 you can use tools like the [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) to generate API clients.

## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

## Authentication

Authentication is done via [OAuth2](https://oauth.net/2/) and the [client credentials](https://oauth.net/2/grant-types/client-credentials/) grant type.