Profile Mapping by ID API
Update or delete an individual profile field mapping.
PUT /profile-mappings/{id}
Update an existing profile field mapping.
Request
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Mapping identifier (path parameter) |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
profile_field | string | Yes | Updated profile field name |
{
"profile_field": "updated_field_name"
}
Response
200 OK
{
"id": "mapping-123",
"metadata_key": "company_size",
"profile_field": "updated_field_name",
"updated_at": "2025-01-15T11:00:00Z"
}
Example
curl -X PUT "https://api.leadvibe.com/profile-mappings/mapping-123" \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d '{"profile_field": "updated_field_name"}'
Common Errors
| Status | Meaning | Solution |
|---|---|---|
| 401 | Unauthorized | Check authentication credentials |
| 404 | Not Found | Mapping does not exist |
DELETE /profile-mappings/{id}
Delete a profile field mapping. This does not delete historical profile data or scores -- it only prevents future events from being mapped to this profile field.
Request
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Mapping identifier (path parameter) |
Response
204 No Content
Example
curl -X DELETE "https://api.leadvibe.com/profile-mappings/mapping-123" \
-H "Authorization: Bearer <token>"
Common Errors
| Status | Meaning | Solution |
|---|---|---|
| 401 | Unauthorized | Check authentication credentials |
| 404 | Not Found | Mapping does not exist |
Notes
- Deleting a mapping does not affect existing profile scores or historical data
- Only future event processing is affected when a mapping is removed
Related Endpoints
- Profile Mappings - List and create profile mappings
- Profile Scoring Rules - Rules that use profile fields for scoring