Skip to main content

List leads by RUT

POST 
/partner/lead/batch

Returns every one of your leads for a batch of RUTs, in one call. Each row is exactly a row of List leads, plus the rut it was found for — so you can sync the people you already track without paging through your whole grid.

Requires the evaluation module.

What the batch returns​

  • Every lead per RUT, not just the latest. A person who entered your funnel more than once has one row per lead. Rows come newest first across the whole batch.
  • Only your leads. A RUT that also exists under another partner returns only the leads that came in through your own PartnerEntities.
  • Same scope as the list. Archived leads are included; leads with any BNPL pre-approval are excluded. resultado, idPreAprobacion and vigenteHasta resolve the same way, with the same caveats.
  • A RUT with no leads is not an error. It simply contributes no rows, and a batch where no RUT matches returns { "items": [], "total": 0 }. Compare the rut of the rows against what you sent to see which RUTs had none.
  • RUTs are normalised. 15.888.222-3, 15888222-3 and 158882223 are the same RUT, and a RUT sent twice is looked up once.

Why POST​

RUTs are personal data and do not belong in a URL, where proxies and access logs keep them. This is a read: it changes nothing and can be retried safely.

There is no pagination. total is the number of rows returned, and the batch size is capped instead: send at most 100 RUTs per request.

Request​

Responses​

Leads retrieved successfully