Decathlon Authentication and Database structure

Summary of Changes:

Date DD/MM/YYY	Applied changes	Comments
04/05/2022	Typo correction (NL-Netherlands)	There was a typo in previous revision in “NL-Netherlands“

The whole authentication is happening with API key generated directly from the seller account on MIRAKL. We will need to use this API key as a Authorization header.

End Point: https://decathlonbelgium-preprod.mirakl.net/api/ If you need the API key please contact Bogomil Pavlov or Maria Mitreva (Unlicensed)

Please note for Phase1 we are doing only GB Channel that`s why we will have it as default value and only GB will be visible in the Account Decathlon > Channel dropdown.

New Tables and fields

Account Decathlon- Slave table of Account table used for the account setup

Field Name	Type	Required	Comment
End Point	varchar	Yes	The API endpoint to which we are connecting
API Key	varchar	Yes	API key required for the authentication
Channel	dropdown	Yes	Because we can list one offer on many channels we will need to add a dropdown list with values:

BE - Belgium CH - Switzerland DE - Germany ES - Spain FR - France GB - Great Britain IT - Italy NL - Netherlands PL - Poland PT - Portugal RO - Romania HU - Hungary CZ - Czech Republic We will display the full country name and push the code. For Phase1 we will need to display only GB | GB |

Item Account Decathlon -Slave table of Item Account containing all Decathlon specific fields.

Field Name	Type	Required	Comment	Default Value
Main Image	varchar	N
Additional Images	varchar	N	this field need to have the same logic as Item > More Picture URL
Discount Start Date	date	N
Discount End Date	date	N
Free Return	checkbox	N	“true“ or “false“	false
Eco Contributions	varchar	N	this field should have the same logic as our Item Account > Item Specifics.

Marketplaces / Decathlon Technical Scope / Decathlon Authentication and Database structure

Decathlon Authentication and Database structure