| Info |
|---|
| Table of Contents |
|---|
Introduction
This document covers the API definitions developed by Norges idrettsforbund og olympiske og paralympiske komité (NIF). NIF API products consists of a set of RESTful services.
This document is written for developers, programmers and the solution providers of third-party membership solutions (3. party/ 3. parties), who seek to sync data with NIF. NIFs requirements must be met to achieve a contract to provide service through NIF APIs to NIF organizations, prior to engaging in a delivery contract with given clubs.
This document also includes how to connect to the APIs and how to read from NIFs Enterprise Service Bus (ESB) hosted on Microsoft Azure cloud.
Change History
...
No
...
Changes
...
Date
...
1
...
Remove membership payment and active membership payment entity messages from section Entities Posted to Queue
Remove payment entity JSON schema for membership payment and active membership payment in section Entities JSON schema
...
6. February 2020
...
2
...
In POST Membership, SSN would not be mandatory.
In POST Membership, NationalityID would be used to decide is membership request for Norwegian or Foreign member.
List of Membership Status IDs updated with descriptions.
ToOrgtype JSON added
...
11. March 2020
...
3
...
Added description of how to generate developerUserID
Updated simplified flow for the membership
Updated person merge with all messages related to person merge
...
22. May 2020
...
4
...
Updated person merge message sequence as per new implementation
...
23. June 2020
...
5
...
Specify MembershipRequest-guidelines for 3.party
Remove SSN in MembershipRequest
...
14. October 2020
...
6
...
Added sections for Corporate Sports APIs
...
11. December 2020
...
7
...
Added support for Allidrett
...
5. March 2021
...
8
...
Extended response in PaymentDetails
...
Change History
No | Changes | Date |
1 | Remove membership payment and active membership payment entity messages from section Entities Posted to Queue Remove payment entity JSON schema for membership payment and active membership payment in section Entities JSON schema | 6. February 2020 |
2 | In POST Membership, SSN would not be mandatory. In POST Membership, NationalityID would be used to decide is membership request for Norwegian or Foreign member. List of Membership Status IDs updated with descriptions. ToOrgtype JSON added | 11. March 2020 |
3 | Added description of how to generate developerUserID Updated simplified flow for the membership Updated person merge with all messages related to person merge | 22. May 2020 |
4 | Updated person merge message sequence as per new implementation | 23. June 2020 |
5 | Specify MembershipRequest-guidelines for 3.party Remove SSN in MembershipRequest | 14. October 2020 |
6 | Added sections for Corporate Sports APIs | 11. December 2020 |
7 | Added support for Allidrett | 5. March 2021 |
8 | Extended response in PaymentDetails | 1. April 2022 |
Introduction
This document covers the API definitions developed by Norges idrettsforbund og olympiske og paralympiske komité (NIF). NIF API products consists of a set of RESTful services.
This document is written for developers, programmers and the solution providers of third-party membership solutions (3. party/ 3. parties), who seek to sync data with NIF. NIFs requirements must be met to achieve a contract to provide service through NIF APIs to NIF organizations, prior to engaging in a delivery contract with given clubs.
This document also includes how to connect to the APIs and how to read from NIFs Enterprise Service Bus (ESB) hosted on Microsoft Azure cloud.
Preparations
For any 3. party to connect to and consume NIF APIs, the request must go through the following stages:
...