POST/v1/entity/resolve1 unit+GET/v1/entity/{id}/edges2 units

Entity index

Walk the graph behind LeadLeap. Resolve a known string to a token, then list related tokens. Use it to get emails, phones, and LinkedIn profiles associated with a domain.

Resolve

curl -X POST https://data.leadleap.net/v1/entity/resolve \
  -H "Authorization: Bearer $LEADLEAP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind": "company.domain", "value": "awipanels.com"}'

Response carries a token_id. 404 if not in the index; 400 with the accepted-kinds list if the kind is unknown.

Walk

curl -H "Authorization: Bearer $LEADLEAP_KEY" \
  "https://data.leadleap.net/v1/entity/<token_id>/edges?kinds=person.email,person.phone"

kinds filters the peer side (CSV). limit caps at 100.min_weight=2 trims long-tail single-row co-sightings.

Use it as the contacts substitute, for now. While /v1/contacts/search is being populated, this is the path from a domain to its associated people. When contacts/search ships rows, that becomes the recommended call; the entity endpoints stay alive for everything else.

Full kind list lives in /v1/schema.