Unable to get token

[ajay mistry]

I am unable to get token, and keep on receiving connection timeout. Is there any outage or is this due to Azure outage.

Thanks,

Ajay

[Beneficiary Claims Data API (BCDA) Community]

Hi Ajay,

Sorry for the trouble connecting to the production API. The timeout responses you've received are consistent with making API requests from an IP address that is not on the allow list. If you haven't already, please ensure that your requests are being made from an IP address that is on the allow-list associated with your organization's credentials in 4i or ACO-MS

Some common API clients, like the Postman Web Client, will send requests from their own web server by default. If you are using the Postman Web Client, please check that any proxy settings for your API client are set to use one of your organization's allowed IP addresses. Alternatively, try making a request from the Postman Desktop Client or another API client. The Postman Desktop Client allows you to view the network information from the request in the console. Postman has some documentation on how to do this here.

If you continue to have this issue after confirming you have taken the steps above, please share the following:

1. The 5 character Entity ID for your organization(s). For example, ACOs in the Shared Savings Program have Entity IDs which begin with the letter 'A' followed by four numbers, like "A9999".
2. The API request that is resulting in these timeout errors. Please be sure to censor Personally Identifiable Information (PII) and other sensitive information (e.g., private keys, passwords) by replacing the information with the word ‘REDACTED’. Additional details and guidance can be found here in the Google Group.
3. The last time a successful job was completed for your respective entity(ies), and the last time a job was requested but not completed.
4. Whether this is happening for every type of resource type (e.g., patient, EoB, coverage).

Thank you,
The BCDA Team