updateUser

Previous value: -"Set `1` to auto-create unknown category/service names on `updateUser`. Without it, unknown names in `services`/`profession_name` are silently skipped. **Has no effect on `createUser`** (which always auto-creates, hardcoded).\n\nAuto-created sub-categories go under the member's current top-level category with `master_id=0`; deeper nesting requires a separate `createSubCategory` call."New value: +"Set `1` to auto-create unknown category names on `updateUser`. Without it, unknown names in `services`/`profession_name` are silently skipped. **No effect on `createUser`** (always auto-creates). Creates whatever level the name references: top-level via `profession_name`, sub via `services`, and sub-sub inline via the `Sub=>SubSub` format in `services` (no separate `createSubCategory` call needed)."

Added value: +{
+  "description": "Set `1` to wipe ALL the member's sub- and sub-sub-category links (every `rel_services` row) BEFORE applying any `services` in the same call — turns `services` from append into replace. Does NOT remove the top-level category (`profession_id`) or any `list_services` definitions. Without it, `services` is additive. Combine with `services` (and `create_new_categories=1` for unknown names) to replace the member's entire sub-category set in one call. `updateUser` only.",
+  "enum": [
+    "0",
+    "1"
+  ],
+  "type": "string"
+}

Previous value: -"Sub-categories for this member. Formats: `category=>service1,service2` OR `service1,service2` (top category defaults to member's current `profession_id`). Supports sub-sub-categories via `Parent=>Child` (e.g. `Honda=>2022,Honda=>2023,Toyota`).\n\nUnknown names silently ignored unless `create_new_categories=1` is also set (on update - create auto-creates always).\n\n**WARNING:** changing `profession_id` in the same call WIPES all existing sub-category links. Re-send the full `services` list to preserve them."New value: +"Sub-categories for this member. Formats: `category=>service1,service2` OR `service1,service2` (top category defaults to member's current `profession_id`). Supports sub-sub-categories via `Parent=>Child` (e.g. `Honda=>2022,Honda=>2023,Toyota`).\n\nUnknown names silently ignored unless `create_new_categories=1` is also set (on update - create auto-creates always).\n\n**Additive by default** — these links are ADDED to the member's existing ones. To REPLACE the whole set instead, pass `delete_categories=1` in the same call.\n\n**WARNING:** changing `profession_id` in the same call WIPES all existing sub-category links. Re-send the full `services` list to preserve them."

Previous value: -"Cover photo URL. **LANDSCAPE only — never portrait/vertical. Bare URL — no `?query`, must end in `.jpg`/`.jpeg`/`.png`/`.webp`.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage."New value: +"Cover photo URL. **LANDSCAPE only — never portrait/vertical; source via `https://www.pexels.com/search/<term>/?orientation=landscape`; bare URL, no `?query`, must end in `.jpg`/`.jpeg`/`.png`/`.webp` — see image URL rule.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage."

Previous value: -"Timestamp of user's last login. Format: `YYYYMMDDHHmmss` (14-digit, no separators). Auto-maintained by BD on each login - omit unless backfilling historical data during import/migration."New value: +"Timestamp of user's last login. Format: `YYYYMMDDHHmmss` in the site's timezone. BD silently truncates other formats, corrupting the value. BD updates on each login — omit unless backfilling historical data during import/migration."

Previous value: -"User signup date. Format: `YYYYMMDDHHmmss` (14-digit, no separators - e.g. `20260419143022`). Auto-filled by BD on create - omit unless backfilling legacy signup dates during import/migration."New value: +"User signup date. Format: `YYYYMMDDHHmmss` in the site's timezone. BD silently truncates other formats, corrupting the value. BD auto-fills on create — omit unless backfilling legacy signup dates during import/migration."

Previous value: -"OPTIONAL: Enter the FULL URL of the image filename for the user's cover photo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://"New value: +"Cover photo URL. **LANDSCAPE only — never portrait/vertical. Bare URL — no `?query`, must end in `.jpg`/`.jpeg`/`.png`/`.webp`.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage."

Previous value: -"OPTIONAL: Enter the FULL URL of the image filename for the user's profile logo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://"New value: +"Logo URL (brand/business mark). **Bare URL only — no `?query`, must end in `.jpg`/`.jpeg`/`.png`/`.webp`.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage."

Previous value: -"OPTIONAL: Enter the FULL URL of the image filename for the user's profile photo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://"New value: +"Profile photo URL (member headshot). **Bare URL only — no `?query`, must end in `.jpg`/`.jpeg`/`.png`/`.webp`.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage."

Previous value: -"Long description of the member/user. Renders on their public profile page. HTML allowed (per universal safe-HTML rule)."New value: +"Long description of the member/user. Renders on their public profile. Froala body field — use `<p>`/`<h2>`/`<h3>`/`<ul>`/`<ol>` structure; skip images unless user asks. HTML allowed (per universal safe-HTML rule)."

Previous value: -"The long description about this user. Pass raw HTML — do NOT wrap in `<![CDATA[...]]>`, do NOT escape as `&lt;` / `&gt;`, and do NOT include tool-call scaffolding tags (e.g. `<parameter name=\"...\">...</parameter>`, `<invoke>`, `<function_calls>`). BD stores the field value verbatim; any wrapper / escape / scaffolding renders as literal visible text."New value: +"Long description of the member/user. Renders on their public profile page. HTML allowed (per universal safe-HTML rule)."

Previous value: -"The status of the user. BD does NOT validate this field — integers outside the documented set are stored as-is (observed: `99`). Stick to documented values.\\n\\nDocumented values:\\n  1 = Not Active - Account Still Requires Activation\\n  2 = Active - Account is Live\\n  3 = Canceled - Sets User as Canceled Status\\n  4 = On Hold - Account Requires Moderation\\n  5 = Past Due - Sets User as Past Due Status\\n  6 = Incomplete - Paid signup hit an issue BD didn't account for; member was created but stays Incomplete instead of Active (without having paid). Rare edge state.\\n\\nReading: the top-level `status` response field (\"Active\", \"Not Active\", \"Incomplete\", etc.) is a computed label. When `active` is an unknown value, `status` is OMITTED from the response — do not treat `status` as always-present."New value: +"User account status. BD does NOT validate - integers outside the set store as-is (observed: `99`). Stick to documented values:\n\n- `1` = Not Active (requires activation)\n\n- `2` = Active (live)\n\n- `3` = Canceled\n\n- `4` = On Hold (requires moderation)\n\n- `5` = Past Due\n\n- `6` = Incomplete (rare - paid signup hit an issue; member created but unpaid/stuck)\n\n**Read caveat:** top-level `status` response field (`\"Active\"`, `\"Not Active\"`, etc.) is a computed label. When `active` is an unknown value, `status` is OMITTED from the response - don't treat `status` as always-present."

Previous value: -"Use Google Maps to geocode this user's location. Requires the \"Pretty URLs with Google Maps\" feature to be enabled on the site. (string, \"1\" or \"0\").\\n  1 = Yes\\n  0 = No"New value: +"Use Google Maps to geocode this user's location. Requires the \"Pretty URLs with Google Maps\" feature to be enabled on the site. (string, \"1\" or \"0\").\\n 1 = Yes\\n 0 = No"

Previous value: -"If YES, system will import user images and save them to your website. Processing may take several minutes after import.\\n\\nValid values:\\n  1 = Yes\\n  0 = No"New value: +"If YES, system will import user images and save them to your website. Processing may take several minutes after import.\\n\\nValid values:\\n 1 = Yes\\n 0 = No"

Previous value: -"Set to `1` to enable auto-creation of unknown category/service names during this `updateUser` call. Without this flag, unknown names in `services` or `profession_name` are silently skipped. Has no effect on `createUser` (which always auto-creates). Auto-created sub-categories go under the member's current top-level category with `master_id=0`; deeper nesting requires a separate `createSubCategory` call."New value: +"Set `1` to auto-create unknown category/service names on `updateUser`. Without it, unknown names in `services`/`profession_name` are silently skipped. **Has no effect on `createUser`** (which always auto-creates, hardcoded).\n\nAuto-created sub-categories go under the member's current top-level category with `master_id=0`; deeper nesting requires a separate `createSubCategory` call."

Previous value: -"How to apply `credit_amount` to the member's credit balance. `add` increments, `deduct` decrements, `override` REPLACES the balance with `credit_amount` (irreversible via API — no undo). Requires `credit_amount` to be set. Omit both fields to leave credits unchanged. BD does NOT reject deducts/overrides that produce a negative balance — if you need a non-negative guarantee, validate client-side against the current `credit_balance` (dollar-formatted string, may be negative) before calling."New value: +"How `credit_amount` applies to the member's credit balance:\n\n- `add` - increments\n\n- `deduct` - decrements\n\n- `override` - REPLACES balance with `credit_amount` (irreversible via API - no undo)\n\n**Requires `credit_amount` to be set.** Omit both fields to leave credits unchanged.\n\nBD does NOT reject deducts/overrides that produce negative balance. If non-negative required, validate client-side against current `credit_balance` (dollar-formatted string, may be negative) before calling."

Previous value: -"Override BD's auto-generated URL slug. BD may REGENERATE the slug on a future update (when city/category/name change), silently overwriting your override. Usually OMIT — let BD derive. Only set if you must control the public URL and are willing to re-set it after every future update."New value: +"Override BD's auto-generated URL slug. **Usually OMIT** - let BD derive. BD may REGENERATE the slug on future updates (when city/category/name change), silently overwriting your override. Only set if you must control the public URL and will re-set it after every future update."

Previous value: -"Removes stored member images. `remove_all` clears all three (profile, logo, cover); the other values clear only the named image. PERMANENT via API — no undo. To REPLACE an image instead of removing, pass the new `profile_photo` / `logo` / `cover_photo` URL (optionally with `auto_image_import=1`) — do not set `images_action` for replacement."New value: +"Removes stored member images. PERMANENT via API - no undo.\n\n- `remove_all` - clears all three (profile, logo, cover)\n- `remove_profile_image` / `remove_logo_image` / `remove_cover_image` - clears only that image\n\n**To REPLACE** an image instead of removing, pass the new `profile_photo` / `logo` / `cover_photo` URL (optionally with `auto_image_import=1`). Do NOT set `images_action` for replacement."

Previous value: -"Date/time of the user's last login. Format: `YYYYMMDDHHmmss` (14-digit timestamp, no separators). Auto-maintained by BD on each login — omit unless backfilling historical login data during import/migration."New value: +"Timestamp of user's last login. Format: `YYYYMMDDHHmmss` (14-digit, no separators). Auto-maintained by BD on each login - omit unless backfilling historical data during import/migration."

Previous value: -"Listing type classification. **BD does NOT validate this field — any string is stored verbatim.** Canonical values (exact case): `Individual` or `Company`. On `updateUser`, include only when reclassifying an existing member (e.g. fixing a record originally created as `Individual` that should be `Company`). If including, normalize case client-side — `individual` or other off-canonical casings will store as-is and break downstream logic. Otherwise omit to preserve the current value."New value: +"Listing type classification. **BD does NOT validate this field - any string is stored verbatim.** Canonical values (exact case): `Individual` or `Company`. On `updateUser`, include only when reclassifying an existing member (e.g. fixing a record originally created as `Individual` that should be `Company`). If including, normalize case client-side - `individual` or other off-canonical casings will store as-is and break downstream logic. Otherwise omit to preserve the current value."

Previous value: -"REQUIRED when modifying tags. Set to `1` alongside `member_tags` to actually apply the tag change — without this flag the `member_tags` value is ignored. Tag IDs not included in `member_tags` are removed; i.e. the submitted list REPLACES the current set (not additive). To fully clear tags, pass `member_tags` as an empty string with `member_tag_action=1`."New value: +"**REQUIRED when modifying tags.** Set `1` alongside `member_tags` to apply the change - without this flag, `member_tags` value is ignored.\n\n**REPLACES** the current tag set (not additive): tag IDs NOT in `member_tags` are removed. To clear all tags, pass empty `member_tags` with `member_tag_action=1`."

Previous value: -"Comma-separated tag IDs to assign to the member (e.g. `1,2,3`). Discover valid IDs via `listTags`. Requires `member_tag_action=1` to take effect. Replaces the existing tag set on save — include every tag you want the member to have, not just new additions. **Unknown tag IDs are silently dropped** — the response will echo your submitted `member_tags` value, but `tags` in the response will only reflect successfully-attached tags. Re-read the user after update and check the `tags` array to verify."New value: +"Comma-separated tag IDs to assign to the member (e.g. `1,2,3`). Discover via `listTags`. **Requires `member_tag_action=1` to take effect.**\n\n**REPLACES** the existing tag set on save - include every tag you want the member to have, not just additions. Unknown tag IDs are silently dropped - response echoes your submitted value, but `tags` array in the response reflects only successfully-attached tags. Re-GET after update and verify `tags` array."

Previous value: -"If YES, the user's listing will be found in all geographical location searches.\\n\\nValid values:\\n  1 = Yes\\n  0 = No"New value: +"If YES, the user's listing will be found in all geographical location searches.\\n\\nValid values:\\n 1 = Yes\\n 0 = No"

Previous value: -"Alternative to `profession_id` — pass the top-level category NAME as a string. BD looks it up in `list_professions`. On `createUser`, unknown names are auto-created. On `updateUser`, unknown names are silently skipped unless `create_new_categories=1` is also passed."New value: +"Alternative to `profession_id` - pass the top-level category NAME as a string. BD looks it up in `list_professions`.\n\n**Create vs update asymmetry (silent-failure trap):**\n\n- `createUser` -> unknown names auto-create (hardcoded)\n\n- `updateUser` -> unknown names **SILENTLY SKIPPED** unless `create_new_categories=1` is also passed. The write succeeds and returns success; the category just doesn't change. Always pass `create_new_categories=1` on update when supplying a `profession_name` that might not exist."

Previous value: -"The short description about this user. Displays under your user's name on search result pages. 170 Character Limit. Pass raw HTML — do NOT wrap in `<![CDATA[...]]>`, do NOT escape as `&lt;` / `&gt;`, and do NOT include tool-call scaffolding tags (e.g. `<parameter name=\"...\">...</parameter>`, `<invoke>`, `<function_calls>`). BD stores the field value verbatim; any wrapper / escape / scaffolding renders as literal visible text."New value: +"Short description shown under the user's name on search result pages. **170-char limit.**"

Previous value: -"Sub-categories for this member. Format: `category=>service1,service2` OR `service1,service2` (top category defaults to the member's current `profession_id`). Supports sub-sub-categories via `Parent=>Child` (e.g. `Honda=>2022,Honda=>2023,Toyota`). Unknown names are silently ignored unless `create_new_categories=1` is also set. WARNING: changing `profession_id` in the same call WIPES all existing sub-category links — re-send the full `services` list to preserve them."New value: +"Sub-categories for this member. Formats: `category=>service1,service2` OR `service1,service2` (top category defaults to member's current `profession_id`). Supports sub-sub-categories via `Parent=>Child` (e.g. `Honda=>2022,Honda=>2023,Toyota`).\n\nUnknown names silently ignored unless `create_new_categories=1` is also set (on update - create auto-creates always).\n\n**WARNING:** changing `profession_id` in the same call WIPES all existing sub-category links. Re-send the full `services` list to preserve them."

Previous value: -"Date the user signed up. Format: `YYYYMMDDHHmmss` (14-digit timestamp, no separators — e.g. `20260419143022` for 2026-04-19 14:30:22). Auto-filled by BD on create — omit unless backfilling a legacy signup date during import/migration."New value: +"User signup date. Format: `YYYYMMDDHHmmss` (14-digit, no separators - e.g. `20260419143022`). Auto-filled by BD on create - omit unless backfilling legacy signup dates during import/migration."

Previous value: -"If YES, a verified icon badge will display on the user's listing.\\n\\nValid values:\\n  1 = Yes\\n  0 = No"New value: +"If YES, a verified icon badge will display on the user's listing.\\n\\nValid values:\\n 1 = Yes\\n 0 = No"

Added value: +{
+  "description": "Set to `1` to enable auto-creation of unknown category/service names during this `updateUser` call. Without this flag, unknown names in `services` or `profession_name` are silently skipped. Has no effect on `createUser` (which always auto-creates). Auto-created sub-categories go under the member's current top-level category with `master_id=0`; deeper nesting requires a separate `createSubCategory` call.",
+  "enum": [
+    0,
+    1
+  ],
+  "type": "integer"
+}

Added value: +{
+  "description": "Alternative to `profession_id` — pass the top-level category NAME as a string. BD looks it up in `list_professions`. On `createUser`, unknown names are auto-created. On `updateUser`, unknown names are silently skipped unless `create_new_categories=1` is also passed.",
+  "type": "string"
+}