Returning.AIDevelopers
v1

API reference / Legacy / Authentication

.md

Log in user with password

This page documents POST /auth/login.

Last updated 26 Sep 2026API v1

Method
POST
Path
https://api.returning.ai/auth/login
Retries
Repeating login will not mount the route.

Authentication#

Header
Authorization: Bearer <API_KEY>

Password login is not the community API-key flow. A valid community key does not make this route exist.

Behaviour#

That login route is not mounted on https://api.returning.ai.

Do not use it for broker user ingestion. Create members with Create New User and look them up with Get User Data.

Request#

Headers#

Authorization#stringREQUIRED
API key.

RuleBearer <API_KEY>

Content-Type#stringREQUIRED
Request body format.

Ruleapplication/json

Body#

email#stringREQUIRED
User email address.

Eg"savade@koletter.com"

password#stringREQUIRED

Eg"@Password123"

host#stringOPTIONAL

Eg"ic.genesiv.com"

Watch for

  • Legacy Authentication pages describe an application login that this public API gateway does not serve.
  • GET /api/secureAuth also 404s.
  • Register is the same class of unmounted route.
More examples and details

There is no success example.

  • POST /v1/auth/login → HTML 404 Cannot POST /api/secureAuth/login
  • POST /auth/login → 404
curl --request POST \
  --url https://api.returning.ai/auth/login \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "email": "savade@koletter.com",
    "password": "@Password123",
    "host": "ic.genesiv.com"
  }'

Response#

This POST has no success response on https://api.returning.ai.

meta#objectALWAYS

Eg{ ... }

success#booleanALWAYS

Egtrue

message#stringALWAYS

Eg"Login success"

devMessage#stringALWAYS

Eg"Login success"

body#objectALWAYS

Eg{ ... }

accessToken#stringALWAYS

Eg"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE0NTA3NSIsImlhdCI6MTc0NjAwMTY1MywiZXhwIjoxNzQ2MDg4MDUzfQ.a-ee52XuvMtnV4tGgapFDNOh8kvGxswvzMJujSUFLxU"

refreshToken#stringALWAYS

Eg"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE0NTA3NSIsImlhdCI6MTc0NjAwMTY1MywiZXhwIjoxNzQ2NjA2NDUzfQ.Vuy6Va2QdkwPpsLpx1rurIkv9EcxM1zJapXz0Vj9f_U"

{
  "meta": {
    "success": true,
    "message": "Login success",
    "devMessage": "Login success"
  },
  "body": {
    "accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE0NTA3NSIsImlhdCI6MTc0NjAwMTY1MywiZXhwIjoxNzQ2MDg4MDUzfQ.a-ee52XuvMtnV4tGgapFDNOh8kvGxswvzMJujSUFLxU",
    "refreshToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE0NTA3NSIsImlhdCI6MTc0NjAwMTY1MywiZXhwIjoxNzQ2NjA2NDUzfQ.Vuy6Va2QdkwPpsLpx1rurIkv9EcxM1zJapXz0Vj9f_U"
  }
}

Errors#

Fix the request02

400Fix the request
Invalid request. Check required parameters, body fields, file format, pagination values, and ObjectId values.
401Fix the request
Invalid credentials, disabled account, or authentication token problem.

Retry with backoff01

500Retry with backoff
Unexpected Returning.AI service error.
{
  "status": "fail",
  "message": "Invalid request. Check required parameters, body fields, file format, pagination values, and ObjectId values."
}

Next step#

Getting StartedCreate a community API key and call a /v1 read.