This group is created to facilitate technical and integration discussions related to cowin platform. API related contents can be obtained at API setu portal https://apisetu.gov.in/public/marketplace/api/cowin
115
stars
30
forks
source link
KYC-VS API should be slotted under Public instead of Protected API #556
Looking at the Certificate APIs, which is essentially a read operation, its rightly categorized as Public API
But the KYC-VS [Vaccination Verification API] whose JSON payload response is a minute subset of Certificate API's pdf response is categorized as a Protected API. [Also, consequentlythe cost in terms of compute + bandwidth for both COWIN servers and us the API consumers is also much greater with Certifcate APIs].
Making KYS-VS as protected API only ensures needless friction in utilizing it.
As per API Setu's own sandbox doc , public APIs are for read operations
Looking at the Certificate APIs, which is essentially a read operation, its rightly categorized as Public API
But the KYC-VS [Vaccination Verification API] whose JSON payload response is a minute subset of Certificate API's pdf response is categorized as a Protected API. [Also, consequentlythe cost in terms of compute + bandwidth for both COWIN servers and us the API consumers is also much greater with Certifcate APIs].
Making KYS-VS as protected API only ensures needless friction in utilizing it.