Comments on: Does your REST API need an SDK?

By: API Digest #39: Why Not to Test, Scrum and SDK?

API Digest #39: Why Not to Test, Scrum and SDK? — Wed, 16 Mar 2016 14:00:28 +0000

[…] Offering an SDK together with your API is good but sometimes not a necessity yet. Ivan Valle has explained when each case arises and how to know your REST API needs an SDK. […]

By: Aubada Taljo

Aubada Taljo — Sat, 20 Feb 2016 07:31:00 +0000

Nice article, it gives a general and clean idea about the problem

By: This week in API land #41 | Restlet - We Know About APIs

This week in API land #41 | Restlet - We Know About APIs — Fri, 19 Feb 2016 19:10:58 +0000

[…] Does your REST API need an SDK? asks Ivan Valle. He says that no SDK will palliate a poorly designed API, that a talkative API might make for a chatty SDK, and covering a bad API with an SDK could make the situation even worse. […]

By: Ivan Valle

Ivan Valle — Fri, 19 Feb 2016 13:38:00 +0000

In reply to Shishir.

Thank you for reading!

That’s a very good point. OData is definitely another approach to standardize an API that exposes lots of data, and the OData libraries in various languages can definitely act as SDKs. While our API does indeed use some aspects of OData (a few of the query parameters like $top, $skip, etc), it doesn’t make full use of the standard. Companies who use OData to a greater extent would be more suited to write about it than I would.

By: Shishir

Shishir — Fri, 19 Feb 2016 04:32:00 +0000

No mention of OData?