FAQs about the API

Are there limits on the use of the service?

• Maximum request size: 100MB.
• Maximum document size: 60MB.
• Maximum number of items in a collection: 100 items.
• Number of requests per minute: to be established.

General questions about the API

What is the format of the dates?

Are all API fields mandatory?

Can I send multiple financial statements in the same POST call?

Yes, each call can contain as many statements as you wish from the same taxpayer (a single taxpayer), as specified in the "Declaration of Enforceability" data type of the schema.

Regarding indicator progress statements: does the "date" field (the progress reference date) have to be the current date?

The progress reference date of an indicator is the date on which the value of the indicator being updated is considered to have been reached, and therefore must be the current date or before, i.e. no future dates are allowed.

Why is "change" reported for quantitative indicators and "value" for qualitative indicators?

Indicators are measures of progress and can be quantitative (their value is a numeric figure within a range) or qualitative (they can take a value from a closed set of options)

• In the case of quantitative indicators, the change since the previous value of the indicator should be reported. For example, if the indicator is "Number of electric vehicles registered" and the indicator has changed from 1000 to 3000 vehicles, it should be reported "2000” vehicles.

• In the case of qualitative indicators, the new value taken from the possible ones (start, in progress and finished) must be reported.

The reason why the variation is provided for quantitative indicators is that the system allows for a justification (textual and, optionally, accompanied by files). It is understood that at the time of declaration, the increased (or decreased) value of an indicator is being justified, and not the final value achieved (in the example above, the 2000 vehicles that have been registered are justified).

In the case of qualitative indicators, there is a change in their status, and therefore the status achieved is declared.

Concerning the accounting execution reports: can the field "accounting date" (The reference date of the progress) be a date that falls after the current date?

The accounting date must be the current date or before, i.e. no future dates are allowed.

What is the reference of a legal instrument?

Declarations of accounting performance specify a reference to the legal instrument under which the declaration is made. The typical case is a contract or a grant, but all envisaged instruments must be identifiable.

The reference is therefore a code identifying the specific legal instrument within the scope of the Action for which the execution is registered.

Usually the reference coincides with the instrument code itself, which is established by the person who registers it in CoFFEE (by screen, bulk upload, ...).

For example, in the case of a grant registered in CoFFEE with the BDNS code "576282", the reference is exactly the same code. Or a contract (non-PLACSP) that has been registered in CoFFEE with the contract code "2023OIP45544", will have the same code as a reference.

However, there is the more complex case of PLACSP contracts, which is specifically addressed in the next question.

How is a contract that is registered on the Public Procurement Platform (PLACSP) differentiated from one that is not?

PLACSP contracts are identified by three codes: contracting authority code, tender code, and contract code (see next question for a detailed explanation). Non-PLACSP contracts are identified by a unique code.

In the contract registration entries in CoFFEE, the two types of contracts are identified separately.

Since references to legal instruments are made through a single field, in the case of PLACSP contracts (which, as indicated above, have three codes) the reference corresponds to the concatenation of the three values using the separator "~" between them, even if the fields were empty.

What are the PLACSP contracting authority, tendering authority and contract codes?

El The contracting authority code is an identifier used by the Public Sector Contracting Platform (PLACSP) associated with each contracting authority (in PLACSP it is called "Platform ID"). Each contracting body can consult its own in the administrator screen of the PLACSP "contracting body administrator" profile.

In addition, the Directorate-General for State Assets periodically publishes the list of codes in an Excel sheet that they update.

In the case of PLACSP and for each contracting body, the tender and contract codes are those that uniquely identify a contract that is incorporated into the Public Sector Procurement Platform:

The tender code corresponds to the File Number in the PLACSP, which is that provided by each contracting body.

The contract code corresponds to the Contract in the PLACSP. It is also a value determined by the contracting authority. It corresponds to each contract within the dossier.

In any case, both are values provided by the manager to the PLACSP. Both can be seen in the following image.

When is the "Other sources of financing" field completed?

Data on other sources of information will be filled in when the action to which the operation corresponds is financed by some other source, in addition to the funding from the Recovery and Resilience Facility. In this case, the mechanism or fund that has financed the operation shall be identified.

 

In the case of sending accounting information: Do the contracts/grants to be included have to be registered in CoFFEE prior to the submission of information?

Yes, it is necessary for third parties to be registered in CoFFEE prior to the submission of accounting information. The API provides the necessary services.

In the case of sending accounting information, do the third parties (beneficiaries, contractors, etc.) to be included have to be registered in CoFFEE prior to sending the information?

Yes, it is necessary for third parties to be registered in CoFFEE prior to the submission of accounting information. The API provides the necessary services.

In the case of "barred" accounting phases (A/, D/, O/, AD/, ADO/, PR/, RE/), are the amounts to be shown positive or negative?

Amounts in deleted documents are always positive; the slash already indicates that the amounts will be treated as negative for accounting purposes.

Once the accounting execution or indicator progress information has been sent: Will I receive any acknowledgement of receipt?

Yes, the system will provide an electronic acknowledgement of receipt to allow traceability of transactions.

• Path:
• The POST path /execution/other-instruments/targets has been updated
• The detailed routes of a legal instrument have been updated. The {reference} parameter becomes a query parameter. For example, GET /structure/proceedings/{code}/agreements/{reference} becomes GET /structure/proceedings/{code}/agreements/details?reference={reference}
• Performance:
• The field transferenciaDeRecursosEconomicosAOtroSubproyecto for Action has been made optional.
• The hitosObjetivosCriticos field has been added to Action.
• The type of the resourcesEconomics for Action field has been updated.
• Subproject:
• The field costeEstimado of recursosEconomicos of Subproject has been removed.
• SubproyectoInstrumental:
• The field costeEstimado of recursosEconomicos of SubproyectoInstrumental has been removed.

• Registration of legal instrument: the unique code assigned to the legal instrument is returned in the response of the registration operation. For example: POST /v2.0/contratos
• Consultation of legal instruments of an action: the list of legal instruments includes the unique code of each legal instrument. GET /v2.0/proceedings/{code}/juridical-tools
• Unique code query: there is a utility to obtain the unique code of a legal instrument from the action code and the reference of the legal instrument. GET /v2.0/instrumentos-juridicos/utilidades/codigo-unico

• Document upload: A new document is added to the system and the locator required for further operations is obtained. The document is created with the type PENDING. Uploaded documents not associated with an item will be deleted periodically. The service used is: POST /v2.0/documents
• Association of the document with an element: The document uploaded in the previous point is associated to an element. The association indicates the document location, the effective type and additional metadata. The service used depends on the element, e.g. to add a document to a contract, the service is: POST /v2.0/contratos/{codigo-unico}/documentos.

Other concerns

I have functional doubts about the management of the Recovery, Transformation and Resilience Plan and its management system, where can I go?

I have further technical queries related to the API. Where can I address them?