This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
preface [2018/12/03 12:19] clubadmin [Security] |
preface [2025/07/17 11:49] (current) clubadmin |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Every API call that is sent to Club Planner API must be accompanied by a **token** that is preconfigured in the club planner parameters. | Every API call that is sent to Club Planner API must be accompanied by a **token** that is preconfigured in the club planner parameters. | ||
| + | For security reasons you should pass this token in the header as **x_auth_token**. | ||
| + | Note that the fixed token will be replaced in time with a more secure system. | ||
| Most API's also have a **from** optional parameter, this will be saved in the database as the user that created or changed the data. Examples for **from** can be " | Most API's also have a **from** optional parameter, this will be saved in the database as the user that created or changed the data. Examples for **from** can be " | ||
| Line 12: | Line 14: | ||
| Is over HTTPS and should never be used over HTTP, when using important data please put this API behind a VPN. | Is over HTTPS and should never be used over HTTP, when using important data please put this API behind a VPN. | ||
| + | |||
| + | Most api's are monitored and have logging (level of logging is configurable). | ||
| ====== Base URL====== | ====== Base URL====== | ||
| - | Is usaly the base url of the web platform + \api | + | Is usually |
| Example: https:// | Example: https:// | ||
| Line 31: | Line 35: | ||
| The getmember API needs an id or uid or email, when none are provided you will get HTTP 400. | The getmember API needs an id or uid or email, when none are provided you will get HTTP 400. | ||
| - | https://demo.clubplanner.be/ | + | https://YOUR-ENDPOINT.clubplanner.be/ |
| Return: | Return: | ||