canonical: https://jentic.com/apis/europace.de/europace

# Europace De Vorgänge API

The Europace Vorgänge API reads mortgage cases (Vorgänge) from the Europace Baufinanzierung platform and lets your system act on them. It lists every case visible to the caller with an aenderungSeit filter for incremental sync, returns a single case by vorgangsNummer, and walks down to the loan applications (Anträge) and individual sub-applications attached to it. It also sets the status of a sub-application and reassigns the customer adviser (Kundenbetreuer) or case handler (Vorgangsbearbeiter) by partnerId.

## For AI agents

List and read Europace mortgage cases and their loan applications, set an application's status, and reassign the adviser or case handler on a case.

## Scope

Does not handle creating new cases, uploading documents, loan pricing, or payment servicing. Use for reading Europace mortgage cases and updating application status and case ownership only.

## Capabilities

- List all visible mortgage cases with paging, sort order, and an aenderungSeit timestamp to fetch only cases changed since a given date
- Switch between live and test data with the datenKontext parameter (ECHT_GESCHAEFT or TEST_MODUS)
- Retrieve one case by its vorgangsNummer
- Walk a case's loan applications and drill into a specific sub-application by antragsNummer and teilantragsNummer
- Set the status of a sub-application, recording the antragsteller and produktAnbieter positions with optional rejection reasons and a kommentar
- Reassign the Kundenbetreuer or Vorgangsbearbeiter on a case by passing a partnerId

## Use cases

### Agent-driven mortgage case sync through Jentic

A broker back-office agent keeps a local CRM in step with Europace by polling GET `/v1/vorgaenge` with aenderungSeit set to the last sync time, then fetching each changed case by vorgangsNummer. Through Jentic the agent finds these operations by intent, the OAuth2 client credentials stay in the developer's own Jentic One instance, and a rule can keep the agent on read operations only.

Example prompt: Call GET `/v1/vorgaenge` with aenderungSeit '2026-11-08' and datenKontext 'ECHT_GESCHAEFT', then call GET `/v1/vorgaenge/{vorgangsNummer}` for each returned case

### Loan application status updates

When a product provider decides on a sub-application, the status can be written back to Europace with POST on the sub-application's status path. The request body requires both the antragsteller and produktAnbieter positions and accepts rejection reasons and a kommentar, so the case history on Europace reflects the decision without manual entry.

Example prompt: Call GET `/v1/vorgaenge/AB1234/antraege` to find the antragsNummer and teilantragsNummer, then POST `/v1/vorgaenge/AB1234/antraege/{antragsNummer}/{teilantragsNummer}/status` with antragsteller, produktAnbieter, and a kommentar

### Case ownership handover

When an adviser leaves or a workload is rebalanced, the case can be moved to a new owner. GET `/v1/vorgaenge/{vorgangsNummer}/kundenBetreuer` and GET `/v1/vorgaenge/{vorgangsNummer}/vorgangsBearbeiter` show the current people on the case, and the matching PUT operations take a partnerId to reassign the customer adviser or the case handler.

Example prompt: Call GET `/v1/vorgaenge/AB1234/kundenBetreuer` to read the current adviser, then PUT `/v1/vorgaenge/AB1234/kundenBetreuer` with partnerId 'XY987' to reassign the case

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/vorgaenge` | List all visible cases |
| GET | `/v1/vorgaenge/{vorgangsNummer}` | Retrieve one case |
| GET | `/v1/vorgaenge/{vorgangsNummer}/antraege` | List the applications on a case |
| GET | `/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}` | Retrieve one sub-application |
| POST | `/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}/status` | Set a sub-application status |
| PUT | `/v1/vorgaenge/{vorgangsNummer}/kundenBetreuer` | Reassign the customer adviser |
| PUT | `/v1/vorgaenge/{vorgangsNummer}/vorgangsBearbeiter` | Reassign the case handler |

## Key resources

- **Vorgänge (cases)** — Mortgage cases on the Europace platform, listed with paging and change filters and read by vorgangsNummer
- **Anträge (applications)** — Loan applications and sub-applications attached to a case, with a settable status
- **Kundenbetreuer and Vorgangsbearbeiter** — The customer adviser and case handler assigned to a case, identified by partnerId

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 85 / 100
  - AI Discoverability: 41 / 100
- **View full report:** https://jentic.com/apis/europace.de/europace/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Europace Vorgänge API by hand means running the OAuth2 client credentials exchange, requesting the right baufinanzierung scopes, and refreshing tokens yourself. Through Jentic you install once, import the API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Europace puts the vorgangsNummer in the URL path of every case-level operation, so a rule can pin your agent to one case and the operations you pick. You choose the operations it may call, so write actions like setting an application status or reassigning the Kundenbetreuer are not included unless you add them.
- **Credential handling:** Your Europace client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list changed mortgage cases' or 'set application status', and Jentic returns the matching Europace operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **nCino Mortgage API** — Mortgage origination platform API for loan files and borrower data
- **LoanPro API** — Loan servicing platform for managing loans after origination

## FAQ

### Is there a Europace MCP server?

You don't need an MCP server to give your agent the Europace Vorgänge API. Jentic connects it directly from the API Directory: import it, store your OAuth2 client credentials once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### What authentication does the Europace Vorgänge API use?

Per its OpenAPI spec, the Europace Vorgänge API uses OAuth2 with the client credentials flow against the Europace token endpoint. The spec declares scopes such as baufinanzierung:vorgang:lesen for reading cases and baufinanzierung:vorgang:schreiben for writing. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and injected at execution time, so they never enter the agent's context.

### Can I limit what my agent is allowed to do with the Europace Vorgänge API?

Yes. For example, write a rule that allows GET `/v1/vorgaenge/AB1234` and GET `/v1/vorgaenge/AB1234/antraege`, so the agent can read that one case and its applications while status changes and adviser reassignment stay out of reach. Every call it makes is logged on your own machine.

### How do I fetch only the cases that changed since my last sync?

Pass the aenderungSeit query parameter to GET `/v1/vorgaenge` in ISO 8601 format, such as 2026-11-08 or 2026-11-08T13:00Z. Combine it with page and limit to walk the results, and use sort to choose ascending or descending order.

### How do I set an application status through Jentic?

Install Jentic One, import the Europace Vorgänge API from the directory, and search for 'set Europace application status'. Jentic returns the setAntragsStatus operation with its input schema; supply the vorgangsNummer, antragsNummer, and teilantragsNummer plus the required antragsteller and produktAnbieter fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I work with test data instead of live cases?

Yes. GET `/v1/vorgaenge` accepts a datenKontext query parameter with the values ECHT_GESCHAEFT (the default, live business) and TEST_MODUS, so you can point an agent at test cases while you build the integration.

### What are the rate limits for the Europace Vorgänge API?

The OpenAPI spec does not specify rate limits. Check the Europace developer documentation at https://docs.api.europace.de for current limits.