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

SuperTokens Email Verification API

Email verification token creation and validation

SuperTokens Email Verification API is one of 10 APIs that SuperTokens publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Email Verification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, a JSON-LD context, and 2 JSON Schemas.

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

Requests are made against a single base URL, http://{host}:{port}.

3 operations 2 paths 5 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.1
Base URL
https://{supertokens-core-host}:{port}
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

SuperTokens Email Verification API declares 1 security scheme for authenticating requests. An API key is passed in the header as api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — SuperTokens Core API key (configured in config.yaml or via environment variable)

Paths & Operations 3

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

Email Verification 3

Email verification token creation and validation

POST
/recipe/user/email/verify/token
Create Email Verification Token
createEmailVerificationToken body → 200
POST
/recipe/user/email/verify
Verify Email
verifyEmail body → 200
GET
/recipe/user/email/verify
Is Email Verified
isEmailVerified 2 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are VerifyEmailRequest (3 properties), EmailVerificationTokenRequest (3 properties), IsEmailVerifiedResponse (2 properties), EmailVerificationTokenResponse (2 properties). Each schema is shown below with its type and property counts.

EmailVerificationTokenRequest
object
3 properties 2 required
EmailVerificationTokenResponse
object
2 properties
StatusResponse
object
1 property
IsEmailVerifiedResponse
object
2 properties
VerifyEmailRequest
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

supertokens-email-verification-api-openapi.yml Raw ↑

Other APIs SuperTokens publishes across the network.

SuperTokens Email Password API
SuperTokens Health API
SuperTokens Multi Tenancy API
SuperTokens Passwordless API
SuperTokens Sessions API
SuperTokens Third Party API
SuperTokens User Metadata API
SuperTokens User Roles API
SuperTokens Users API
Where this information came from

This is an independent, third-party profile of SuperTokens Email Verification 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.