[March 2025]
Planning
The following services are already available in the production environment:
- Definition of sub-projects (high, editing, deletion)
- Definition of instrumental sub-projects (high, editing, deletion)
- Action planning (high, editing, deletion)
- Definition of projects (high, editing, deletion)
- Definition of milestones and objectives (high, editing, deletion)
- Financial instrument services (high, editing, deletion)
Publication of version 2.0.4
A new version has been published with new enpoints available and with the necessary changes detected during the implementation of the planning services. Specific changes can be found in the FAQ section:
Highlighted changes from v2.0.3 to v2.0.4[February 2025]
Planning
Services for direct financial instruments and instruments are already available in the testing environment.
Once tested and validated, they will be deployed in the production environment.
[February 2025]
Planning
Services for definition and planning are already available in the testing environment:
- Definition of sub-projects (high, editing, deletion)
- Definition of instrumental sub-projects (high, editing, deletion)
- Action planning (high, editing, deletion)
- Definition of projects (high, editing, deletion)
- Definition of milestones and objectives (high, editing, deletion)
With regard to financial legal instruments:
- Implementation of financial instrument services: Second half of February.
Once tested and validated, they will be deployed in the production environment.
[January 2025]
Planning
Planning in the test environment is updated:
- Definition of sub-projects (high, editing, deletion): Already available in the testing environment
- Definition of instrumental sub-projects (high, editing, deletion): The second half of January.
- Action planning (high, editing, deletion): First half of February.
- Definition of projects (high, editing, deletion): First half of February.
- Definition of milestones and objectives (high, editing, deletion): First half of February.
- Implementation of financial instrument services: First half of February.
Once tested and validated, they will be deployed in the production environment.
[December 2024]
Legal instruments
The definition of services aimed at supporting loan management is published in CoFFEE in its early stages. In particular, the legal instruments: implementing agreement, brokering agreement, direct financial instrument and indirect financial instrument.
[October 2024]
Record of progress of indicators
Indicator progress recording services v2.0 are available in the production environment. (High, editing, erasing) according to the v2.0.2 specification.
[October 2024]
Record of progress of indicators
Indicator progress recording services v2.0 are available in the testing environment. (High, editing, erasing) according to the v2.0.2 specification.
Publication of version 2.0.2
Version 2.0.2 includes:
- Definitive definition of endpoints for recording the progress of indicators.
- Definition of the services for the consultation of (non-) revocation certificates.
The v2.0 version of the test environment implements this specification. Once tested and validated, it will be deployed in the production environment. The current integrations are not affected.
Planning
Planning is maintained in the testing environment:
- Definition of sub-projects (high, editing, deletion): Second half of November.
- Definition of instrumental sub-projects (high, editing, deletion): The first half of December.
- Action planning (high, editing, deletion): Second half of December.
- Definition of projects (high, editing, deletion): Second half of December.
Once tested and validated, they will be deployed in the production environment.
[September 2024]
Production environment
The v2.0 plan consultation and legal instrument management services are available in the production environment.
(Status of endpoints)Planning
Publication of services in the testing environment:
- 2. Implementation. Indicator progress record (high, editing, deletion): First half of October.
- Definition of sub-projects (high, editing, deletion): Second half of November.
- Definition of instrumental sub-projects (high, editing, deletion): The first half of December.
- Action planning (high, editing, deletion): Second half of December.
- Definition of projects (high, editing, deletion): Second half of December.
Once tested and validated, they will be deployed in the production environment.
[June 2024]
Production environment
The production environment and instructions for access to the production environment are available.
Services for the management of legal instruments
Services for the management of legal instruments according to the v2.0 version of the API are available in the testing environment.
Once tested and validated, they will be deployed in the production environment.
Publication of version 2.0.1Version 2.0.1 includes:
- Correction of errors in the definition of services for the management of legal instruments. (For more information, see ‘Frequently asked questions’)
- Full definition of services for the discharge of proceedings, instrumental sub-projects, sub-projects and projects.
- Comprehensive definition of services for the recording of progress and monitoring of indicators.
The services will be implemented in a staggered manner in the following order:
1. Follow-up to the plan (GETs).
2. Discharge of activities, instrumental sub-projects, sub-projects and projects.
3. Progress of indicators (SRAPs).
The implementation of the services will be reported by means of an information mail by blocks implemented, the status of implementation of the different endpoints can be consulted in:
status of endpoints.
In any case, the planning can be modified according to the demand or other needs that have been received. In cooperation with the General Secretariat of European Funds, the procedure for authorising access to the service, which simplifies both technical and managerial configuration, is being reviewed. The environment will be available once the procedure has been implemented.
[January 2024]Publication of version 1.5.1 correcting errors found in 1.5.0. Specific changes can be found in the FAQ section:
Highlighted changes from v1.5.0 to v1.5.1For organisational reasons, the first phase will not include the implementation of the financial execution registration service ('/execution/financial').
The testing environment will be available from Thursday, 1 February. The form for making the request for access will also be enabled. The following services will be available:
1.Structure information consultation services.
2. Registration services for legal instruments and recipients.
[November 2023]
Release of API version 1.5.0, adaptation of the previous version to the current CoFFEE information architecture.
Implementation of the definition will be carried out in phases; the first will group the following services:
1. Structure information consultation services; registration services for legal instruments and recipients; performance registration services.
2. Indicator progress recording services and possibly other services resulting from agency demand.
By means of this page and/or by e-mail, the units concerned will be informed of the planned schedule for implementingthe phases in the pre-production environments and in the production environment.
Versions of the service (index)
The following versions are currently available:
| Date | Version | Environment | Specification | Notes |
|---|
| June 2025 | 2.0 | Production | v2.0.10 | Recommended version. It is adapted to the functional changes of CoFFEE-MRR. |
| May 2025 | 1.5 | Production | V1.5.3 | Version available. It is not adapted to the functional changes of CoFFEE-MRR. |
Access and use of the service (index)
As a next step, following the submission of the initial form, the OIP will contact the requesting technical department via the support mail box@soportesgffee.zendesk.com. The communications required for the technical set-up, as well as the other set-up steps (including the final discharge in production) will be received from the same e-mail address.
Before the API can be used, those responsible for node information (projects, sub-projects and instrumental sub-projects of the PRTR) must authorise the user who identifies the management application that serves them to access and edit the data of the nodes; to this end, during the configuration process authorisation will be obtained through the completion of the document below, and its content will be verified by the General Secretariat of European Funds. Such authorisation shall be given only once by each responsible person, and shall have effect on all nodes (existing and future) that depend on it. The person responsible for the information of a node corresponds to the owner of the managing body of that node, and will be the person who must sign the authorisation or revocation.
Instructions for the completion of the authorization are available in the following files:
For the correct use of the service, two parameters must be added to the published interface REST API requests that make it possible to identify the origin of the calls, and that will be provided by the technical contact of the Office of Budgetary Information during the registration process. The parameters are:
- idApplication: CoFFEE-MRR API identifier
- idUser: user identifier of the management application.
Client Web services shall be authenticated by means of HTTPS/TLS with an electronic seal certificate issued by one of the certification service providers recognised by the Web service of @Fira.
More information (index)
For more information, see the page of answers to frequently asked questions, which will be updated on a regular basis with the answers to the queries raised.
In order to make any technical enquiry, erratum communication in the definition of services or other input, the units may be sent by e-mail to the support account (support@soportesgffee.zendesk.com).