Workflow or API calls:
Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? No
Have you signed up to be in the Healthcare Developer Track? No
Are you a registered Code Program member? Yes
Does your App have a presence on the Oracle Healthcare App Marketplace? No
Are you developing on behalf of an Oracle Health client? No
If so, which client:
Application's Client ID and App ID, if relevant:
**c7221076-42cd-4ab1-9009-e6d791f983e8**
**6d32544e-5735-4603-a3b7-82ae2215136c**
Expected Result:
To see a successful post for the financial transaction
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id: /D3CEFCBC646A3AA825F8402AF92AC394/ADA82853896983121C07ED052FBC4547
Date/time of the example: Wed, 15 Oct 2025 16:41:04 GMT
I got back my bearer token with these scopes:
"scope": "system/Appointment.read system/Appointment.write system/FinancialTransaction.write system/Patient.read system/Slot.read",
So I would expect that when I call the financial transaction with my bearer token I would get a successful response. I am using the sample req body from the docs.
However this is the response I get:
{
"code": 403,
"message": "code=\"urn:cerner:error:oauth2:resource-access:insufficient-scopes\", error=\"insufficient_scope\", subcode=\"no_scope_for_resource_path\""
}