Get your MyEPO Mailbox and deadlines through an API

What you can build on MyEPO

• Get new Mailbox communications

  Build this

  Reads a folder of the company Mailbox, such as Inbox or Unread, with each communication's application, recipient, dispatch date and handled state.

  Takes

  Folder, dispatched since (optional)

  Returns

  Application number, communication title, recipient, dispatch date, user reference, handled, number of documents

• Get the time limits of an application

  Build this

  Opens an application in Applications and patents and reads the Time limits panel: the actions the EPO expects from you, each with its due date.

  Takes

  Application number

  Returns

  Application number, action, due date

• Get the due fees of an application

  Build this

  Reads the Due fees panel of one application in Applications and patents: which fees are pending, how much and by when.

  Takes

  Application number

  Returns

  Application number, fee, amount, due date

• Mark Mailbox communications as handled

  Build this

  Finds the Mailbox communications you list, marks them as handled and moves them to the folder you name.

  Takes

  Application number, communication title, dispatch date, folder

  Returns

  Application number, communication title, handled, folder

Automate MyEPO with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• New Mailbox communications, handed to your docketing system

  Build this

  Starts

  Every weekday at 7:30

  Step 1

  Get the communications in the Mailbox Inbox.

  Step 2

  Keep the communications that were not there on the last run.

  Step 3

  Post each one, with application number, title, recipient and dispatch date, to your docketing system's webhook.

• Time limits due in the next 30 days, by application

  Build this

  Starts

  Every Monday at 8:00

  Step 1

  For each EP application you list, get the Time limits panel.

  Step 2

  Keep the actions due in the next 30 days.

  Step 3

  Email you the list, sorted by due date, one line per action.

• Due fees each month, posted to your renewals system

  Build this

  Starts

  On the first day of every month at 9:00

  Step 1

  For each EP application you list, get the Due fees panel.

  Step 2

  Stop when no fee is pending.

  Step 3

  Post each fee, with application number, amount and due date, to your webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get new Mailbox communications” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "my.epo.org/get_mailbox_communications",
    "input": {
      "folder": "Inbox",
      "dispatched_since": "2026-11-09"
    }
  }'

{
  "status": "completed",
  "data": {
    "folder": "Inbox",
    "communications": [
      {
        "application_number": "EP26990012",
        "title": "Communication pursuant to Article 94(3) EPC",
        "recipient": "Acme Patent Attorneys",
        "dispatch_date": "2026-11-10",
        "user_reference": "ACME-0412-EP",
        "handled": false,
        "documents": 2
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

MyEPO’s own options

The EPO offers two APIs for IP management systems. The MyEPO API reads and updates Mailbox content and reads application data, and the Online Filing 2.0 API imports, submits and checks EP forms. Both use a B2B account requested from EPO support, and in MyEPO itself you can download Mailbox and application lists as CSV.

Read on November 12, 2026: Feature guide: APIs for exchanging information with your IP management systems, FAQ: What APIs are currently available?, Feature guide: handling Mailbox communications.

Signing in to MyEPO

MyEPO signs you in with your EPO account: email address and password, then a second factor, such as a security key, Okta Verify, Google Authenticator, a phone code, or an emailed code or link. With Fous you sign in once through the EPO's own sign-in with your own account, and the login is sealed with AES-256. If your second factor is an emailed code or link, it is handled and an expired session is signed back in.

Worth knowing

The Mailbox belongs to the company

Communications go to a company's Mailbox, not to a person. The company administrator activates it, adds recipients, which the EPO checks over several working days, and chooses who may handle it.

Non-public data needs portfolio permissions

Any user sees public data on published applications. Unpublished applications, non-public documents and the Time limits panel need the administrator to grant you the recipient's portfolio.

Replies are signed by an authorised person

A reply must be signed with the name and function of the representative or an authorised employee. Self-representing applicants cannot yet reply to communications in MyEPO.

Not every reply shows as a pending action

A reply under Rules 161(1) and 162 EPC does not appear automatically in Pending actions, because it is sometimes voluntary.

More in Legal, courts and intellectual property

• Portal Informacyjny Sądów Powszechnych
• MyHMCTS
• eCourts e-Filing
• Money Claim Online
• PACER
• Authorized Paid Representative Portal
• Arbitration Forums
• CCMS
• CounselLink
• Legal Tracker
• TyMetrix 360
• Collaborati

Other industries: myKN, Schwab Advisor Center, eModal, Walmart Scheduler 2.0, Lockheed Martin Procure to Pay, VUMPA.