updateCity
Update an existing city row to correct typos or reassign its state/country. Requires locaiton_id. Only use for corrections; new cities are auto-seeded.
Instructions
Update a city (corrections only) - Update an existing city row. Read-mostly - use sparingly. Fields omitted are untouched (PATCH semantics - only send what you want to change).
Use when: correcting a typo in city_ln or city_filename, or reassigning a city's state_sn / country_sn if originally miscategorized. For a NEW city, DO NOT create via API - let the next member signup from that location auto-seed the row (BD handles this).
Required: locaiton_id (BD schema typo - sic).
Warning on city_filename edits: this is the URL slug used in every search-result page for that city. Changing it breaks all inbound links AND any static SEO pages (seo_type=profile_search_results) whose filename includes the old slug. If you must rename, create Redirect (301) records for each affected URL.
Returns: { status: "success", message: {...updatedRecord} }.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locaiton_id | Yes | City PK (BD typo - sic) | |
| city_ln | No | ||
| city_filename | No | URL slug. Changing this breaks inbound URLs - create redirects. | |
| state_sn | No | ||
| country_sn | No | ||
| _clear_fields | No | Column names to clear to empty string. Available on every `update*` operation. Works on base columns AND EAV/`users_meta` rows (rows preserved with `value=""`). To actually clear a field you MUST use this parameter — sending the field with `""` alone is a no-op (BD drops empty values). To remove a `users_meta` row entirely, use `deleteUserMeta`. See **Rule: Clearing fields**. Example: `_clear_fields: ["h2", "hero_link_url"]`. |