Reviewing and submitting asset summary data

Submitting data to GRESB at group level and in bulk

Use the GRESB group review page to review how synchronized your IBM Envizi ESG Suite data is against data in GRESB at the group or entity level. You can also use the GRESB group review page to send asset data in bulk by API.

To use this feature, select multiple rows and click Submit to GRESB. All fields in all sections for the selected rows are submitted. To view the API status and any returned validations, click the location name to go to the GRESB Asset Summary (with API) page.

Refreshing heatmap data displayed in the GRESB group review page

After data is sent to GRESB through the API, the percentage of matching responses in the heatmap might not be reflected immediately. This is because of the timing of the API data submission, and the timing of the page refresh to get the latest values stored in GRESB. After data is submitted, wait a few minutes for the API data transfer to GRESB to be completed, and then refresh the page twice, with approximately fifteen minutes between each refresh. The first page refresh triggers a series of API calls to GRESB to fetch new values stored in GRESB for each property, and the second page refresh displays the updated percentage of matching responses based on the most recently retrieved data from GRESB from the first page refresh.

What does '404 Resource not found’ mean?

If your API connection encounters a 404 Resource not found error, it is most likely that the asset’s reporting entity hasn’t been authorized in the GRESB portal to grant Envizi ESG Suite API access to it. An account manager with access to the GRESB portal needs to do the steps at Connecting to GRESB by API to grant Envizi ESG Suite API access to your reporting entity in the GRESB portal.

The steps need to be repeated for every GRESB reporting entity. For more information, see the GRESB API documentation.