This is custom heading element

DESCRIPTION

The marketplace wishes to record a Buyer ESPD for which it has an identifer or an XML, with or without attached file.

ENVIRONMENTS

PARAMETERS

Header parameters

DataFormatOptional / mandatory
CertificateVarcharMandatory
Content - TypeVarcharMandatory

Header example:

curl -v -X POST --insecure --cert xxxxx.pem https://api.aife.economie.gouv.fr/dume/dumeA -d "{}"

The braces frame the JSON.

Complete description of the API's input and output parameters

Entry parameterMandatory (M) / Optional (O)Management rule
operationMconstant
=enregistrerDUME
(means: record ESPD)
idDumeO (M if modification of an ESPD that's already been dropped)Functional ESPD ID - 8 random alphanumeric characters
DUME uuencodeMThe XML is UUENCODE in base 64
idStatutDumeMHeading 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".
idTypeProcedureO (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
idTypeMarcheO (M if request of "released" status or if call for tenders ID provided)Heading Code status:
« 01 » - Works
« 02 » - Supplies
« 03 » - Service
idNatureMarketO (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
idConsultationO (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
libelleConsultationO (M if request of "released" status or if call for tenders ID provided)Call for tenders heading
refFonctionnelleConsultationO (M if request of "released" status or if call for tenders ID provided)Same reference as in the ESPD
Témoin_accessibleMEvidence enabling to determine that a Buyer ESPD is accessible because it has been published (the contract was published in the Official Journal)
DLROOYYYY-MM-DDTHH :MM :SS format
Id acheteurMAlphanumeric (14 characters)
lotsConcernes (means: concerned lots)
idO (M if request of "released" status or if call for tenders ID provided)
libelleO (M if request of "released" status or if call for tenders ID provided)
platform
typeIdPlateformeOThe 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)
idPlateformeM1/ 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 positioned on the same line as this database
idTechniquePlateformeO1/ 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
idDemandeurMThe 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
rsDemandeurMName of the entity which makes the request on the place (Corporate name)

In the case where the ESPD has already been dropped for the same call for tenders / the same lot for a buyer identifier, the ESPD ID and the XML file are mandatory.

Recording of an ESPD

{
"operation": "enregistrerDume",
"dumeA":  {"xmlDume": "DUMEAuuencode"},
"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_Dume___A_ii12dfs9",
"DLRO": "2018-04-23T18:25:43.511Z",
"identifiantA": "65412398745621",
"typeIdA": "1",
"lots": [
{
"numeroLot":"1",
"libelle":"super lot"
}
],
"accessible": true
}
{
"response": {
"idDume": "fufhjhhi",
"statutDume": "01"
}
}

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.

Print Friendly, PDF & Email
Back To Top