Leads in JSONLead format: specification
JSONLead lead specification: fields and delivery methods via email, webhook or SFTP.
Automating your sales flow and connecting it with your management system or ERP has never been so easy. With our system, every lead generated on the portal is sent in a structured way so you can process it automatically without complications. Here we explain how it works and how you can implement this integration.
Delivery format: JSONLead as a market standard
To guarantee compatibility and ease of integration, we use the JSONLead format. This format is widely recognised in the market and makes the automatic processing of sales in third-party systems easier.
Available delivery methods
You have three options for receiving leads. In every case the content of the lead in json format will be the same.
- Webhook: The fastest and most direct option. Leads are sent immediately to your system's URL configured to receive them (POST request). If for security reasons you need any kind of custom header, we can add it without any problem.
- SFTP/FTP: You can use our SFTP server or your own (SFTP/FTP) to receive the data. One json file will be created per lead.
- Email: If you prefer, we can send you the leads in JSONLead format as the body of emails.
Example of a JSONLead sent
{
"client": {
"foreign_id": "1df807f0ba96f8be5529308f6667a144",
"first_name": "John",
"postal_code": "76119",
"phone": "600000000",
"email": "user@mail.com"
},
"sales_lead": {
"origin": {
"source": "portal_hero",
"medium": "Ebay"
},
"related_urls": [
"https://portal.com/item/1234"
],
"custom": {
"account": "some_email@mail.com",
"external_id": "1243948",
"title": "Some pretty product",
"created_at": "2025-01-17 10:25:22.145432"
},
"foreign_id": "17-12583-30383",
"inquiry": "[{\"created_at\": \"2022-10-31T20:03:21.360000\",\"text\": \"Te dejo mi numero de telefono 6XXXXXXXXX\"}, {\"created_at\":\"2022-10-31T19:50:55.194000\", \"text\": \"Hola!\"}]"
},
"version": "1.0.0"
}
JSONLead field details
| Name | Type | Required | Description |
|---|---|---|---|
client.foreign_id | string | Yes | Unique identifier of the customer. |
client.first_name | string | Yes | Customer's name. Depending on the portal it may be a username. |
client.postal_code | string | No | Postcode of the customer's address. |
client.phone | string | No | Customer's phone number. |
client.email | string | No | Customer's email. |
sales_lead.origin.source | string | Yes | Origin of the sale. It will always be "portal_hero". |
sales_lead.origin.medium | string | No | Name of the portal the sale comes from. |
sales_lead.related_urls | array | No | Relevant URL(s). Normally the URL of the item on the portal. |
sales_lead.custom.account | string | No | Email or identifier of the account on the portal. Useful when multiple accounts are managed on the same portal, to identify the account the sale originated from. |
sales_lead.custom.external_id | string/arraystring* | Yes | Unique identifier of the item. The same one you send us when uploading items. |
sales_lead.custom.title | string/arraystring* | Yes | Title of the product sold. |
sales_lead.custom.created_at | datetime | Yes | Date and time the sale was created. |
sales_lead.foreign_id | string | Yes | Unique identifier of the sale. |
sales_lead.inquiry | array | No | Conversation held with the user on the portal. |
version | string | Yes | Version of the jsonLead schema. Version 1.0.0 for now. |
Benefits of this integration
- Complete automation: Automatically process leads in your management system.
- Standardisation: The JSONLead format ensures compatibility with most systems on the market.
- Flexibility: Choose between webhook, SFTP or email according to what best suits your needs.
Integrate this solution into your workflow and streamline the management of your leads quickly, accurately and easily. If you need more details or technical support, get in touch! 🚀