rechercherDumes
DESCRIPTION
The marketplace wishes to retrieve the Buyer ESPDs' IDs, responding to a number of criteria (ID_consultation, Buyer SIRET,...)
ENVIRONMENTS
| Production URL | https://api.aife.economie.gouv.fr/dume/ |
| Qualification URL | https://sandbox-api.aife.economie.gouv.fr/dume/ |
PARAMETERS
Paramètres
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/dumeA -d "{}"
The braces frame the JSON.
Complete description of the API’s input and output parameters
| Entry parameter | Mandatory (M) / Optional (O) | Management rule |
|---|---|---|
| operation | M | Constant =rechercherDumes |
| platform | ||
| typeIdPlateforme | O | 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 the "requesting ID") corresponds to the SIRET or to the functional identifier of the public entity making the request on the marketplace. |
| rsDemandeur | M | Name of the entity making the request on the place (Corporate name) |
| CONSULTATION | ||
| idConsultation | O | |
| dateCreationDebut | O | |
| dateCreationFin | O | |
| dateModificationDebut | O | |
| dateModificationFin | O | |
| idNumeroRecherche | O | |
| BUYER | ||
| Id acheteur ("Buyer id") | O | Alphanumeric (14 characters) |
| MARKETPLACE | ||
| idPlateforme | O | |
| idTechniquePlateforme | O | |
| BUYER ESPD | ||
| idDume | O | Functional ID of the ESPD - 8 random alphanumeric characters |
| idStatutDume | O | |
| dateCreationDebut | O | |
| dateCreationFin | O | |
| dateModificationDebut | O | |
| dateModificationFin | O |
{
"operation":"rechercherDumes",
"plateforme":{ "typeIdPlateforme" : "1" , "idPlateforme": "33592022900036", "idTechniquePlateforme":"azerty"},
"idDemandeur":"123",
"rsDemandeur":"123",
"consultations":[{"idConsultation":"12345678901236","dateCreationDebut":"2015-07-05T19:04:17.413Z","dateCreationFin":"2015-07-05T19:04:17.413Z", "dateModificationDebut":"2018-07-05T19:04:17.413Z", "dateModificationFin":"2018-07-05T19:04:17.413Z", "typeMarket":"01", "natureMarket":"01", "typeProcedure":"01", "refFonctionnelle":"123456789012345678901234567809"}]
"
}
"response": {
"responseRecherche": {
"1": {
"dumeAcheteur": {
"Id": "esfpekdj",
"Date de création": "2018-05-18 10:29:53",
"Date de modification": "2018-05-18 10:29:53",
"Statut": "02",
"Accessibilité": true
},
"consultation": {
"Id": "4718547779",
"referenceFonctionnelle": "consultalalala69",
"idTypeProcedure": "01",
"idNatureMarket": "01",
"idTypeMarket": "01"
},
"lot": {
"numeroLot": "1"
},
"acheteur": {
"identifiant": "65412398745621"
}
}
}
}
This call mode is complete and illustrates the overall structure of the call: to make it operational, remove the sections that you don't wish to use in your search and complete the criteria to use by providing the information to search for between the quotation marks.
{
"operation":"rechercherDumes",
"plateforme":{ "typeIdPlateforme" : "" , "idPlateforme": "33592022900036", "idTechniquePlateforme":"azerty"},
"idDemandeur":"123",
"rsDemandeur":"123",
"consultations":[{"idConsultation":"","dateCreationDebut":"","dateCreationFin":"", "dateModificationDebut":"", "dateModificationFin":"", "typeMarket":"", "natureMarket":"", "typeProcedure":"", "refFonctionnelle":""}],
"lots":[{"idNumeroRecherche":"", "dateCreationDebut":"","dateCreationFin":"", "dateModificationDebut":"", "dateModificationFin":""}],
"identifiantsA":[{"identifiantA":""}],
"plateformeRecherche":{ "typeIdPlateforme" : "" , "idPlateforme": "", "idTechniquePlateforme":""},
"dumesAcheteurs":[{"idDume":"", "idStatutDume":"","dateCreationDebut":"","dateCreationFin":"", "dateModificationDebut":"", "dateModificationFin":""}]
}
