EU Funding & Tenders Portal API: What Coordinators Need to Know
The EU Funding & Tenders Portal API is a set of programmatic interfaces that allow research organisations, technology providers, and project coordinators to access funding opportunity data, procurement notices, and project information from the European Commission's central grant management platform without using the browser-based interface. Rather than manually searching calls on the EU Funding & Tenders Portal, your systems can query structured data directly — automating opportunity monitoring, partner database updates, and compliance checks at scale.
The Portal itself is the European Commission's platform for the single electronic data interchange area for participants (SEDIA) under Article 150(1) of the EU Financial Regulation 2024/2509 (HE AGA, Article 1.1, p.1). Every grant managed through the Portal — including the vast majority of Horizon Europe actions — is subject to fully electronic communication workflows. Understanding where the API fits into this architecture is essential for organisations building internal tools or integrating Portal data into project management systems.
What Is the EU Funding & Tenders Portal and Why Does Its API Matter?
The EU Funding & Tenders Portal is the mandatory single entry point for all European Commission funding programmes and procurement opportunities, replacing the earlier Participant Portal from 2017 onwards. The Portal handles the full grant lifecycle — from opportunity discovery and proposal submission through to reporting, amendments, and payment — for programmes spanning Horizon Europe, Digital Europe, LIFE, Erasmus+, and dozens of others.
As stated in the Horizon Europe Annotated Grant Agreement, all communications between consortia and the granting authority — including formal notifications, amendments, deliverables, and financial statements — must be made electronically through the Portal (HE AGA, Article 36.1, p.319). This means the Portal is not merely a discovery tool; it is the legally binding communication channel for every active EU grant.
For organisations managing multiple funded projects simultaneously, or research support offices that monitor dozens of open calls across programmes, manual interaction with the Portal interface becomes a significant administrative bottleneck. The Portal's API infrastructure addresses this by exposing structured data endpoints that your internal systems can query programmatically. The API support section of the Portal documents the available interfaces and access requirements.
Many coordinators find that the real value of API integration is not in replacing the Portal workflow — which remains mandatory for all formal submissions and notifications — but in feeding Portal data into internal dashboards, CRM systems, and project management tools where the team already works.
What APIs Does the EU Funding & Tenders Portal Offer?
The Portal's API ecosystem comprises several distinct services, each covering a different domain of EU funding data. The primary interfaces available cover open calls and topic data, procurement notices via TED (Tenders Electronic Daily), and funded project results.
Search and Opportunities API
The Portal exposes a search API — sometimes referred to as the EC Search API or Topic Search API — that returns structured data on open and forthcoming calls for proposals. Queries can filter by programme (e.g., Horizon Europe with CCM2 programme ID 43108390), call status codes, type of action, and date ranges. The API returns call identifiers, deadlines, topic codes, and budget information.
A known limitation practitioners encounter is that the search API does not always return the full topic description text, including the objectives section visible when clicking through to a topic page in the Portal interface. This means organisations building automated briefing tools often need to combine API responses with targeted page-level requests or manual review for detailed topic content — a gap that is well documented in developer community discussions.
TED API for Procurement Notices
For procurement opportunities, the Portal integrates with the TED (Tenders Electronic Daily) system. According to TED API documentation, the system processes thousands of public procurement notices daily. Anonymous access is available for published notices, while authenticated access is required for submission-related workflows. This distinction matters for organisations building procurement monitoring tools: read access to published data is open, but any write or submission operation requires authenticated credentials linked to a validated organisation in the Participant Register.
CORDIS and Project Results Data
Funded project data — including project summaries, consortium members, deliverables, and outcomes — is accessible through CORDIS (Community Research and Development Information Service). While technically a separate system from the core Portal grant management environment, CORDIS data is fed from Portal project records and is widely used by research organisations for competitive intelligence, partner identification, and impact analysis.
| API / Data Service | Primary Use Case | Access Type | Key Data Fields |
|---|---|---|---|
| Portal Search / Topic API | Open call monitoring, opportunity alerts | Anonymous (read) | Call ID, deadlines, budget, programme, status |
| TED API | Procurement notice monitoring and submission | Anonymous (read) / Authenticated (submit) | Notice ID, contracting authority, CPV codes, deadlines |
| CORDIS | Project results, partner research, impact analysis | Open / downloadable datasets | Project acronym, consortium, funding amount, deliverables |
| Participant Register | Organisation validation, PIC lookup | Authenticated (Portal account required) | PIC, legal name, address, LEAR details |
How Does Authentication Work for Portal API Access?
Access to Portal API endpoints — particularly those involving organisation data, grant management workflows, or submission functions — is tied to the Portal's role-based access control system. All users must hold a valid EU Login account, and organisations must be registered in the Participant Register (formerly the Beneficiary Register) before any authenticated operations are possible.
The Portal's grant management system ('My Area', also referred to as the electronic exchange system) is accessible only to persons holding a user account and appropriate authorisation role (HE AGA, Article 1.1, p.1). The key roles with system-level implications for API-adjacent integrations are:
- LEAR (Legal Entity Appointed Representative): The mandatory organisational representative who must be designated before the signature of any Grant Agreement. The LEAR manages user roles and authorisations for their organisation within the Portal.
- PLSIGN (Legal Signatory): The only role authorised to sign Grant Agreements and amendments electronically.
- PFSIGN (Financial Statement Signatory): The only role authorised to sign financial statements.
- PCoCo / CoCo (Primary/Coordinator Contact): The roles through which the coordinator submits information to the granting authority during project execution.
For API integrations that read public data (open calls, published procurement notices), no authentication is required. For integrations that involve organisation-specific data — such as pulling your own project records, monitoring grant status, or any write operation — your integration must operate under an authenticated session tied to an appropriately authorised Portal account.
In practice, this means your IT team cannot build a fully automated submission pipeline that bypasses the Portal's role-based controls. The Portal Terms and Conditions govern all electronic exchange, and formal submissions must be made by the designated authorised persons — not by anonymous automated processes.
What Can You Realistically Automate with Portal API Data?
The honest answer is that the Portal API is well-suited to read-heavy, monitoring-oriented use cases, but is not a fully open programmatic interface for grant management operations. Here is what is practically achievable:
Funding Opportunity Monitoring
Research support offices managing multiple programmes can build automated alert systems that query the Portal's topic search endpoint daily, filtering by programme, type of action, and deadline range. When a new Horizon Europe call opens — or an existing call's deadline changes — your system can notify the relevant internal stakeholder automatically rather than relying on manual Portal checks. Call identifiers, budget indicative amounts, opening and closing dates, and topic codes are all available in API responses.
Partner and Organisation Database Enrichment
The Participant Register assigns every registered organisation a PIC (Participant Identification Code) — a nine-digit unique identifier used across all Portal interactions. Legal entity data including legal name, address, and legal representative details flows from the Participant Register into all grant communications automatically (HE AGA, Article 2.1, p.19). If your organisation maintains a partner CRM or consortium database, you can cross-reference PIC data from CORDIS project records to enrich partner profiles with funding history, previous consortium memberships, and active project counts — all without authenticated access.
Procurement Notice Tracking
For organisations bidding on European Commission procurement contracts accessible via the calls for tenders section of the Portal, the TED API enables systematic monitoring of notices by CPV code, contracting authority, and publication date. This is particularly useful for research infrastructure providers and consultancies that respond to both grants and procurement contracts.
What the API Cannot Replace
All formal grant management actions — submitting proposals, signing Grant Agreements, filing amendments, submitting periodic reports, and uploading financial statements — must be performed directly inside the Portal's secure grant management environment by the designated authorised persons (HE AGA, Article 36.1, p.319). No API integration can substitute for these actions. Communications sent through the Portal generate legally binding time-stamped records; formal notifications not accessed within 10 days after sending are considered accessed under the Portal Terms and Conditions (HE AGA, Article 36.2, p.319).
How Should Coordinators Integrate Portal API Data into Project Management Workflows?
For project coordinators managing active Horizon Europe grants across a consortium of 10 to 20 partners, the most practical integration approach connects Portal-sourced data to your internal project management environment without attempting to replicate the Portal's formal workflow functions.
Consider a concrete scenario: your institution coordinates a 4-year Horizon Europe Research and Innovation Action with 14 partners across 9 countries. Your project management office needs to track open sub-calls relevant to your thematic area for potential follow-on projects, while simultaneously managing reporting deadlines for the current grant. A practical integration would:
- Query the Portal topic search API weekly for new calls matching your programme cluster and keywords, delivering a formatted digest to your research support team's inbox or internal wiki.
- Pull CORDIS records for the 14 partner organisations to maintain current funding history profiles, flagging any partner that has taken on a new coordination role (a potential workload conflict indicator).
- Map your internal project milestone calendar against Portal reporting deadlines by maintaining a local record of the progress report schedule defined in Annex 1 of your Grant Agreement — typically structured as progress reports due 30 days after the end of each reporting period (HE AGA, Article 4.2.1, p.23).
- Use the authenticated Portal grant management system directly for all formal submissions, with the PCoCo role assigned to a named staff member who receives automated internal reminders from your project management tool.
A common challenge is keeping your internal tool in sync with the Portal without creating confusion about which system holds the authoritative record. The answer is clear: the Portal is always the authoritative record for all legal and financial matters. Your internal tools consume and display Portal data; they do not replace it.
For organisations evaluating third-party tools that claim Portal API integration, verify specifically which data endpoints they use and whether they require your Portal credentials. Tools built on public read endpoints carry no access risk; tools requiring authenticated credentials should be assessed against your institution's data security policies and the Portal Terms and Conditions.
You can find the full list of available API interfaces and their documentation in the Portal's dedicated API support section. For a broader orientation to Portal navigation and registration workflows, the Funding & Tenders Portal for Beginners webinar hosted by the Common Implementation Centre provides a structured walkthrough of core functions. For step-by-step guidance on using the Portal from first registration through to proposal submission, see the EMDESK Academy guide to using the Funding and Tenders Portal.
Practical Implications for Research Coordinators
The Portal API ecosystem is genuinely useful for research support teams, but it rewards realistic expectations. The interfaces available today are strongest for public data consumption — open calls, procurement notices, funded project records — and are deliberately constrained for formal grant management operations, where role-based human authorisation is a legal requirement, not a technical limitation.
Before building or procuring an API-based integration, your team should clarify three things: which data you actually need programmatically (vs. what is easier to retrieve manually), whether the integration requires authenticated Portal access and under whose credentials, and how your organisation will handle the separation between the authoritative Portal record and your internal data copies.
Organisations that have successfully implemented Portal API integrations typically start narrowly — automating a single workflow like call monitoring or partner PIC validation — before expanding. Attempting to build a comprehensive Portal mirror from the outset tends to create maintenance overhead that outweighs the efficiency gains.
For guidance on how the grant management process functions within the Portal across the full project lifecycle, the Grant Management Process video published by the Portal team provides a useful orientation. The Horizon Europe Annotated Grant Agreement remains the authoritative reference for understanding which Portal actions are legally required and by whom.
As the Commission continues to expand the Portal's digital infrastructure under the MFF 2021–2027, the API surface is likely to grow — but the fundamental principle will remain unchanged: the Portal is the single electronic data interchange area, and any automation built around it must operate within the boundaries of its terms and role-based access controls.
Frequently Asked Questions
Does the EU Funding & Tenders Portal have a public API for searching open calls?
Yes. The EU Funding & Tenders Portal exposes a search API that returns structured data on open and forthcoming calls for proposals, including call identifiers, deadlines, budget amounts, and topic codes. Anonymous read access is available for published opportunity data. The API documentation is available in the Portal's dedicated API support section at ec.europa.eu/info/funding-tenders/opportunities/portal/screen/support/apis.
Can I automate proposal submission through the Portal API?
No. Formal proposal submissions, Grant Agreement signatures, amendments, and financial statements must be made directly inside the Portal's secure grant management environment by designated authorised persons — specifically the PLSIGN, PFSIGN, and PCoCo roles. According to Article 36.1 of the Horizon Europe Model Grant Agreement, all formal communications must be made electronically through the Portal by persons authorised under the Portal Terms and Conditions. No API integration can substitute for these role-based actions.
What is the TED API and how does it relate to the Funding & Tenders Portal?
The TED (Tenders Electronic Daily) API provides programmatic access to European public procurement notices. It is integrated with the EU Funding & Tenders Portal and processes thousands of notices daily. Anonymous read access is available for published procurement notices, while authenticated access is required for submission workflows. Organisations monitoring European Commission procurement contracts can filter notices by CPV code, contracting authority, and publication date.
What is a PIC number and how does it appear in Portal API data?
A PIC (Participant Identification Code) is a nine-digit unique identifier assigned to every organisation registered in the EU Funding & Tenders Portal Participant Register. It is used across all Portal interactions and appears in CORDIS project records, call participant data, and consortium records. When querying CORDIS data via API, PIC numbers allow you to cross-reference partner organisations across multiple funded projects for competitive intelligence and partner due diligence.
Do Portal API integrations require sharing EU Login credentials with third-party tools?
Integrations using only public read endpoints — such as open call data or CORDIS project records — do not require EU Login credentials. However, integrations accessing organisation-specific data or grant management functions require authenticated access tied to a Portal account with appropriate role authorisation. Before granting third-party tools authenticated Portal access, organisations should assess the arrangement against their institutional data security policies and the Portal Terms and Conditions.
