This is custom heading element
DESCRIPTION
The EnregistrerDume ("Record ESPD") method enables the buyer profile to record an Economic Operator ESPD for which he or she has an identifier or an XML.
ENVIRONMENTS
Production URL | https://api.aife.economie.gouv.fr/dume/dumeOE |
Qualification URL | https://sandbox-api.aife.economie.gouv.fr/dume/xxx |
PARAMETERS
Header Parameters
Data | Format | Optional / mandatory |
---|---|---|
Certificate | Varchar | Mandatory |
Content - Type | Varchar | Mandatory |
Header example:
curl -v -X POST --insecure --cert xxxxx.pem https://api.aife.economie.gouv.fr/dume/dumeOE -d "{}"
The braces frame the JSON
Complete description of the API’s input and output parameters
Input parameters:
Input parameter | M/O (Mandatory / Optional) | Management rules |
---|---|---|
opération | M | Constant = enregistrerDume |
idDume | O (M if modification of an ESPD that's already been dropped) | Functional ESPD ID - 6 random alphanumeric characters given by the ESPD Service |
Dume | M | DUME OE uuencode (Economic Operator ESPD uuencode) |
Platform | ||
typeIdPlateforme | M | The values for « type d’ID plateforme demandeuse » (which means "requesting platform ID type") are: - « 1 » (Third party with SIRET number) - « 2 » (European structure outside of France) – intracommunity VAT - « 3 » (Structure outside of the EU) – Country code + first 16 corporate name characters - « 4 » (RIDET) - « 5 » (Tahiti Number) |
idPlateforme | M | 1/ Functional Id of the buyer profile which requested the connection 2/ The ID format of the platform is controled: - If « identification type » is « 1 » : 14 characters - If « identification type » is « 2 » : 18 characters maximum (1 to 18 characters) - If « identification type » is « 3 » : 3 to 18 characters - If « identification type » is « 4 » : 9 ou 10 characters - If « identification type » is « 5 » : « 9 » characters - If « identification type » is not provided, it is deemed to be a SIRET: 14 characters 3/ The platform's technical ID and the platform's ID must exist in database and be postioned on the same line as this database |
idTechniquePlateforme | M | 1/ ID available on the Chorus Pro "connection" space. The technical ID corresponds to the partner application code contained in the connection form. 2/ The platform's technical ID and the platform's ID must exist in database and be postioned on the same line as this database |
idDemandeur | M | The idDemandeur (which means "requester ID") corresponds to the SIRET number or functional identifier of the public entity that makes the request on the marketplace. - 1 to 18 characters |
rsDemandeur | M | Name of the entity which makes the request on the place (Corporate name) - 100 characters maximum |
idStatutDume | M | Heading Code status - « 01 » : Draft - « 02 » : Released - « 03 » : Replaced If the place wishes to replace an ESPD, it puts the new ESPD's XML as input parameter, with the ID of the ESPD to replace and status "3". The new ESPD is generated at status "2". |
idTypeProcedure | O (M if request of "released" status or if call for tenders ID provided) | Heading Code status: « 01 » - adapted procedure « 02 » - Open call for tenders « 03 » - Restricted call for tenders « 04 » - competitive procedure with negotiation « 05 » - negotiated procedure with a prior call for competition « 06 »- contract negotiated with no publication or prior call for competition « 07 » - competitive dialogue « 08 »- Competition « 09 » - Other |
idTypeMarche | O (M if request of "released" status or if call for tenders ID provided) | Heading Code status: « 01 » - Works « 02 » - Supplies « 03 » - Service |
idNatureMarket | O (M if request of "released" status or if call for tenders ID provided) | Heading Code status: « 01 » - Contract (initial contract) « 02 » - Partnership contract « 03 » - Framework agreement « 04 » - Subsequent contract « 05 » - Reserved market « 06 » - other |
idConsultation | O (M if request of "released" status or if call for tenders ID provided) | Call for tenders ID, released by the platform which makes the request to record the ESPD - 14 alphanumerical characters |
libelleConsultation | O (M if request of "released" status or if call for tenders ID provided) | Call for tenders heading - 100 alphanumerical characters |
refFonctionnelleConsultation | O (M if request of "released" status or if call for tenders ID provided) | Same reference as in the ESPD |
DLRO | O | YYYY-MM-DDTHH :MM :SS format |
idAcheteur | O | Buyer SIRET: Alphanumeric (14 characters) |
typeIdOE | O | The values are: - « 1 » (Third party with SIRET number) - « 2 » (European structure outside of France) – intracommunity VAT - « 3 » (Structure outside of the EU) – Country code + first 16 corporate name characters - « 4 » (RIDET) - « 5 » (Tahiti Number) |
ID Fonctionnel OE | M | IDFunctionnelOE ("Functional Economic Operator ID") corresponds to the identifier of the economic operator, under whose name the ESPD is dropped. - If « identification type » is « 1 » : 14 characters - If « identification type » is « 2 » : 18 characters maximum (1 to 18 characters) - If « identification type » is « 3 » : 3 to 18 characters - If « identification type » is « 4 » : 9 ou 10 characters - If « identification type » is « 5 » : « 9 » characters - If « identification type » is not provided, it is deemed to be a SIRET: 14 characters |
Type_réponse | O | The respondent is: - « 1 » : Representative - « 2 » : co-contractor - « 3 » : subcontractor - « 4 » : holder |
siret_NP1 | O | Contract holder's SIRET |
lotsConcernes ("concerned lots") | ||
id | O | Table reiterating the lots and associated labels' Ids. |
libelle | O | Table reiterating the lots and associated labels' Ids. |
Output parameters: recorded Economic Operator ESPD's identifier and associated metadata.
When an ESPD is recorded with released status, the following entry parameters are mandatory:
- ID Type de procédure ("Type of procedure ID")
- ID Type de marché ("Type of contract ID")
- ID Nature de marché ("Nature of contract ID")
- ID Consultation ("Call for tenders ID")
- Libellé consultation ("Call for tenders heading")
- refFonctionnelleConsultation ("Functional call for tenders reference")
- Lots concernés ("Concerned lots")
When recording an ESPD whose status is released, the data pertaining to the contract can only be modified via the metadata API.
{ "operation": "enregistrerDume", "dumeOE": {"xmlDume": "XMLdumeOEuuencode"}, "plateforme": { "typeIdPlateforme": "1" , "idPlateforme":"33592022900036", "idTechniquePlateforme":"azerty"}, "rsDemandeur": "AIFE", "idDemandeur": "12345698765445", "idStatutDume": "01", "idTypeProcedure": "01", "idTypeMarche": "01", "idNatureMarche": "01", "idConsultation": "12345632165412", "libelleConsultation": "bonne consultation", "refFonctionnelleConsultation": "consultation_DumeA_ii12dfs9", "DLRO": "2018-04-23T18:25:43.511Z", "identifiantA": "65412398745621", "typeIdOE": "1", "identifiantOE": "32165412345685", "typeReponse": "1", "lots": [ { "numeroLot":"1", "libelle":"super lot" } ], "siretNP1": "12365412398745", "accessible": true }
{ "response": { "idDume": "psppzpcp", "statutDume": "01" } }