EPO & digital workflows
EPO APIs: plan an AI-assisted data handover
Turn an integration idea into a bounded pilot with expected data, a checked result and a clear next-step decision.
Start with a handover whose result your team can check: which official data should support which internal task? Microsoft 365 can bring together the expected set, AI comparison and acceptance record. The technical connection is separately planned and tested with the responsible people.
Downloading official communications, matching them to files and entering data again in an IP system creates handovers worth examining. The EPO provides documented interfaces for software integration. Their usefulness depends on the workflow, permissions and software in your practice.
This overview considers data exchange with electronic EPO services from a formalities team's perspective. It explains capabilities and an orderly introduction process. It does not imply that a particular working environment is already connected. Sources were checked on 8 November 2026.
Choose the task before the interface
An API is a documented technical connection through which software can request particular data or trigger supported actions. Start with a practical question: which manual handover should it support? One example is connecting the arrival of an official communication with its storage in the electronic case file.
| Service | Documented uses | Important boundary |
|---|---|---|
| EPO communications and application API | Retrieve official mailbox communications and documents; exchange permitted application and portfolio information | Access follows the B2B account’s permissions; some functions also change data or status |
| EPO electronic filing API | Import and export submission packages and send them through supported workflows | Package review, signature and approval to send remain necessary |
Check the specific form, document type and supported action against current documentation before starting a project. A general product description does not prove that your particular scenario is covered. This matters when older feature guides sit alongside later extensions to supported forms.
A personal login is not yet B2B access
For company integration, the EPO describes a B2B account with technical credentials. The company must already be established for the relevant digital EPO services. Its administrator receives the credentials and assigns suitable access. Personal sign-in and the machine connection are separate setup tasks.
The same technical account can serve several documented EPO interfaces. Mailbox access, portfolio rights and electronic filing permissions still need to be assigned to the task. Shared credentials do not mean that every function is automatically available.
Start with a bounded official mailbox retrieval
A manageable pilot retrieves a communication and its documents, then transfers them into a case record under controlled conditions. First confirm access to the intended official mailbox. Check portfolio permissions separately for any additional application queries. Compare the output with a known starting set: which communications were expected, which were returned and which documents were stored?
Other API functions include application information, displayed due dates and fees, and changes such as communication handling status or user references. Assess each function separately. A fee query does not make a payment. A returned list of due dates is not a complete docket until its coverage has been examined.
Compare the expected data with the test result
Define a bounded expected set for the pilot: documents, associated fields and their intended internal use. AI can compare the authorised test output with that list and suggest missing items, duplicate records or inconsistent labels. This review covers the data actually returned, not automatically every company record.
The responsible person checks proposed differences against the source set. In Microsoft 365, record what was tested, the remaining limits and who decides the next step. One successful example does not establish complete operation. Check any possible status changes caused by retrieval against the specific technical documentation before the pilot.
Move from testing to controlled operation
The EPO provides documented testing options with dummy data or a demo mode. Keep these environments visibly separate from production in the configuration. A sample-data test does not yet establish permissions or coverage in the company's real portfolio.
- The task, data types and intended result are precisely described.
- The administrator, IT or software provider and business owner are identified.
- The B2B account, environment and necessary permissions are checked.
- List requests account for filters, multiple result pages and expected totals.
- Missing permission, empty results and technical failure remain distinguishable in records.
- Retries, status changes and possible duplicate submissions are addressed.
- Production start, approvals and a return to the previous process are agreed.
Where AI and external support can help
AI can summarise a downloaded communication, propose a case association or prepare a checklist. Its output needs to remain traceable to the original document and correct matter. The client and IT determine which data may be processed in which system. Signature and legal decisions remain allocated to the responsible person.
A useful first engagement reviews a limited process: one handover, one data set and a result that can be checked. IP Formalities can prepare administrative requirements, example scenarios and acceptance checks with your team. Technical implementation and operation are coordinated with your IT or software provider. Start with the EPO access setup guide and use our responsibilities overview to define the scope.
Connect the workflow to the next task
Related steps: access and responsibility, handling official communications, comparing documents.
Sources and further reading
Frequently asked questions
- Can my EPO browser login be used directly as API access?
- The documented company integration uses a B2B account with technical credentials and suitable permissions. A personal login or an existing official mailbox right is not sufficient on its own.
- Can an API automatically replace every deadline entry?
- That cannot be concluded from a technical request. Check which matters, data and actions are covered for the relevant role. The agreed deadline control remains a separate responsibility.
- Can the EPO electronic filing API send submissions?
- The EPO documents API submission for supported packages. The specific process must satisfy requirements including suitable rights, a reviewed package, a valid signature and explicit authority to send.
- Does one successful test request mean the integration is ready?
- No. A test establishes only the checked request under the tested conditions. Operation also requires checks of coverage, permissions, error handling, retries, records and responsibilities.