Unable to Create First Client Token in DPC Sandbox – Organization 1408

[Gokulraj]

Unable to Create First Client Token in DPC Sandbox – Organization 1408

Hello DPC Support Team,

I am unable to create the first client token for my organization in the DPC Sandbox portal.

Environment: DPC Sandbox
Organization ID: 1408

When I navigate to the Client Tokens section, click + New Token, enter a label, and select Create Token, I receive the following error:

“Client token could not be created.”

I have reproduced the issue multiple times.

I also tested using:

• A normal Chrome browser session

• Chrome Incognito mode

• A different token label, such as DPC-Sandbox-01

The issue occurs consistently.

From Chrome Developer Tools, I can confirm that the portal sends the following request:

POST https://sandbox.dpc.cms.gov/organizations/1408/client_tokens

The request returns:

HTTP 200 OK

The submitted payload includes:

label: DPC-Sandbox-01

However, the client token is not created and the portal displays the error:

“Client token could not be created.”

Request IDs from my attempts:

53ce48e2-0c34-4e8b-a5fd-0530e324460c

119b287f-3992-499f-b4ae-1908b324d633

Could you please check the DPC backend logs and verify whether there is an issue with the organization/API registration or client-token configuration for Organization 1408?

This is our first client token, so we are currently unable to proceed with DPC authentication and API access.

I have attached screenshots showing the POST request, HTTP 200 response, request ID, and submitted token label.

Thank you.

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

Hello,

Thanks for your question regarding Client Token generation. 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,

Thank you for your patience – we wanted to give you a quick update. We're still actively investigating the client token creation issue you reported and are working to get you a resolution as soon as possible. 

We expect to have a resolution for you early next week and will follow up as soon as we do.

Best,

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,

We've resolved the client token creation issue you reported in the sandbox. You should now be able to create your client token in the DPC Sandbox portal as expected.

Let us know if you run into any further issues or have questions. We're happy to help.

Best,

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.