Skip to main content

Real Estate Testing in Automation

In production, a real-estate lead is created and evaluated by the client: the person opens creditos.banca.me from your link, enters their RUT, authenticates with Clave Única, completes their data and receives a pre-approval. You cannot drive that flow from a test pipeline.

To let you test your integration end to end without a real person, the automation environment exposes three extra endpoints that emulate what the client does in creditos.banca.me:

EndpointEmulates
POST /automation/real-estate/leadThe client entering their RUT in creditos.banca.me — a lead is created.
POST /automation/real-estate/pre-approve/{plrId}The client completing the flow — the lead is evaluated and pre-approves are generated.
POST /automation/real-estate/complement/{plrId}An income co-applicant invited by the client completing the flow — the lead is evaluated again with both incomes.
These endpoints exist only in automation

/automation/real-estate/* is available only at https://automation.api.banca.me. In every other environment, including production, it responds 404 ERR_ENDPOINT_NOT_AVAILABLE.

Do not build them into your production integration: they are a test harness that stands in for the client. In production the client always goes through creditos.banca.me, and you only receive the result through webhooks and read it through the API.

What you can test​

The point of these endpoints is not the endpoints themselves — it is everything that happens because a lead was created and evaluated. With them you can test:

  1. Your webhooks. Creating a lead fires new_lead, and generating its pre-approves fires pre_approve, exactly as they would in production, to the destinations you registered with POST /partner/webhook/subscription.
  2. Your API integration. Once the lead exists, read it back by RUT with the regular partner API — for example Get All Leads by ID Number, Get Pre-Approve by RUT or Get Leads by RUTs.
  3. Client re-entry. Repeating the flow with the same RUT archives the previous lead and creates a new one, the same as a person who comes back to creditos.banca.me. See Re-entry.
  4. Complements. Complement a lead rejected for income with a co-applicant and check what your webhooks and the API report. See Complement a lead.

How the evaluation is mocked​

Only the client's data is mocked; your real risk policies are still evaluated.

When you generate pre-approves, banca.me does not query bureaus, Clave Única or any other data source. Instead it loads a fixed risk profile chosen by the lead's RUT — a healthy profile for any RUT, or a negative one for the documented test RUTs — and then runs the same evaluation as production against the risk policies configured for your project. The outcome is therefore deterministic: the same RUT always produces the same result.

Prerequisites​

  • An API key for the automation environment (the same key you use for the partner API there).
  • The origin label of the project you want the leads created in.
  • Your partner has the evaluation module enabled — both new_lead and pre_approve require it (see Which Webhook Integration Is Yours).
  • To test webhooks: a destination registered in automation with POST /partner/webhook/subscription, subscribed to new_lead and/or pre_approve.

Continue with the Operating Guide.