Is the api server down? Any status update site?

[Yubin Park]

I am pinging the BCDA sandbox and production URLs, and I am not getting any response back. Is there any site I can check the server status? Thanks so much!

[Yubin Park]

ping api.bcda.cms.gov

PING bcda-api-prod-01-1802555575.us-east-1.elb.amazonaws.com (52.44.158.186) 56(84) bytes of data.

^C

--- bcda-api-prod-01-1802555575.us-east-1.elb.amazonaws.com ping statistics ---

136 packets transmitted, 0 received, 100% packet loss, time 138279ms

This is what I did, and I am not getting anything back. Am I doing something wrong?

[Yubin Park]

Is this still the right way to get the access token for the sandbox environment?

curl -d "" -X POST "https://sandbox.bcda.cms.gov/auth/token" \ --user 2462c96b-6427-4efb-aed7-118e20c2e997:825598c105bd1fe021c9eb9d41b30e82beb7a505a1184282e69891f76aa0a396dc9d20f35c9df4a5 \ -H "accept: application/json"
It is not giving me anything!!

[Beneficiary Claims Data API (BCDA) Community]

Hello,

BCDA is currently running as expected and the curl command you shared is an accurate way to retrieve a sandbox token. The results you shared using ping are expected as BCDA does not allow ICMP requests like ping.

The BCDA does not have a webpage indicating status of the API, but you can check the status using the /metadata endpoint. Requests to the production environment (api.bcda.cms.gov) will timeout unless you've added your IP address to BCDA's allow-list as part of the production credentialing process.

In support of our investigation, could you please share the response and error messages from running the curl command you shared earlier?

Thanks,
The BCDA Team

[Jack Shoemaker]

The cURL command line needs a password.

Please DO NOT post that in plain text to this group.

--

Jack N Shoemaker / (336) 202-2165

 

---

From: bc-...@googlegroups.com <bc-...@googlegroups.com> on behalf of Yubin Park <yubin...@mimilabs.ai>
Sent: Monday, October 21, 2024 13:11
To: Beneficiary Claims Data API (BCDA) Community <bc-...@googlegroups.com>
Subject: [BCDA] Re: Is the api server down? Any status update site?

 

--
You received this message because you are subscribed to the Google Groups "Beneficiary Claims Data API (BCDA) Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bc-api+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bc-api/afbe958a-58d4-412e-bc56-b496e82ea38fn%40googlegroups.com.

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please reply to the sender (only) and then delete this message from your inbox as well as any copies. Thank you.

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please reply to the sender (only) and then delete this message from your inbox as well as any copies. Thank you.

Secured by Paubox - HITRUST certified

[Beneficiary Claims Data API (BCDA) Community]

Hi Jack,

Thank you for the reminder to not share PHI, PII, or other sensitive information like BCDA production credentials in the Google Group.  While it's good practice to redact credentials regardless of the environment, this user's earlier message included the publicly available BCDA sandbox credentials - which are not sensitive information.

As a reminder to all, please take a look at our guidance on how to redact PHI, secrets, and other sensitive information from your posts in the BCDA Google Group.

Thanks,
The BCDA team