Send every lead where your team already works, and bring the outcome back.

GET /v1/me

The account this key opens: its id, company name, dashboard address, the key's label and the events you can subscribe to. Use it as the connection test.

curl https://trulata-product-api.onrender.com/v1/me \
  -H "Authorization: Bearer $TRULATA_KEY"

GET /v1/leads

Your leads, newest first, each with a stable id. limit takes up to 100 (default 50). days looks back up to 365 days (default 30).

curl "https://trulata-product-api.onrender.com/v1/leads?limit=10&days=7" \
  -H "Authorization: Bearer $TRULATA_KEY"

GET /v1/leads/search

Find a lead by email or by phone, across the last 365 days. Phone numbers match on their last ten digits, so formatting does not matter.

curl "https://trulata-product-api.onrender.com/v1/leads/search?email=jordan@example.com" \
  -H "Authorization: Bearer $TRULATA_KEY"

curl "https://trulata-product-api.onrender.com/v1/leads/search?phone=4055550142" \
  -H "Authorization: Bearer $TRULATA_KEY"

POST /v1/leads

Add a lead. It lands on your Leads tab like a website form message. Send name, or first_name and last_name, plus any of email, phone, service, message and source. A lead needs at least a name, an email or a phone. notify defaults to true, which emails the owner the same way a website form lead does; send false to skip it.

curl -X POST https://trulata-product-api.onrender.com/v1/leads \
  -H "Authorization: Bearer $TRULATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name": "Jordan", "last_name": "Example",
       "email": "jordan@example.com", "phone": "405-555-0142",
       "service": "Water heater replacement",
       "message": "Leaking since this morning. Can someone come out this week?",
       "source": "Zapier", "notify": true}'

Response

{
  "ok": true,
  "lead": {
    "id": "ld_3f9a1c2b7d4e5f6a8b9c",
    "created_at": "2026-10-21T09:14:00-04:00",
    "name": "Jordan Example",
    "email": "jordan@example.com",
    "phone": "405-555-0142",
    "service": "Water heater replacement",
    "message": "Leaking since this morning. Can someone come out this week?",
    "town": "",
    "page": "",
    "source": "Zapier",
    "quality": "",
    "status": "",
    "status_note": ""
  }
}

POST /v1/leads/{id}/status

Set a lead's outcome: contacted, quoted, won, lost or not_lead, with an optional note. It is the same record the Leads tab shows, so an outcome set here appears on the screen. The id comes from a new lead, a list or a search.

curl -X POST https://trulata-product-api.onrender.com/v1/leads/ld_3f9a1c2b7d4e5f6a8b9c/status \
  -H "Authorization: Bearer $TRULATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "won", "note": "Signed the quote on site"}'

GET /v1/posts

Your published blog posts, newest first: id, title, url, excerpt, image_url, target_search and published_at. limit takes up to 100 (default 25).

curl "https://trulata-product-api.onrender.com/v1/posts?limit=5" \
  -H "Authorization: Bearer $TRULATA_KEY"

POST /v1/hooks

Subscribe a public https address to an event. You get back the subscription's id; keep it to unsubscribe. A key can hold up to 50 subscriptions.

curl -X POST https://trulata-product-api.onrender.com/v1/hooks \
  -H "Authorization: Bearer $TRULATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event": "lead.created", "target_url": "https://hooks.example.com/trulata/new-lead"}'

Response

{
  "ok": true,
  "id": "42",
  "event": "lead.created",
  "target_url": "https://hooks.example.com/trulata/new-lead"
}

GET /v1/hooks

The subscriptions this key holds, with when each was made, when it last sent and the status your address last answered with.

curl https://trulata-product-api.onrender.com/v1/hooks \
  -H "Authorization: Bearer $TRULATA_KEY"

DELETE /v1/hooks/{id}

Unsubscribe. Removing one that is already gone still answers ok.

curl -X DELETE https://trulata-product-api.onrender.com/v1/hooks/42 \
  -H "Authorization: Bearer $TRULATA_KEY"