Auth0 · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Auth0 Authentication Deprecated > Passwordless API

3 actions 3 updates phrasing extends openapi/auth0-deprecated-passwordless-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Auth0's API. It is a proposal applied on top of the contract, not a document Auth0 publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/passwordless/verify'].post
$.paths['/oauth/ro'].post

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Auth0 Authentication Deprecated > Passwordless API
  version: 1.0.0
extends: openapi/auth0-deprecated-passwordless-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/passwordless/verify'].post
  update:
    x-apievangelist-phrasing:
      intent: Log in with a passwordless code (legacy)
      effect: write
      questions:
      - How does a user log in with the code from a passwordless email or SMS on the old endpoint?
      - Can the legacy passwordless verify endpoint exchange a code for tokens?
      instructions:
      - text: Verify passwordless code {password} for {username} on connection {connection}.
        slots:
          password: requestBody.password
          username: requestBody.username
          connection: requestBody.connection
      - text: Log in {username} with verification code {password} using the deprecated passwordless verify.
        slots:
          username: requestBody.username
          password: requestBody.password
      method: generated
      generated: '2026-10-01'
- target: $.paths['/oauth/ro'].post
  update:
    x-apievangelist-phrasing:
      intent: Log in with username and password (legacy)
      effect: write
      questions:
      - Can I still get tokens with a username and password via the old resource owner endpoint?
      - Which connections does the legacy resource owner login work for?
      instructions:
      - text: Authenticate {username} with password {password} on {connection} via the legacy resource owner endpoint.
        slots:
          username: requestBody.username
          password: requestBody.password
          connection: requestBody.connection
      - text: Get tokens for {username} on database connection {connection} with scope {scope}.
        slots:
          username: requestBody.username
          connection: requestBody.connection
          scope: requestBody.scope
      method: generated
      generated: '2026-10-01'