Error on Sandbox

[aditi malvankar]

Hi Team,

 

We are trying to access dpc sandbox url (https://sandbox.dpc.cms.gov/api/v1/Token/auth) from azure east us2 vnet using azure integrated runtimes and we are getting 403 Forbidden error response. When checked with azure team and network team, we are unable to trace the call going out of our network. The same setup works fine for BCDA sandbox in azure data factory and also DPC sandbox works from Postman. Can you help us understand what are we missing here.

[Data at the Point of Care (DPC) Community]

Hello!

Thanks for your question regarding the API error response. We're reviewing the information you shared and will get back to you shortly.

Thank you,

The DPC API Team
Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.

[Data at the Point of Care (DPC) Community]

Hello,

Thanks again for reaching out! We appreciate your inquiry. Could you confirm if you're sending a user-agent header from Azure? Not including this header can cause the API request to fail.

If you have any other questions or need further assistance, please let us know!

Thank you,

The DPC API Team

Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.

[aditi malvankar]

Hi,

Thank you for your response.

After adding the “user-agent” header, we are now receiving a 200 response.

Quick question: Is the “user-agent” header mandatory for all DPC endpoints?

[Data at the Point of Care (DPC) Community]

Hello!

Thanks for your question regarding the API error response. We're reviewing the information you shared and will get back to you shortly.

Thank you,

The DPC API Team
Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.

[aditi malvankar]

Hi DPC team,

I hope this email finds you well. I am writing to follow up on error above. I would appreciate any updates or answers you can provide at your earliest convenience. 

Thanks and Regards,

Aditi Malvankar

[Data at the Point of Care (DPC) Community]

Hi Aditi,

Thanks for your question. The user agent header is required for all DPC endpoints. Let us know if you have any further questions!

Thanks,

The DPC API Team

Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.