UYAP connection in preparation.
The UYAP connection is not yet available. This page describes planned scope; it does not promise automatic sync, e-signature setup or inclusion in a specific plan. Available scope will be announced after the connection method and provider validation are complete.
- Status
- In preparation
The UYAP connection is not yet available.
- Access
- To be validated
The company-selected connection method and authorisation conditions will be validated before activation.
- Data flow
- Planned import
The scope of case, hearing and e-notification imports will be validated for the connection method.
- Sync
- Not yet available
Automatic background sync from UYAP is not yet available.
01/03
A planned flow, not a working connection.
The draft below illustrates a possible record flow; it does not operate on UYAP and is not a real sync log. Import, matching and notification steps depend on connection validation. The applicable date and deadline rule require separate review. See the UYAP guide for concepts and the e-notification guide for record tracking.
Source access to be validated
Planned flow draft; not evidence of a real operation, service or notification.
02/03
Planned data scope.
Case, court, hearing and e-notification data are under consideration for import. The fields below are a draft; they do not show working UYAP matching or automatic updates. Supported fields and unmatched record handling will be defined after the connection method is validated.
Planned source fields
- Case no.
- 2026/42 E.
- Court
- Commercial Court
- Hearing
- 24.11.2026 10:30
- Status
- Pending
Draft record; not real UYAP data or a completed import.
Target fields under consideration
- Case number and court
- Case record: case number and court fields
- Hearing date and time
- Hearings tab and the team agenda
- Case status
- Case status; the matching column on the kanban board
- E-notification and delivery date
- E-notification record and deadline tracking
For the case file side see case management; for the deadline calculation itself see legal deadline tracking.
03/03
What do lawyers ask about the UYAP integration?
- 01/07
How is my UYAP account connected to Vekilaw?
The UYAP connection is not yet available. A connection method such as a browser extension or desktop agent has not been selected. Setup and permissions will be validated for the company-selected method and provider; no current plan promises an available UYAP connection.
- 02/07
Which data is matched from UYAP?
Case, court, hearing and e-notification data are planned scope. Supported fields depend on the connection method and validation; working automatic UYAP imports are not currently offered.
- 03/07
Where can I see the e-notification delivery date?
Automatic delivery date imports from UYAP are not yet offered. E-notification record tracking is a separate feature; the applicable service date and deadline rule require separate review.
- 04/07
How do I fix a UYAP record that did not match?
A working UYAP matching flow is not yet offered. Review, correction and retry behaviour for unmatched records will be validated during connection acceptance; automatic person matching is not promised.
- 05/07
Who can set up and see the UYAP connection?
The connection is planned to be managed for the company selection and authorised users. Required permissions and provider access will be validated after a connection method is selected; this page does not indicate an active connection.
- 06/07
How does the team learn about a recorded delivery date?
An automatic notification flow from UYAP is not yet offered. Other notifications depend on channel setup, permissions, preferences and provider conditions; delivery across every channel is not guaranteed.
- 07/07
How long is the log kept?
This page does not commit to a retention period for the UYAP connection. Relevant terms will be stated once the actual connection scope and approved retention policy are defined.