[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, Erasing)
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. You can see the specific changes 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 fortnight 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): Second fortnight of January.
- Action planning (high, editing, deletion): First fortnight of February.
- Definition of projects (high, editing, deletion): First fortnight of February.
- Definition of milestones and objectives(high, editing, deletion): First fortnight of February.
- Implementation of financial instrument services: First fortnight 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 the management of loans in CoFFEE in its early stages is published. In particular, the legal instruments: implementing agreement, intermediation agreement, direct financial instrument and indirect financial instrument.
[October 2024]
Register 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]
Register of progress of indicators
The Indicator Progress Log v2.0 services are available in the test environment. (High, editing, erasing) according to the v2.0.2 specification.
Publication of version 2.0.2
Version 2.0.2 includes:
- Final definition of the 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 fortnight of November.
- Definition of instrumental sub-projects (high, editing, deletion): First fortnight of December.
- Action planning (high, editing, deletion): Second fortnight of December.
- Definition of projects (high, editing, deletion): Second fortnight of December.
Once tested and validated, they will be deployed in the production environment.
[September 2024]
Production environment
The Legal Instruments Management and Plan Consultation Services v2.0 is available in the production environment.
(Status of endpoints)
Planning
Publication of services in the testing environment:
- Execution. Record of progress of indicators (high, editing, deletion): First fortnight of October.
- Definition of sub-projects (high, editing, deletion): Second fortnight of November.
- Definition of instrumental sub-projects (high, editing, deletion): First fortnight of December.
- Action planning (high, editing, deletion): Second fortnight of December.
- Definition of projects (high, editing, deletion): Second fortnight 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.1
Version 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 actions, instrumental sub-projects, sub-projects and projects.
- Full definition of services for the registration of progress and monitoring of indicators.
The services shall be implemented in a phased manner in the following order:
1. Implementation of the Convention Follow-up to the plan (GETs).
2. Chapter II. Discharge of actions, instrumental sub-projects, sub-projects and project.
3. Chapter II. Progress of indicators (POSTs).
The implementation of the services will be reported through an informative mail by blocks implemented, you can check the implementation status of the different endpoints in:
status of endpoints.
In any case, the planning can be modified depending on 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 is being revised to simplify both technical and managerial set-up. 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. You can see the specific changes in the FAQ section:
Highlighted changes from v1.5.0 to v1.5.1
For 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 access request will also be enabled. The following services will be available:
1. Implementation of the ConventionStructure information consultation services.
2. Chapter II. Registration services of 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 stages; the former will group the following services:
1. Implementation of the Convention
Structure information consultation services; registration services for legal instruments and recipients; enforcement registration services.
2. Chapter II. Services for recording the progress of indicators 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 timetable for implementing
the phases in the pre-production environments and in the production environment.
Versions of the service (index)
The following versions are currently available:
| Date and place | Version | Environment | Specification | Notes |
|---|
| May 2025 | 2.0. | Production |
V2.0.8. | Recommended version. It adapts to the functional changes of CoFFEE-MRR. |
| May 2025 | 1.5. Table 1.5 | Production |
V1.5.3. | Version available. It does not adapt to the functional changes of CoFFEE-MRR. |
Access and use of the service (index)
As a next step, after the submission of the initial form, the OIP will contact the requesting technical department through the CoFFEE-Development@igae.hacienda.gob.es mailbox. The necessary communications for the technical configuration, as well as the rest of the configuration steps (including the final registration in production) will be received from the same email address.
Before the API can be used, those responsible for the information of the nodes (projects, subprojects and instrumental subprojects of the PRTR) must authorize the user who identifies the management application that serves them to access and edit the data of the nodes; for this, during the configuration process, the authorization will be obtained through the completion of the document listed below, and its content will be verified by the General Secretariat of European Funds. Such authorisation shall take place only once for each controller, 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 authorisation are available in the following files:
For the correct use of the service, two parameters must be added to the requests to the REST API of the published interface to identify the origin of the calls, which will be provided by the technical contact of the Budget Information Office during the registration process. The parameters are:
- idApplication: CoFFEE-MRR API identifier
- idUser: identifier of the user of the management application.
Client Web services will be authenticated via HTTPS/TLS with an electronic seal certificate issued by one of the certification service providers recognized by the @Marca Web service.
More information (index)
For more information, see the
answers to frequently asked questions page, which will be updated periodically with the answers to the queries raised.
In order to make any technical enquiry, communication of errata in the definition of the services or other contribution, the units can be directed by e-mail to the account of the development team (CoFFEE-Development@igae.hacienda.gob.es).