Three calls
From key to webhook
Paste these in order. The third one is where most integrations actually begin.
bash
# 1. Exchange your key for a token curl -X POST https://api.qubi360.com/v2/auth/token \ -H "Content-Type: application/json" \ -d '{"api_key": "YOUR_KEY"}' # 2. Read the leads your token can see curl https://api.qubi360.com/v2/leads?limit=25 \ -H "Authorization: Bearer $TOKEN" # 3. Get notified when one converts curl -X POST https://api.qubi360.com/v2/webhooks \ -H "Authorization: Bearer $TOKEN" \ -d '{"event": "lead.converted", "url": "https://your-app/hook"}'
Common endpoints
What you will reach for first
GET
/v2/leads
List leads, filtered by owner, source or status
POST
/v2/leads
Create a lead; assignment rules still apply
GET
/v2/projects/{id}
One project with its tasks, budget and team
GET
/v2/timelogs
Approved time, filterable by project or person
POST
/v2/invoices
Raise an invoice from approved time
POST
/v2/webhooks
Subscribe to an event; delivery is retried for 24 hours
Before you build
Two things worth knowing
Tokens inherit roles, and webhooks retry
A token can never read more than the role attached to it, so an integration cannot quietly widen its own access. Webhook deliveries retry with backoff for twenty-four hours, then land in a dead-letter queue you can replay from the admin screen.