How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Emotive Auth0 API

The Auth0 API from Emotive — 5 operation(s) for auth0.

Emotive Auth0 API is one of 36 APIs that Emotive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Auth0. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a getting-started guide.

This API exposes 5 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api-gw.emotiveapp.co/auth.

5 operations 5 paths 4 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.emotiveapp.co
Authentication
API Key
License
Private
Resource Areas
1

Authentication & Security 1

Emotive Auth0 API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth).

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Auth0 5
POST
/auth0/google_token
Accept Auth0 JWT for Google login, create Emotive admin JWT, redirect to Emotive admin brand selection page.
controllers.auth0.issue_token_for_google_login body → 302400401
POST
/auth0/login
Authenticate username/password for auth0
controllers.auth0.login body → 200400401403
POST
/auth0/password-reset
Password reset from auth0
controllers.auth0.password_reset body → 200400401404
POST
/auth0/token
Accept Auth0 JWT, create Emotive JWT, redirect to Emotive home page.
controllers.auth0.issue_token body → 302400401
GET
/auth0/user/{email}
Get user profile info for password reset using Auth0
controllers.auth0.get_user 1 param → 200400401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Auth0JWTPayload (2 properties), Auth0PasswordResetPayload (2 properties), Auth0LoginPayload (2 properties), JsonResponse (1 property). Each schema is shown below with its type and property counts.

Auth0LoginPayload
object
2 properties 2 required
Auth0PasswordResetPayload
object
2 properties 2 required
JsonResponse
object
1 property
Auth0JWTPayload
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emotive-auth0-api-openapi.yml Raw ↑

Other APIs Emotive publishes across the network.

Emotive Knowledge Base MCP Server
Emotive Admin API
Emotive Authentication Source API
Emotive Brand API
Emotive Brands API
Emotive Bulk Subscriber API
Emotive Connections API
Emotive Custom Events API
Emotive Experience API
Emotive Google API
Emotive Impersonate API
Emotive JWT API
Where this information came from

This is an independent, third-party profile of Emotive Auth0 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.