Lead Data API Server

Multi-database lead management API for n8n workflow integration

API Overview

This API server provides lead data management across multiple simulated databases with API key authentication.

Authentication Required: All API endpoints require a valid API key in the Authorization header using Bearer token format.

API Endpoints

GET /api/lead/{database}/{leadCallId} Check if lead exists

POST /api/lead/{database} Store lead data

PATCH /api/lead/{database}/{leadCallId} Update existing lead data

DELETE /api/lead/{database}/{leadCallId} Delete lead data

GET /api/health Health check (no auth)

Authentication

Include your API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Set your API_KEY environment variable in Replit secrets.

Example Usage

Check if lead exists:

GET /api/lead/krise/lead123
Authorization: Bearer your-api-key

Store lead data:

POST /api/lead/sales
Authorization: Bearer your-api-key
Content-Type: application/json

{
  "leadCallId": "lead456",
  "name": "John Doe",
  "email": "john@example.com"
}

Update lead data:

PATCH /api/lead/sales/lead456
Authorization: Bearer your-api-key
Content-Type: application/json

{
  "leadCallId": "lead456",
  "name": "Jane Doe",
  "email": "jane@example.com",
  "phone": "+1-555-0123"
}

Delete lead data:

DELETE /api/lead/sales/lead456
Authorization: Bearer your-api-key

API Status

API Server Running Ready for n8n workflow integration