API Endpoints

Get to understand the API

to test the api you can go on the tutorial site

/authorize/{provider}

GET authorize api for OAuth protocol

Responses

200 Success

/callback/{provider}

GET callback api for OAuth protocol

Responses

200 Success

/conf/

GET get all configured elements

Responses

200 Success

/conf/{project}/

PUT create a project

Responses

200 Success

POST (KO) import a zipped project

Parameters

Name	Located in	Description	Type
file	formData	yaml file	Array of File

Responses

200 Success

DELETE delete a project

Responses

200 Success

GET get configuration files of a project

Responses

200 Success

/conf/{project}/{file}

POST upload a text/yaml configuration file to a project

Parameters

Name	Located in	Description	Type
yaml	query	yaml text	String

Responses

200 Success

DELETE delete a text/yaml configuration file from project

Responses

200 Success

GET get a text/yaml configuration file from project

Responses

200 Success

/connectors/

GET get json of all configured connectors

Responses

200 Success

/datasets/

GET get json of all configured datasets

Responses

200 Success

/datasets/{dataset}/

POST get sample of a configured dataset, number of rows being configured in connector

Responses

200 Success

DELETE delete the content of a dataset (currently only working on elasticsearch datasets)

Responses

200 Success

GET get json of a configured dataset

Responses

200 Success

/datasets/{dataset}/{action}

PUT action = validation : configure the frontend to point to this dataset

Responses

200 Success

POST direct search into the dataset

Parameters

Name	Located in	Description	Type
file	formData	data file : csv, ...	File

Responses

200 Success

GET alternative way to get text/yaml source code including the dataset

Responses

200 Success

/datasets/{dataset}/{doc_type}/{id}/{action}

POST elasticsearch update api proxy

Parameters

Name	Located in	Description	Type
file	formData	data file : csv, ...	File

Responses

200 Success

/groups/

GET get all groups

Responses

200 Success

/jobs/

GET retrieve jobs list

Responses

200 Success

/login/

POST login api with user and hash

Responses

200 Success

GET return current user if logged

Responses

200 Success

/logout/

POST logout current user

Responses

200 Success

/recipes/

GET get json of all configured recipes

Responses

200 Success

/recipes/{recipe}/

GET get json of a configured recipe

Responses

200 Success

/recipes/{recipe}/{action}

PUT test, run or stop recipe

Responses

200 Success

POST apply recipe on posted data

Parameters

Name	Located in	Description	Type
file	formData	data file : csv, ...	File

Responses

200 Success

GET retrieve information on a recipe

Responses

200 Success

/roles/

GET get all roles

Responses

200 Success

/upload/

POST upload multiple tabular data files,

Parameters

Name	Located in	Description	Type
file	formData	data file : csv, ...	Array of File

Responses

200 Success

GET list uploaded resources

Responses

200 Success

/upload/{file}

DELETE deleted uploaded file

Responses

200 Success

GET get back uploaded file

Responses

200 Success

/users/

GET get list of all configured users

Responses

200 Success

Les auteurs

Fabien ANTOINE

Fabien est ingénieur et travaillait au sein de ministères régaliens sur la data et l'IA. Concepteur de matchID et de deces.matchid.io, il développe toujours avec plaisir les algorithmes aussi bien que les UI, sur son temps libre. Il a quitté depuis peu l'administration française, et reste passionné par les projets d'intérêt général.

Fabien ANTOINE image

Cristian PEREZ BROKATE

Cristian est phD passionné de développement et technologie, expert en deeplearning. Il travaille aujourd'hui au ministère de l'Intérieur, où il a créé IA Flash, et contribue activement à matchID avec la création de l'API décès.

Cristian PEREZ BROKATE image

Martin GROSS

Martin est ingénieur et cofondateur de CommoPrices.com, la plus grosse plateforme de prix de matières premières he world biggest portal of commodity prices. Il a développé l'interface de validation de matchID pendant son challenge EIG.

Martin GROSS image