Closed joeyhorst closed 2 years ago
@apostolosSotiropoulos @miguelaferreira till recently api.gresb.com was accessible. Do you know what the correct base URL is for production endpoints?
That domain name was not updated while migrating the production portal. I've updated now, it should be reachable again. If not immediately, within the hour all DNS caches should have been invalidated and the resolution should work again.
By the way, that name api.gresb.com
is pointing to the portal instance. I'm not sure how it is used but when I reach it, I'm directed to the portal sign in page. I guess that to use the API one needs certain paths.
Edit: it seems like that, indeed. When I reach the path you posted earlier @joeyhorst I get an expected error.
curl https://api.gresb.com/api/v1/entities/5028/assets
{"error":"The access token is invalid"}
Beautiful - thanks for updating @miguelaferreira 👍
In http://gresb.github.io/api-docs/#basic-operations-endpoints, we refer to https://api.gresb.com/api/v1 as the production endpoint. This is/was? the URL to use for submitting the real estate asset data via the API.
Receiving some questions from data partners why it is not accessible from the browser. Will refer them to https://portal.gresb.com/oauth/applications for prod and https://api-sandbox.gresb.com/oauth/applications for sandbox.
Check if the following URL is still used for the production API endpoint? If not then change the api-docs accordingly.