Api/vi/authn giving 401 on API side but works on UI for trial-*.okta.com endpoint

Questions API
1

I have a https://trial-*.okta.com account curently in use.
Something has changed last week, and any curl commands to https://trial-*.okta.com/api/v1/authn are giving me 401 Authentication Error.

The exact same user credentials work as expected on UI, and I can login using them, but only API calls are failing.
Can someone help why this may be happening?

Example curl req and response below -

curl -k --request POST   --url https://trial-<hidden>.okta.com/api/v1/authn   --header 'content-type: application/json'   --data '{
  "username": "<hidden>",
  "password": "<hidden>"

}' | jq

{
  "errorCode": "E0000004",
  "errorSummary": "Authentication failed",
  "errorLink": "E0000004",
  "errorId": "oae4uk_H8RATmujZ5_TbS0EdQ",
  "errorCauses": []
}
2

Can you share the x-okta-request-id response header from your failing request so I can check if we have any other logs on our side about this 401?

3

here’s the info from the response -

< HTTP/2 401 
< date: Tue, 09 Dec 2025 21:34:36 GMT
< content-type: application/json\
< server: nginx
< x-okta-request-id: bcc38bc05d30939f3570c1279e56ffda
4

@shardulb Sorry for the delay. Our team is looking into this and we are planning to have a fix released in January, after the holiday season.

5

Just throwing another hat in the ring - this has broken some of our end-to-end tests that rely on hitting a live Okta API. We’ll have to disable or mock the Okta side on these tests for now, but hoping for a quick resolution to keep our mutual customers happy.

6

@shardulb & @camden.webster A fix has been applied to both of your orgs.

Can you please re-test and let me know if its working now?

7

Thanks @andrea, unfortunately we are still seeing the issue in a specific integrator tenant - not sure if that’s the org you referred to. I can reach out with the specific tenant ID.

8

@camden.webster yes, please do and I can apply the fix to the right org