# Passwordless in auth0 is not taking api token during run time **URL:** \ **Category:** Get Help\ **Tags:** new-universal-login-experience, login-experience\ **Created:** [June 1, 2026, 11:12am UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443 "2026-06-01T11:12:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![valuemoretec](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/valuemoretec/32/72551_2.png) [@valuemoretec](https://community.auth0.com/u/valuemoretec)\ **Post date:** [June 1, 2026, 11:12am UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443/1 "2026-06-01T11:12:51Z")
passwordless in auth0 is not taking api token during run time but working with same api using manually in sms provider and test case in auth0 ---
**Author:** ![discourse\_ai\_spam](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@discourse\_ai\_spam](https://community.auth0.com/u/discourse_ai_spam)\ **Post date:** [June 1, 2026, 11:12am UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443/2 "2026-06-01T11:12:52Z")
---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [June 2, 2026, 10:08pm UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443/3 "2026-06-02T22:08:21Z")
---
**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\ **Post date:** [June 2, 2026, 10:22pm UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443/5 "2026-06-02T22:22:52Z")
Hi @valuemoretec Thank you for reaching out to us! If your Auth0 Passwordless setup works perfectly when tested manually via the SMS provider and also during “Try connection” / “Test” cases in the Auth0 Dashboard, but fails to send or accept the API token/keys at runtime, it is likely that you are encountering one of the following: - If you configured a legacy Custom SMS Gateway under your Connection settings, Auth0’s native gateway integration does not support API Keys, Auth Tokens, or Basic Authentication at runtime. [It only supports](https://community.auth0.com/t/custom-sms-provider/109743) Unauthenticated HTTP requests and JWT (JSON Web Token) authentication. If your SMS provider requires API Key/Token, you must implement a [Custom Phone Provider using Auth0 Actions](https://auth0.com/docs/customize/phone-messages/configure-phone-messaging-providers/configure-a-custom-phone-provider); - Ensure you are adhering strictly to the exact Liquid syntax/macros expected by your gateway, or build a lightweight middle-layer proxy to handle the API payload translation between Auth0 and your SMS provider; - If the problem is not _sending_ the SMS, but rather that the authentication token returned _after_ submitting the SMS code is rejected by your API backend, check your runtime token parameters. In manual/test environments, Auth0 might successfully validate a code and return a Token. At runtime, however, if your frontend application initiates the passwordless flow without explicitly passing an `audience` parameter in the `/authorize` or `/oauth/token` request, Auth0 defaults to issuing an **opaque/JWE token** instead of a standard JWT Let us know if this helped solve the issues! Best regards, Gerald ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [June 29, 2026, 8:27pm UTC](https://community.auth0.com/t/passwordless-in-auth0-is-not-taking-api-token-during-run-time/200443/6 "2026-06-29T20:27:45Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.