Lead Metadata API
Update profile metadata for a specific lead. Metadata includes demographic and firmographic attributes such as name, company, title, and custom fields.
PATCH /lead/{leadID}/metadata
Update metadata fields on a lead. This performs a partial update -- only the fields you include in the request body are changed.
Request
| Parameter | Type | Required | Description |
|---|---|---|---|
leadID | string | Yes | Lead identifier (path parameter) |
Request Body
Provide a JSON object with the metadata fields to update. Fields not included in the request remain unchanged.
{
"first_name": "Alex",
"last_name": "Johnson",
"company": "Acme Corp",
"title": "VP Marketing",
"industry": "Technology"
}
Response
200 OK
Returns the updated lead with all current metadata.
Example
curl -X PATCH "https://api.leadvibe.com/lead/ld_123/metadata" \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d '{
"company": "Acme Corp",
"title": "VP Marketing"
}'
Common Errors
| Status | Meaning | Solution |
|---|---|---|
| 400 | Bad Request | Invalid JSON or field values |
| 401 | Unauthorized | Check authentication token |
| 404 | Not Found | Lead does not exist or not accessible |
Notes
- Metadata updates use partial merge -- existing fields not in the request are preserved
- Setting a field to
nullremoves it from the lead's metadata - Profile scoring rules may recalculate after metadata changes if mapped fields are updated
- Metadata is OU-scoped to the active Organizational Unit
Related Endpoints
- Lead Detail - View lead details
- Lead Metadata Properties - List available property keys
- Profile Mappings - Map metadata to profile scoring fields