---
title: "Ready Community (Council Wise) Data Source"
canonical: "https://help.cartinuum.com/space/GC1/4419190785/Ready%20Community%20(Council%20Wise)%20Data%20Source"
format: markdown
---
In Connect for ArcGIS, data sources provide connectivity to third-party business systems. The Ready Community (Council Wise) API data source allows you to fetch real-time data from Ready Community (e.g. property, rating, or owner information) to display in your ArcGIS web mapping applications.

The data source uses Council Wise’s REST APIs with application authentication. You configure an API path and query parameters; map feature attributes (e.g. valuation number, owner email address) can be substituted into the request so that each selected feature retrieves the relevant records from Ready Community.

Below is an example layer link configuration that retrieves property records by Property Id from a Ready Community integration endpoint.

![image-20260409-052744.png](media://ebdf47e2-1162-4bb7-958c-8c63e7fbc5ba)

Each Resource Path brings back different information from Ready Community. You can review the available APIs using the Swagger documentation available from Council Wise.

[https://cwcoreapi.councilwise.com.au/documentation/swagger/index.html](https://cwcoreapi.councilwise.com.au/documentation/swagger/index.html) 

## Data Source Configuration

The Ready Community (Council Wise) API data source configuration requires the following: –

- **Base URL** – The URL for your Council Wise implementation (e.g. `https://cwcoreapi.councilwise.com.au`)
- **Application ID** – The application ID used to sign in to your Council Wise service.
- **Application secret** – The secret associated with that application ID.

> ℹ️ Click [here](https://help.councilwise.com.au/kb/article/3/setting-up--using-a-3rd-party-app-integration-api) to see more information about setting up applications IDs for third party app integration (Ready Community login required).

Optional settings: –

- **Maximum HTTP connections** – Maximum number of simultaneous API requests when multiple map features are selected (default 5). Lower values reduce load on Ready Community; increase only if needed.

Follow the principle of least privilege when configuring integrations. Use an account that has only the access required for your Connect for ArcGIS application (e.g. read-only access to the integration endpoints you use), not a full administrative login.

## Layer Link Configuration

The Ready Community (Council Wise) API layer link configuration includes: –

- **Resource Path** – The API path to call (e.g. `/integration/RG/property_records`). You can use the **[+]** button to insert feature attributes into the path using `{{AttributeName}}` syntax.
- **Query parameters** – One parameter per line in the form `name=value`. Only the first `=` on each line is used to split name and value, so values can contain `=` (e.g. `filters=propertyId={{PROPOID}}`). Use the **[+]** button to insert feature attributes into values. The parameters to use are described in the Swagger documentation and differ for each resource path.
- **JSONata Transformation** (optional) – Only required if you need to pull back information contained in arrays within the query response. For example, to access an array of owners in the response a JSONata value of `owners` might point specifically to that array. Complex JSONata transformations are supported allowing you to extract information from different parts of the response or to filter out certain values (e.g. non-current records). For a full run down of working with JSONata, head to [https://jsonata.org](https://jsonata.org).
- **Test data** (optional) – Sample attribute values for testing the layer link (e.g. `{{PropertyID}}=4957` or `{{Email_Address}}=user@example.com`), one per line. Use this to validate the configuration before publishing.

Validate your Layer Link configuration to confirm the correct information is being returned: -

![image-20260409-054239.png](media://49513179-74ab-4598-affe-998b7cf5ae8f)

When building query parameters, refer to Ready Community’s API documentation for the correct filter format. Errors returned by Ready Community (e.g. invalid column names or filter syntax) are shown in Connect for ArcGIS so you can correct the layer link. A 404 error indicates that the Resource Path URL is invalid or does not exist on your Council Wise service.

![image-20260409-054021.png](media://0ed8a56f-c24b-47f5-9ea0-9169c6e75ccd)