Skip to content

plazatechnologies/lead-documentation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 

Repository files navigation

Lead Creation Webhook Documentation

Overview

This documentation describes how to create a webhook to receive our leads. Our leads will be sent to the webhook via the payload described in the Request Body Parameters below. You must provide us the required {{realEstateID}} and a valid authorization token to successfully receive these leads.

Endpoint

Method: POST

Production URL: https://plaza.services/api/public/v1/leads/webhook/{{realEstateID}}

Replace {{realEstateID}} with the unique identifier of the real estate.

Headers

Header Value Description
Content-Type application/json Indicates the request body is in JSON format.
Authorization Bearer <YOUR_TOKEN> Provide a valid bearer token or agreed-upon secret.

URL Parameters

Parameter Type Required Description
realEstateID string Yes The unique ID of the real estate. This must be included in the request URL.

Request Body Parameters

NOTE: ALL fields must accept all strings.

E.G. The field cpf/cnpj can be "not mentioned" and the field visitDate can be "as soon as possible".

Field Type Required Description
clientListingId string No Internal listing ID.
email string No Lead’s email address.
name string Yes Lead’s full name.
ddd string Yes The area code of the lead's phone number.
phone string Yes The lead’s phone number (excluding area code).
transactionType string No Type of transaction: rent or sale.
origin string No Source of the lead. Possible values: WhatsApp, GrupoZap, ImovelWeb, ChavesNaMaoLais, VivaReal.
leadSummary string No A short summary highlighting the lead’s key details and interests.
leadPreferences string No Specific property preferences indicated by the lead.
listingLink string No URL pointing to the associated listing.
cpf/cnpj string No The lead’s CPF or CNPJ (Brazilian ID numbers).
intendedMoveDate string No The date the lead intends to move.
conversation string No A URL linking to a conversation transcript with the lead.
visitDate string No The date the lead plans to visit the property.
message string No A message containing all lead info.

Example Request

POST <https://plaza.services/api/public/v1/leads/webhook/12345>
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

{
  "clientListingId": "ABC123",
  "email": "lead@example.com",
  "name": "John Doe",
  "ddd": "11",
  "phone": "999999999",
  "transactionType": "sale",
  "origin": "WhatsApp",
  "leadSummary": "Interessado em apartamentos de 2 quartos.",
  "leadPreferences": "Sala ampla com varanda, em um bairro tranquilo.",
  "listingLink": "https://listing.example.com/property/ABC123",
  "cpf/cnpj": "123.456.789-00",
  "intendedMoveDate": "2025-01-15",
  "conversation": "https://useplaza.comv.br/conversations/123",
  "visitDate": "2024-12-20-12:10:30 -03:00",
  "message": "💼 Quem é John Doe? \nNão informado\n\n🏢 Quais são suas necessidades? \nEstá em busca de um apartamento de 2 quartos, com sala ampla e varanda, em um bairro tranquilo.\n\n📅 Data da visita: 26/02/2025\n\n*CPF/CNPJ*: 123.456.789-00\n\n🚛 Quando planeja se mudar: 01/04/2025\n\nOrigem: Facebook\n\n🏭 Imóvel : 
              https://exemplo.com.br/imovel/1234\n\nCódigo do Imóvel: 1234\n\nPrimeiro Imóvel de Interesse: 5678\n\n💬 Ver Conversa: [Ver conversa](https://exemplo.com.br/conversa/9876)\n\nStatus do Lead: Aguardando aprovação"
}

Responses

201 Created

When a lead is successfully created, the response includes detailed information about the new lead. This helps the caller confirm the correct processing of the data and provides a reference for future interactions.

PS: Please always return the lead_id created on your system.

Example Response Body for 201 Created:

{
  "status": "success",
  "message": "Lead created successfully.",
  "data": {
	  "clientListingId": "ABC123",
	  "email": "lead@example.com",
	  "name": "John Doe",
	  "ddd": "11",
	  "phone": "999999999",
	  "transactionType": "sale",
	  "origin": "WhatsApp",
	  "leadSummary": "Interessado em apartamentos de 2 quartos.",
	  "leadPreferences": "Sala ampla com varanda, em um bairro tranquilo.",
	  "listingLink": "https://listing.example.com/property/ABC123",
	  "cpf/cnpj": "123.456.789-00",
	  "intendedMoveDate": "2025-01-15",
	  "conversation": "https://useplaza.comv.br/conversations/123",
	  "visitDate": "2024-12-20-12:10:30 -03:00"
	}
}

400 Bad Request

This response is returned when the request fails due to incorrect input or missing required fields. It specifies the exact errors, enabling the caller to correct them and retry the request.

Example Response Body for 400 Bad Request:

{
  "status": "error",
  "message": "Request validation failed.",
  "errors": [
    {
      "field": "phone",
      "message": "Phone number is required."
    },
    {
      "field": "name",
      "message": "Name is required."
    }
  ]
}

About

“Public documentation for clients and third parties”

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •