Your first request
Create a key, send it with a request, and read a page of your organization's leads. About five minutes, start to finish.
Steps
Create an organization key
In the app, open Settings › API keys, choose New key, name it after the integration that will use it, and give it only the permissions it needs. For this guide,
leads:readis enough.Keep it out of your code
Store the key in an environment variable or your platform's secret store, never in source control:
Shell export LEADUP_API_KEY="lup_org_live_…"Send it as a bearer token
Every request carries the key in the
Authorizationheader.curl "https://api.leadup.group/v1/leads?limit=5" \ -H "Authorization: Bearer $LEADUP_API_KEY"Read the page that comes back
Lists return
itemsand anextCursor. Send the cursor back ascursorto read the next page; it isnullon the last one.200 OK { "items": [ { "id": "0192f0c1-7a3e-7c51-9d2e-4b7f0a1c2d3e", "companyName": "Clínica Sorriso Pleno", "segment": "dental", "city": "Campinas", "region": "SP", "stage": "proposal", "nextFollowUpAt": "2026-10-14T13:00:00Z" } ], "nextCursor": null }
If it fails
- 401
auth.unauthenticated: the key is missing, mistyped, revoked or expired. The API doesn't say which, on purpose. - 403
auth.forbidden: the key works but lacks the permission this endpoint needs. Create a key with it. - 429
request.rateLimited: wait for the seconds inRetry-After, then try again. See rate limits.
Next steps
- Find leads by stage, city or name.
- Move a lead through the pipeline.
- Browse every endpoint in the API reference.
Was this page helpful?