FIFA Connect ID Service exposes a set of REST API methods. Every scenario that can be achieved via SDK can be also achieved directly by the use of API (Hashing API, ID Directory API, Service Bus API). SDKs in .NET, Java and PHP that Connect ID provides, use that API layer under the hood.
If so, an MA whose NRS is built in technology other than supported (e.g. in Python) could expect that choosing a direct integration via API will be a viable option for them. This is, however, not a recommended approach. You can read more about our recommendations here as this article only explains the challenges of the "via API" integration.
If one chooses to integrate directly via REST API, they will basically need to
In fact even this extensive list of operations that need to be performed without SDK, is simplified. It assumes that you have implemented and run a listener component responsible for sending & receiving messages from the Service Bus. Authorization topic was not discussed either, but your application will of course need to authenticate with REST API and Service Bus component (via Azure Active Directory). Sending out messages to different MAs should be done asynchronously, otherwise the performance will be affected. Things like error handling or logging cannot be forgotten either.
All in all, developing the whole integration from scratch without using any of the SDKs under the hood, will be a significant effort and instead we recommend to use one of the approaches described here.
If, despite the recommendation, a Client chooses to pursue the direct integration with API, they will find the following resource useful as it includes the code snippets: Direct API integration (proof of concept).
Reading about all these difficulties one might ask a question: why is Connect ID Service built in a way that it needs a thick client (SDK)? Why haven't all those abovementioned complexities been hidden on the server side behind the REST API? This would definitely be a valid question. The answer is personal data protection. To follow the privacy be design principle of the Connect Programme we needed to ensure that FIFA_ID cannot be correlated with first and last name of the person being registered. Therefore it is the client that needs to implement a logic of first contacting a Hashing service and then, after being returned the results, sending hashes to ID Directory service to get a FIFA_ID.
If you are interested to know more about this topic contact us by opening a ticket or sending an e-mail to firstname.lastname@example.org.