/v1/lead/info

Purpose

Creates or updates a lead record for a specific business and region in the WellnessLiving UAT environment.

This endpoint is typically used when capturing new lead information (e.g., from a web form) before creating a full member account. If the email already exists and is associated with an existing account, the API returns a 200 response with an error payload describing the conflict.

HTTP Request

Method: POST

URL: https://uat-api.wellnessliving.io/v1/lead/info

Required Query Parameters

id_region (number, required)

Region identifier for the request context.

Example: 2

k_business (number/string, required)

Business key/identifier in WellnessLiving.

Example: 49197

Required Headers

Content-Type: application/json

Any required authentication headers (e.g., Authorization: Bearer {{TOKEN}}) must be supplied by the caller, typically inherited from the collection/folder configuration.

JSON Request Body

Body is sent as raw JSON with the following structure:

{
  "k_business": "49197",
  "a_field_data": {
    "743626": "john@example.com",
    "743628": "John",
    "743629": "Doe",
    "743630": "222-222-2222"
  }
}

Top-level Fields

k_business (string, required)

Business key. Should match the k_business passed in the query string.

a_field_data (object, required)

A key/value map of lead form fields. Keys are internal field IDs in the WellnessLiving configuration; values are the user-provided data.

Sample Mapped Fields in `a_field_data`

Note: Field IDs are environment-specific configuration IDs; names below describe their apparent usage based on the sample.

"743626" – Lead email

Type: string (email)

Example: "john@example.com"

Used to check if an account with this email already exists.

"743628" – First name

Type: string

Example: "John"

"743629" – Last name

Type: string

Example: "Doe"

"743630" – Phone number

Type: string (phone)

Example: "222-222-2222"

Additional field IDs can be included in a_field_data depending on the lead form configuration.

Successful 200 Response – Email Already Exists Error Case

When the email provided in a_field_data["743626"] is already associated with an existing account, the API responds with HTTP 200 but returns an error payload describing the problem instead of creating a new lead.

Example response shape (simplified from the last response):

{
  "a_error": [
    {
      "html_message": "An account with this email already exist...",
      "id": null,
      "s_field": "field-743626",
      "s_message": "An account with this email already exist...",
      "sid": "login-member"
    }
  ],
  "class": "Core\\Request\\Api\\UserException",
  "code": null,
  "message": "An account with this email already exist...",
  "status": "login-member",
  "s_version": "444085",
  "__a_message": [
    "name-first|rs.field.general.sid",
    "name-last|rs.field.general.sid",
    "login|rs.field.general.sid",
    "phone-cell|rs.field.general.sid",
    "phone-home|rs.field.general.sid",
    "phone-work|rs.field.general.sid",
    "birthday|rs.field.general.sid",
    "address|rs.field.general.sid",
    "location|rs.field.general.sid",
    "vaccination-status|rs.field.general.sid"
  ]
}

Response Fields (error case)

a_error (array)

List of field-level errors.

Each item contains:

html_message: Full error message, possibly formatted for display.

id: Internal identifier for the error (often null).

s_field: Field identifier causing the error (e.g., field-743626 for the email field).

s_message: Human-readable error message.

sid: Error code/status identifier (e.g., login-member).

class (string)

Backend exception class name (e.g., Core\Request\Api\UserException).

code (number or null)

Numeric error code, if provided.

message (string)

Top-level error message (duplicates the field error in this scenario).

status (string)

Machine-readable status for the error (e.g., login-member).

s_version (string)

Internal version identifier for the backend.

__a_message (array of strings)

Additional internal message keys/identifiers, often mapping to general field SIDs (first name, last name, login/email, various phone and profile fields).

Notes

A 200 HTTP status does not guarantee that the lead was created; always inspect the response body. Presence of a_error, class, and status values like login-member indicates an error condition even when the status code is 200.

Purpose#

HTTP Request#

Required Query Parameters#

Required Headers#

JSON Request Body#

Top-level Fields#

Sample Mapped Fields in a_field_data#

Successful 200 Response – Email Already Exists Error Case#

Response Fields (error case)#

Notes#

Request

Responses