ACO name not available while trying to create API clientID

36 views
Skip to first unread message

RAMAKRISHNA NALLA

unread,
Jul 28, 2026, 9:30:08 AMJul 28
to Beneficiary Claims Data API (BCDA) Community

Hi Team,

I am Ramakrishna.

I am trying to create API credentials for an ACO through the ACOMS portal. However, I am unable to find my ACO while creating the API Client ID.

However, I am able to see the ACO Name in my Data Hub section

I selected all the available roles during the process, but my ACO is still not visible in the "Select ACO" dropdown. I also searched using the ACO ID, but it does not appear in the list.

Could you please let me know how I can resolve this issue?

Thank you in advance for your assistance.

Regards,
Ramakrishna

Beneficiary Claims Data API (BCDA) Community

unread,
Jul 28, 2026, 11:05:04 AMJul 28
to Beneficiary Claims Data API (BCDA) Community

Hi Ramakrishna,


To manage an ACO's BCDA credentials using ACO-MS, you must have the "Credential Management" role for that ACO. If you are still having issues with ACO-MS after confirming you have the Credential Management role, please contact the ACO-MS Technical Help Desk for further assistance at SharedSavi...@cms.hhs.gov.

Thank you,

The BCDA Team

RAMAKRISHNA NALLA

unread,
Jul 29, 2026, 11:19:17 AMJul 29
to Beneficiary Claims Data API (BCDA) Community

Hi,

Thank you for your response. It was very helpful.

I can now see my ACO in the list and have successfully generated the client credentials. However, I'm unable to obtain an access token. I'm consistently receiving a 403 Forbidden error.

I used the following token endpoint:
https://api.bcda.cms.gov/auth/token

I also used the generated Client ID and Client Secret to request the access token.

To verify my implementation, I tested the same process against the Sandbox environment, where I was able to obtain an access token without any issues.

Could you please let me know what might be causing this issue in the production environment?

Thank you in advance for your assistance.

Best regards,

Ramakrishna

Reply all
Reply to author
Forward
0 new messages