Live Direct Marketing Auth API

The auth API from Live Direct Marketing — 8 operation(s) for auth.

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/auth/register Register a new account · Auth controller register #
Ask an LLM
“How do I sign up for a new account?”
“Can I accept the terms and privacy versions while registering?”
Tell an agent
Register {email} with password {password}.
Sign up {email} with password {password} and send emails in {emailLocale}.
GET /api/auth/verify Verify an email address with a token · Auth controller verify #
Ask an LLM
“How do I confirm my email address after signing up?”
“What does the verification link token do?”
Tell an agent
Verify my email with token {token}.
Confirm the signup using verification token {token}.
POST /api/auth/resend-verification Resend the verification email · Auth controller resend #
Ask an LLM
“I never got the verification email, can it be sent again?”
“Can I request a new confirmation link?”
Tell an agent
Resend the verification email to {email}.
Send {email} a fresh confirmation link.
POST /api/auth/login Log in with email and password · Auth controller login #
Ask an LLM
“How do I log in with my email and password?”
“What do I get back when I sign in?”
Tell an agent
Log in as {email} with password {password}.
Sign {email} in using {password}.
POST /api/auth/logout Log out of the current session · Auth controller logout #
Ask an LLM
“How do I end my session?”
“Can I sign out from the API?”
Tell an agent
Log me out.
End my current signed-in session.
GET /api/auth/me Get the signed-in user · Auth controller me #
Ask an LLM
“Who am I logged in as?”
“Can I check my current session's user details?”
Tell an agent
Show who I'm signed in as.
Get my current session's user profile.
POST /api/auth/email-access Request an email sign-in link · Email access controller request #
Ask an LLM
“Can I get access sent to my email instead of using a password?”
“Is there a passwordless email access option?”
Tell an agent
Request email access for my sign-in.
Send me a passwordless access email.
POST /api/auth/email-access/consume Use an email access link to sign in · Email access controller consume #
Ask an LLM
“What happens when I open the email access link I received?”
“Can I redeem an emailed access code to log in?”
Tell an agent
Consume the email access link I received.
Redeem my emailed access code to sign in.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/live-direct-marketing-online:live-direct-marketing-online-auth-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

live-direct-marketing-online-auth-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: inbox-check Auth API
  description: Email deliverability test API for AI agents and automation. Same surface is exposed via REST (here), MCP (streamable-http at /mcp), and A2A (skill manifest at /.well-known/agent.json).
  version: 1.0.0
  contact: {}
servers: []
tags:
- name: Auth
paths:
  /api/auth/register:
    post:
      operationId: AuthController_register
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RegisterDto'
      responses:
        '202':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller register
      x-summary-source: derived
  /api/auth/verify:
    get:
      operationId: AuthController_verify
      parameters:
      - name: token
        required: true
        in: query
        schema:
          type: string
      responses:
        '200':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller verify
      x-summary-source: derived
  /api/auth/resend-verification:
    post:
      operationId: AuthController_resend
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ResendDto'
      responses:
        '202':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller resend
      x-summary-source: derived
  /api/auth/login:
    post:
      operationId: AuthController_login
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LoginDto'
      responses:
        '200':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller login
      x-summary-source: derived
  /api/auth/logout:
    post:
      operationId: AuthController_logout
      parameters: []
      responses:
        '200':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller logout
      x-summary-source: derived
  /api/auth/me:
    get:
      operationId: AuthController_me
      parameters: []
      responses:
        '200':
          description: ''
      security:
      - cookie: []
      tags:
      - Auth
      summary: Auth controller me
      x-summary-source: derived
  /api/auth/email-access:
    post:
      operationId: EmailAccessController_request
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/EmailAccessDto'
      responses:
        '202':
          description: ''
      tags:
      - Auth
      summary: Email access controller request
      x-summary-source: derived
  /api/auth/email-access/consume:
    post:
      operationId: EmailAccessController_consume
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConsumeAccessDto'
      responses:
        '200':
          description: ''
      tags:
      - Auth
      summary: Email access controller consume
      x-summary-source: derived
components:
  schemas:
    ConsumeAccessDto:
      type: object
      properties: {}
    EmailAccessDto:
      type: object
      properties: {}
    RegisterDto:
      type: object
      properties:
        emailLocale:
          type: string
          enum:
          - ru
          - en
        email:
          type: string
          maxLength: 254
          format: email
        password:
          type: string
          minLength: 8
          maxLength: 200
        acceptedTosVersion:
          type: string
          description: 'Versions of the Terms of Service and Privacy Policy the user accepted

            at the moment of signup. Required for new registrations going forward

            (frontend ships a checkbox + version constants). Optional in this DTO

            for one release cycle so the live web frontend keeps working until the

            web-MR adds the checkbox; after that we''ll tighten to required.


            Stored verbatim in `consent_log` row. See W1a.'
          maxLength: 40
        acceptedPrivacyVersion:
          type: string
          maxLength: 40
      required:
      - email
      - password
    LoginDto:
      type: object
      properties:
        email:
          type: string
          maxLength: 254
          format: email
        password:
          type: string
          maxLength: 200
      required:
      - email
      - password
    ResendDto:
      type: object
      properties:
        email:
          type: string
          maxLength: 254
          format: email
      required:
      - email
  securitySchemes:
    apiKey:
      scheme: bearer
      bearerFormat: icp_live_*
      type: http
    adminKey:
      type: apiKey
      in: header
      name: X-Admin-Key