ArcGIS GeoEnrichment createReport Error

Pramod_bahir

We are using ArcGIS JavaScript API 4.32.0 with a React (Vite) application and the GeoEnrichment createReport service to generate Demographic Reports.

• Previously, the report generation and download worked using a static API Key, but recently (Last Week) we observed that the service now requires token-based authentication with expiration, meaning a new token must be generated periodically instead of using the API key directly.
• Below is the error message . we have confirm that token is still valid, beacuse we are able to  featch the aviablable demographic list using the  status API key  : 

{
  "error" : {
    "code" : 498,
    "message" : "Invalid token. (code = 498). [].",
    "details" : [ ]
  }
}

• Additionally, we noticed some changes in the report response/PDF format, which initially caused issues opening the downloaded report in different PDF clients.

Could you please confirm:

• If there has been a recent change in authentication requirements for the GeoEnrichment service?

• Whether API keys are no longer supported for report downloads and OAuth/token authentication is now required?

• If there were recent updates to the report generation or response format?

We are currently running this with ArcGIS JS API 4.32.0 in a React (Vite) environment.

Any clarification or documentation on these changes would be appreciated.

ShlokWagle7

Hi @Pramod_bahir - API key should still work for your Geoenrichment/CreateReport request as long as the API key is not expired and has GeoEnrichment service privilege enabled. You can check this in your ArcGIS API key item page. Can you test with your API key outside of your application first to confirm? 

Example URL: https://geoenrich.arcgis.com/arcgis/rest/services/World/geoenrichmentserver/GeoEnrichment/createReport?studyAreas=[{"geometry":{"x":-117.1956,"y":34.0572}}]&report=dandi&f=bin&format=PDF&token=<ACCESS_TOKEN>

Replace <ACCESS TOKEN> with your static API key. If you have a valid API key, it should download a pdf report.  If this works, the issue is likely with your web app and not the API key.

Thanks, 
Shlok