Register Client

Overview

Create a new client (tenant) account to start using the RealtimeX platform. This is typically the first step when integrating RealtimeX into your application.

Once the registration is successful, the API returns:

A Client ID that identifies your tenant workspace.
An Access Token used to authenticate API requests.
A Refresh Token used to obtain new access tokens when the current one expires.

What happens during registration?

Your application sends the client details to the registration endpoint.
RealtimeX creates a dedicated tenant workspace for the client.
Authentication tokens are generated and returned.
The Client ID is stored for all future tenant-scoped requests.

POST{baseUrl}/api/{apiVersion}/auth/jwt/client/register

Authentication: Not required
Tenant-scoped: No (root DB)

Request Headers

Header	Value	Description
Content-Type	application/json	Specifies the content type of the request body.
is-tenant	false	Targets the tenant DB ("true", needs x-client-id) or the root DB ("false", e.g. client register/create).

Request Payload

json

1{2  "name": "client pro 1",3  "email": "cilentpro1@yoppmail.com",4  "slug": "client-pro-1",5  "password": "test@123",6  "metadata": {7    "plan": "pro"8  }9}

Parameter	Type	Required	Description
name	string		The name of the client.
email	string		The email of the client.
slug	string		The slug of the client.
password	string		The password of the client.
metadata	object	Optional	The metadata of the client.

Success Response (HTTP 201 Created)

json

1{2  "success": true,3  "message": "Client registered successfully",4  "data": {5    "client": {6      "name": "client pro 1",7      "email": "cilentpro1@yoopmail.com",8      "slug": "client-pro-1",9      "password": "$2b$10$0CfdKGTQJSnxHEeLAcSJi.YeoxbqIgj6tmkQVmF6qvaW5clwjH58K",10      "isActive": true,11      "_id": "699fe1377846dcfb775c645c",12      "createdAt": "2026-02-26T05:59:19.339Z",13      "updatedAt": "2026-02-26T05:59:19.339Z",14      "__v": 015    },16    "accessToken": "<access-token>",17    "refreshToken": "<refresh-token>"18  },19  "error": null20}

After Registration

Store these values securely

You’ll use them for all subsequent API requests.

Access Token

Required

Include in the Authorization header.

Refresh Token

Required

Generate a new access token when needed.

Client ID

Tenant APIs

Send with x-client-id for tenant-scoped endpoints.

Next Request Example

After registration, authenticate subsequent tenant-scoped requests like this:

http

1GET /api/v1/user/list HTTP/1.12Authorization: Bearer <access_token>3is-tenant: true4x-client-id: <client_id>

Common Errors

Code	Meaning	Reason
400 Bad Request	Invalid or missing fields	The request body is incomplete or contains invalid data.
409 Conflict	Client already exists	A client account with the same email already exists.
500 Internal Server Error	Unexpected error	An unexpected error occurred on the server.

You’re ready to continue

Once registration is complete, proceed to Auth → Login Client or start calling protected tenant APIs using the returned credentials.

Overview

Create a new client (tenant) account to start using the RealtimeX platform. This is typically the first step when integrating RealtimeX into your application.

Once the registration is successful, the API returns:

A Client ID that identifies your tenant workspace.
An Access Token used to authenticate API requests.
A Refresh Token used to obtain new access tokens when the current one expires.

Header

Value

Description

Content-Type

application/json

Specifies the content type of the request body.

is-tenant

false

Targets the tenant DB ("true", needs x-client-id) or the root DB ("false", e.g. client register/create).

Request Payload

json

1{2  "name": "client pro 1",3  "email": "cilentpro1@yoppmail.com",4  "slug": "client-pro-1",5  "password": "test@123",6  "metadata": {7    "plan": "pro"8  }9}

Parameter	Type	Required	Description
name	string		The name of the client.
email	string		The email of the client.
slug	string		The slug of the client.
password	string		The password of the client.
metadata	object	Optional	The metadata of the client.

Success Response (HTTP 201 Created)

json

1{2  "success": true,3  "message": "Client registered successfully",4  "data": {5    "client": {6      "name": "client pro 1",7      "email": "cilentpro1@yoopmail.com",8      "slug": "client-pro-1",9      "password": "$2b$10$0CfdKGTQJSnxHEeLAcSJi.YeoxbqIgj6tmkQVmF6qvaW5clwjH58K",10      "isActive": true,11      "_id": "699fe1377846dcfb775c645c",12      "createdAt": "2026-02-26T05:59:19.339Z",13      "updatedAt": "2026-02-26T05:59:19.339Z",14      "__v": 015    },16    "accessToken": "<access-token>",17    "refreshToken": "<refresh-token>"18  },19  "error": null20}

Common Errors

Code	Meaning	Reason
400 Bad Request	Invalid or missing fields	The request body is incomplete or contains invalid data.
409 Conflict	Client already exists	A client account with the same email already exists.
500 Internal Server Error	Unexpected error	An unexpected error occurred on the server.

You’re ready to continue

Once registration is complete, proceed to Auth → Login Client or start calling protected tenant APIs using the returned credentials.