[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 targets (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. Please refer to specific changes in the FAQ section:
significant changes from v2.0.3 to v2.0.4
[February 2025]
Planning
The services for direct and indirect financial instruments are already available in the test environment.
Once tested and validated, they shall be deployed in the production environment.
[February 2025]
Planning
Definition and planning services 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 targets (high, editing, deletion)
For financial legal instruments:
- Implementation of financial instrument services: Second half of February.
Once tested and validated, they shall 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 test environment
- Definition of instrumental sub-projects (high, editing, deletion): 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 targets (high, editing, deletion): First half of February.
- Implementation of financial instrument services: First half of February.
Once tested and validated, they shall be deployed in the production environment.
[December 2024]
Legal instruments
The definition of services to support loan management in CoFFEE is published in its early stages. In particular, the legal instruments: implementation agreement, brokering agreement, direct financial instrument and indirect financial instrument.
[October 2024]
Progress register of indicators
The v2.0 Indicators Progress Recording services are available in the production environment. (high, edition, deleted) according to specification v2.0.2.
[October 2024]
Progress register of indicators
The v2.0 Indicators Progress Recording services are available in the testing environment. (high, edition, deleted) according to specification v2.0.2.
Once tested and validated, they shall be deployed in the production environment.
(Endpoint status) Publication
of version 2.0.2
Version 2.0.2 includes:
- Final definition of indicator progress record endpoints.
- Definition of services for the consultation of revocation (no) certificates.
The v2.0 version of the test environment implements this specification. Once tested and validated, it shall be deployed in the production environment. Current integrations are not affected.
Planning
Planning is maintained in the test environment:
- Definition of sub-projects (high, editing, deletion): Second half of November.
- Definition of instrumental sub-projects (high, editing, deletion): 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 shall be deployed in the production environment.
[September 2024]
Production environment
The v2.0 services for consultation of the plan and management of legal instruments are available in the production environment.
(Endpoint status)
Planning
Publication of services in the test environment:
- Implementation. Progress register of indicators (high, edition, deleted): First half of October.
- Definition of sub-projects (high, editing, deletion): Second half of November.
- Definition of instrumental sub-projects (high, editing, deletion): 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 shall be deployed in the production environment.
[June 2024]
Production environment
The production environment and the 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 shall be deployed in the production environment.
Publication
of version 2.0.1
Version 2.0.1 includes:
- Correcting errors in the definition of services for the management of legal instruments. (More information in the
‘FAQ’ section)
- Full definition of services for the discharge of actions, instrument sub-projects, sub-projects and projects.
- Full definition of services for the recording of progress and monitoring of indicators.
The services shall be implemented in a phased manner in the following order:
1.
Monitoring the plan (GETs).
2.
High level of actions, instrumental sub-projects, sub-projects and projects.
3.
Progress of indicators (POs).
The implementation of the services will be reported by means of a block information post implemented, the state of implementation of the different endpoints in:
endpoint status can be consulted.
In any case, planning may be modified on the basis of demand or other needs received. In collaboration with the General Secretariat of European Funds, the procedure for authorising access to the service is being revised to simplify both technical and managerial settings. The environment shall be available once the procedure has been implemented.
[January 2024]
Publication of version 1.5.1 correcting errors found in 1.5.0. Please refer to specific changes in the FAQ section:
significant changes from v1.5.0 to v1.5.1
For organisational reasons, the first stage shall 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 the application for access shall also be made available. The following services shall be available:
1.Structure information consultation services.
2. Discharge services of legal instruments and recipients.
[November 2023]
Publication of API version 1.5.0, adaptation of the previous version to the current CoFFEE information architecture.
The implementation of the definition shall be carried out in phases, the first grouping together the following services:
1.
Services for consultation of structure information; discharge services of legal instruments and addressees; execution registration services.
2. Indicators ' progress record services and possibly other services resulting from agency demand.
By
the same page and/or by e-mail, the units concerned shall be informed of the planned timetable for the implementation of the phases in the pre-production environments and in the production environment.
The following versions are currently available:
| Date | Version | Environment | Specification | Notes |
|---|
| April 2025 | 2.0 | Production |
v2.0.7 | Recommended version. Adapts to the functional changes of CoFFEE-MRR. |
| March 2024 | 1.5 | Production |
v1.5.2 | Available version. It does not adapt to the changes of functions of CoFFEE-MRR. |
Access and use of the service
(index)
If an external management application with CoFFEE is to be integrated, an application should be sent via the
Web Services Catalogue, where the API access request form is available.
As a next step, following the submission of the initial form, the OIP will contact the requesting technical department via the CoFFEE-Development@igae.hacienda.gob.es mailbox. The communications necessary for the technical configuration, as well as the other configuration steps (including final production discharge), shall be received from the same email address.
Prior to the use of the API, those responsible for nodes information (PRTR projects, sub-projects and instrument sub-projects) should authorise the user who identifies the management application servicing them to access and edit nodes data; to this end, authorisation will be sought during the configuration process through the completion of the document below, and its content will be verified by the European Secretariat. Such authorisation shall take place only once for each person responsible and shall have effect on all nodes (existing and future) that depend on him or her. The person responsible for the information of a node shall be the owner of the managing body of that node and shall be the person who is required to sign the authorisation or revocation.
The instructions for completing the authorisation are available in the following files:
For the correct use of the service, two parameters allowing the identification of the origin of the calls shall be added to the requests to the REST API of the published interface and shall be provided by the technical contact of the Office of Budgetary Information Technology during the discharge process. The parameters are:
- idApplication: CoFFEE-MRR API Identifier
- idUser: user identifier of the management application.
The client Web services shall be authenticated by HTTPS/TLS with an electronic seal certificate issued by one of the certification service providers recognised by the @Signature Web Service.
More information (index)
For
more information, please refer to the
FAQ replies page, which will be updated on a regular basis with the responses to the queries raised.
For any technical consultation, communication of errats in the definition of services or other input, units may be directed by email to the CoFFEE-Development@igae.hacienda.gob.es account.