Track results
After the call, read back where each lead ended up, what they said and when they are coming in, and copy it into your CRM, sheet or team chat.
Lead statuses
A lead's status says where it is. Progz moves it along as the call happens and your rules decide, so your code normally just reads it.
| status | Meaning | Final? |
|---|---|---|
new | Created, no call asked for yet. | No |
contacting | A call is queued, ringing or happening (or waiting for calling hours). | No |
qualifying | Being qualified. | No |
qualified | Fits your rules, but nothing is booked yet. Your team gets a task to follow up. | No |
nurture | Right fit, wrong time. Called again after the offering's follow-up period. | No |
needs_review | Answers were unclear or something needs a person. Your team gets a task in the app. | No |
demo_booked | Booked: a demo, site visit, campus visit or appointment, depending on your business. | Yes (the booking itself can still be cancelled) |
not_fit | Doesn't meet your rules. | Yes |
not_interested | Said no, or didn't agree to the call. | Yes |
closed | Your team closed it after a review, for example after three calls nobody answered. | Yes |
Your team can also change a status by hand in the app, so read it rather than assuming the next step.
interest adds what the person said about wanting it: interested, not_interested or call_back_later (they asked to be called back, and will be).
One lead after the call
Read a lead by its id. Its facts now include what the person said on the call, and call_timing shows how fast the call went out:
curl "https://progz.in/api/v1/leads/3f6c2a1e-8b4d-4c1a-9e2f-5d7b8a9c0e11" \
-H "Authorization: Bearer $PROGZ_API_KEY"{
"id": "3f6c2a1e-8b4d-4c1a-9e2f-5d7b8a9c0e11",
"status": "demo_booked",
"interest": "interested",
"facts": {
"product_interest": "3 BHK",
"budget_inr": 6500000,
"purchase_timeline_days": 60,
"needs_financing": true,
"interested": true
},
"call_timing": {
"requested_at": "2026-10-24T06:30:12Z",
"scheduled_for": "2026-10-24T06:30:12Z",
"started_at": "2026-10-24T06:30:41Z",
"seconds_to_call": 29,
"held_for_hours": false
},
…
}call_timing.held_for_hours is true when the call waited for your calling hours rather than being slow. To find leads without keeping ids, list them with filters: GET /leads?status=demo_booked, ?offering_id=…, ?contact_id=…, or ?q= with a name or phone number. Lists are newest first and page with limit and offset.
Bookings
Every booking is an appointment. List the ones still to come, soonest first; subject_id is the lead it belongs to:
curl "https://progz.in/api/v1/appointments?upcoming=true&status=scheduled&limit=100" \
-H "Authorization: Bearer $PROGZ_API_KEY"{
"items": [
{
"id": "d4e5f6a7-b8c9-4d0e-9f1a-2b3c4d5e6f70",
"kind": "demo",
"label": "Site visit",
"title": "Site visit: 3 BHK apartments, Kondapur — Ravi Kumar",
"status": "scheduled",
"start_at": "2026-10-28T04:30:00Z",
"end_at": "2026-10-28T05:00:00Z",
"timezone": "Asia/Kolkata",
"contact_id": "9e8d7c6b-5a49-4382-9170-6f5e4d3c2b1a",
"contact_name": "Ravi Kumar",
"employee_id": "65da53ba-cbf3-48f0-ae83-b5c17fb445fc",
"employee_name": "Priya",
"subject_type": "lead",
"subject_id": "3f6c2a1e-8b4d-4c1a-9e2f-5d7b8a9c0e11",
"conversation_id": "7c1d2e3f-4a5b-4c6d-8e9f-0a1b2c3d4e5f",
"cancelled_at": null,
"cancel_reason": null,
…
}
],
"total": 1,
"limit": 100,
"offset": 0
}- Times are UTC;
timezoneis the business's, for showing them.04:30Zis 10:00 in India. statusisscheduled,cancelled,completedorno_show. Use?past=truefor ones that have ended, latest first, and?contact_id=or?subject_id=for one person.- To cancel one from your system:
POST /appointments/{id}/cancelwith an optionalreason(amemberkey).
Calls: summary and transcript
Each call is a conversation. List a person's calls, then open one for its summary and transcript:
# The calls with this person, newest first
curl "https://progz.in/api/v1/conversations?contact_id=9e8d7c6b-5a49-4382-9170-6f5e4d3c2b1a&channel=phone" \
-H "Authorization: Bearer $PROGZ_API_KEY"
# One call in full: summary, transcript, what the AI employee did
curl "https://progz.in/api/v1/conversations/7c1d2e3f-4a5b-4c6d-8e9f-0a1b2c3d4e5f" \
-H "Authorization: Bearer $PROGZ_API_KEY"- In the list:
status(queued,ringing,in_progress,completed,no_answer,busy,failed,cancelled),outcome,duration_seconds, andescalatedwhen it was handed to your team. - In one conversation:
summary,transcript, andtool_calls(what the AI employee looked up or booked during the call).
Keeping your system up to date
Progz doesn't send webhooks yet, so your system asks for changes on a schedule. Every 5 to 15 minutes is plenty: calls take a few minutes, and bookings are for later days. Two checks cover almost everything:
- New and cancelled bookings: page through
GET /appointments?upcoming=true, and compare the appointment ids with the ones you already have. - Leads still in play: read each lead you sent in that hasn't reached a final status (
demo_booked,not_interested,not_fit,closed), and save its status and facts. Stop tracking it once it is final.
"""Every few minutes: copy new bookings and finished leads into your own system."""
import os
import time
import requests
API = "https://progz.in/api/v1"
HEADERS = {"Authorization": f"Bearer {os.environ['PROGZ_API_KEY']}"}
FINAL = {"demo_booked", "not_interested", "not_fit", "closed"}
def get(path, **params):
while True:
r = requests.get(f"{API}{path}", headers=HEADERS, params=params, timeout=30)
if r.status_code == 429: # rate limited: wait as told, then retry
time.sleep(int(r.headers.get("Retry-After", "5")))
continue
r.raise_for_status()
return r.json()
def sync_bookings(seen_ids: set[str]) -> None:
offset = 0
while True:
page = get("/appointments", upcoming="true", limit=200, offset=offset)
for a in page["items"]:
if a["id"] not in seen_ids: # a booking you haven't copied yet
save_booking(a) # your code: CRM, sheet, Slack …
seen_ids.add(a["id"])
elif a["status"] == "cancelled":
mark_cancelled(a) # your code
offset += page["limit"]
if offset >= page["total"]:
return
def sync_open_leads(open_lead_ids: list[str]) -> None:
for lead_id in open_lead_ids: # leads you sent in that haven't finished
lead = get(f"/leads/{lead_id}")
save_lead_status(lead) # your code: status, facts, interest
if lead["status"] in FINAL:
stop_tracking(lead_id) # your codeRetry-After on a 429, as above. Lists have no "changed since" filter, so track the ids you care about instead of re-reading every lead.Numbers for reports
For a dashboard, ask for the totals instead of counting leads yourself. days is 1 to 365, counted in the business's time zone; add employee_id for one AI employee:
curl "https://progz.in/api/v1/leads/results?days=30" \
-H "Authorization: Bearer $PROGZ_API_KEY"{
"days": 30,
"start": "2026-09-24T18:30:00Z",
"timezone": "Asia/Kolkata",
"enquiries": 412,
"called": 398,
"reached": 301,
"interested": 142,
"booked": 96,
"not_interested": 88,
"not_fit": 31,
"needs_review": 12,
"later": 27,
"in_progress": 18,
"by_offering": [{ "label": "3 BHK apartments, Kondapur", "enquiries": 260, "reached": 190, "interested": 95, "booked": 64 }],
"by_interest": [ … ],
"by_branch": [ … ]
}Each count is about leads that came in during the period: how many were called, reached (answered), interested (qualified or booked) and booked, split by offering, by what they wanted (product_interest) and by branch. GET /leads/upcoming?days=7 gives the coming week's visits in a ready-to-print shape: name, phone, time, what they want and branch.
Next
New to the API? Start with Send in leads. For error codes and retries, see Errors, limits & paging.