Leads

Set or correct a lead's category

Sets the lead's category (tag), typically to correct an AI misclassification of a reply. Validated against the category enum: interested, not_interested, bounced, out_of_office, delivery_incomplete, meeting_booked. Setting meeting_booked behaves exactly like POST /leads/{id}/meeting: it records meetingBookedAt when unset and keeps an existing one, because a meeting is an explicit mark set by you or your agent, never inferred by the system. A real category change fires the LeadCategoryUpdate webhook; setting the value the lead already has is a no-op. Changing the category away from meeting_booked does NOT clear the booked-meeting mark - use DELETE /leads/{id}/meeting for that.

put/leads/{id}/category

Request

Base URL: https://api.emailchaser.com/r
URL: https://api.emailchaser.com/r/leads/{id}/category
Auth: HTTP bearer

Path parameters

idinteger required

Lead ID

Request body

categorystring required

Category must be one of the lead category values: interested, not_interested, bounced, out_of_office, delivery_incomplete, meeting_booked.

Example request

{
  "category": "interested"
}

Response

Lead category updated

messagestring

Example response

{
  "lead": {
    "id": 123,
    "meetingBookedAt": "2026-07-30T14:05:00Z",
    "tag": "meeting_booked"
  },
  "message": "lead category updated successfully"
}

Changes

No recorded changes to this operation across all 1 revision of this API.