Lead intake URL

​

Get your URL

https://app.manypi.com/api/integrations/inbound/<your-token>

​

Send leads

curl -X POST https://app.manypi.com/api/integrations/inbound/<your-token> \
  -H "Content-Type: application/json" \
  -d '{"email":"sam@acme.com","first_name":"Sam","company":"Acme","custom":{"icebreaker":"Loved your post on pricing"}}'

curl -X POST https://app.manypi.com/api/integrations/inbound/<your-token> \
  -H "Content-Type: application/json" \
  -d '[{"email":"sam@acme.com","company":"Acme"},{"email":"ana@globex.com","company":"Globex"}]'

curl -X POST https://app.manypi.com/api/integrations/inbound/<your-token> \
  -H "Content-Type: application/json" \
  -d '{"campaign_id":"<campaign-id>","leads":[{"email":"sam@acme.com","company":"Acme"}]}'

• Field names are forgiving. “Company Name”, “companyName” and “company” all land in Company, the same as a CSV header.
• Custom variables go under custom. Each key there becomes a custom variable the first time it is seen. Other unknown keys are kept only if a custom variable with that name already exists, so a payload full of metadata does not create dozens of columns.
• Up to 100 leads per request. Plan lead limits apply as for any import.
• Duplicates follow the connection’s setting under More settings: merge (the default), overwrite, or skip.
• campaign_id adds the new leads to that campaign, with the same checks as adding them by hand.

{
  "created": 1,
  "updated": 0,
  "skipped": 0,
  "over_limit": 0,
  "lead_ids": ["8c1f…"]
}

​

Common setups