Hi Stephen,
Thanks for reaching out! Please provide a date range of when you were seeing the 415 error so our engineers can investigate?
Also, please confirm: you are not including the curly braces { } when submitting the actual text string in the request, correct?
-H 'Accept: application/json' ^
-H 'Content-Type: text/plain' ^
-X POST ^
-d "{content of JWT}"
To answer your other question:
The documentation says it must be a signed JWT - how does a JWT get signed?
A signed JWT is one that has been signed with the customer’s public key. The online tool they’ve used to generate the JWT signs it for them.
For more detailed information, please visit the DPC documentation page (https://dpc.cms.gov/docsV1). JWT’s are covered in step 4 of the Authorization section.
We appreciate your patience while we look into this issue, please contact us with any additional questions.
Best,
The DPC Team