get
https://connect.agendapro.com/v3/leads/
This endpoint returns a single lead.
Important Notes
- Requires
leads:readscope. - Served by Cortex, AgendaPro's conversational agent. Phones are returned exactly as stored (e.g.
+521…for numbers that came from WhatsApp in Mexico); they are not normalized. meta_ad_idandmeta_source_typeinnullare a legitimate absence (the campaign is not a Meta ad, it is a Meta post, or no conversation matches), never a failure: when the campaign source cannot be resolved, the request answers502and you retry it.
Errors Dictionary
| Status | Error | Detail | Description |
|---|---|---|---|
| 401 | unauthorized | invalid_api_key | Missing or invalid Bearer token. |
| 401 | unauthorized | api_config_inactive | API access is inactive for this company. |
| 403 | forbidden | scope_denied | API key lacks leads:read scope. |
| 403 | forbidden | company_not_enabled | The company is not enabled to read Cortex data through this API. Contact AgendaPro to enable it; retrying does not help. |
| 404 | not_found | lead | Lead not found, or it belongs to another company. |
| 429 | rate_limited | burst_limit_exceeded | Per-minute request limit exceeded. |
| 429 | rate_limited | daily_quota_exceeded | Daily request quota exceeded. |
| 502 | upstream_unavailable | The upstream service is unavailable. | |
| 502 | upstream_unavailable | upstream_misconfigured | AgendaPro's internal connection to Cortex is misconfigured. It is not a problem with your API key; retry later or contact support. |
| 502 | upstream_unavailable | upstream_error | Cortex answered an error, for example because it could not resolve the source of a campaign in the response (AgendaPro's channels broker failed, answered an error or did not answer in time). The whole page fails; retry the same request. |
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…