mettreAJourDume

DESCRIPTION

Market's place wants to record metadata which are associated to a Buyer ESPD or Economic Operator ESPD.

ENVIRONNEMENTS

PARAMETER

Header Parameter

DonnéeFormatFacultatif / obligatoire
CertificatVarcharObligatoire
Content-TypeVarcharObligatoire

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

Braces frames the JSON.

 

Complete description of input and output API's parameters

Input parameterOptional (O) / Mandatory( M)Management rule
operationMConstant
=mettreAJourDume
idDumeMFunctional ESPD ID - 8 random alphanumerical characters given by the ESPD Service
typeIdPlateformeO 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)
idPlateformeM 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
idTechniquePlateformeM 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
ID type de procédureOHeading 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
ID Type de marchéOHeading Code status:
« 01 » - Works
« 02 » - Supplies
« 03 » - Service
ID ConsultationOCall for tenders ID, released by the platform which makes the request to record the ESPD - 14 alphanumerical characters
Libellé consultationOCall for tenders heading - 100 alphanumerical characters
RefFonctionnelle consultationOSame reference as in the ESPD
Lots concernésO3 numerical characters
SIRET AO14 numericals characters
Type ID OEO 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 OEOIDFunctionnelOE ("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éponseO The respondent is:
- « 1 » : Representative
- « 2 » : co-contractor
- « 3 » : subcontractor
- « 4 » : holder
SIRET_N1OContract holder's SIRET
DLROO YYYY-MM-DDTHH :MM :SS format
{
"operation": "mettreAJourDume",
"plateforme": { "typeIdPlateforme": "1" , "idPlateforme":"33592022900036", "idTechniquePlateforme":"azerty"},
"rsDemandeur": "AIFE",
"idDemandeur": "12345698765445",
"dume": {
"idDume":"7jq89hoy"
},
"numeroLot": "1",
"colonneAModifier": "libelleConsultation",
"valeurAModifier": "test"
}

{
"response": {
"messageList": [
{
"type": "INFO",
"code": "MISE-A-JOUR",
"message": "Mise à jour de la donnée (venividivici) effectuée.Remplacement de la valeur (venividivici) par la valeur test."
}
]
}
}
Print Friendly, PDF & Email
Back To Top