Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#1

Post by sunkarapk » Fri, Jan 03, 2014, 1:46 PM UTC

PS: Assuming a REST architecture.

Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby
github.com

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#2

Post by sunkarapk » Fri, Jan 03, 2014, 2:03 PM UTC

Author here. I covered almost everything in the documentation. And there is also a small example which is hosted at https://github.com/alpaca-api.

Please ask if you have any questions. Thanks

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#3

Post by htuao » Fri, Jan 03, 2014, 2:15 PM UTC

sunkarapk wrote: post #2

Author here. I covered almost everything in the documentation. And there is also a small example which is hosted at https://github.com/alpaca-api . Please ask if you have any questions. Thanks

How do you differ from Swagger, Blueprint, I/O Docs, RAML and all these API endpoint descriptions?

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#4

Post by johnnyio » Fri, Jan 03, 2014, 2:18 PM UTC

Describing an API is not hard, but the API authentication method is. How do you think you will do it?

Edit : If you don't make oauth consumption simpler, you don't really solve the problem

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#5

Post by sunkarapk » Fri, Jan 03, 2014, 2:21 PM UTC

johnnyio wrote: post #4

Describing an API is not hard, but the API authentication method is. How do you think you will do it? Edit : If you don't make oauth consumption simpler, you don't really solve the problem

Currently, I am supporting 3 authentication strategies. Basic, Token in header and OAUTH.

These will cover most of the APIs. And I am open to include other kind of authentication strategies too.

https://github.com/pksunkara/alpaca#authorization-strategies

EDIT: OAUTH Consumption is not the main priority here. The problem I intended to solve is automating the development and maintaing of API client libraries in several different languages.

That said, I intend to add support for OAUTH consumption too.

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#6

Post by pjmlp » Fri, Jan 03, 2014, 2:27 PM UTC

Can we please stop calling Web Services APIs?

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#7

Post by sunkarapk » Fri, Jan 03, 2014, 2:35 PM UTC

htuao wrote: post #3

sunkarapk wrote: post #2

Author here. I covered almost everything in the documentation. And there is also a small example which is hosted at https://github.com/alpaca-api . Please ask if you have any questions. Thanks

How do you differ from Swagger, Blueprint, I/O Docs, RAML and all these API endpoint descriptions?

I tried searching for a program which generates client libraries in different programming languages and failed.

Could you please link if something does it? From what I gather, the above mentioned sites only provide methods of describing the API and/or Automating the API on the server side. Nothing is said about client libraries.

Thanks

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#8

Post by AznHisoka » Fri, Jan 03, 2014, 2:37 PM UTC

pjmlp wrote: post #6

Can we please stop calling Web Services APIs?

Why? what else do you call APIs?

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#9

Post by mattdawson » Fri, Jan 03, 2014, 2:40 PM UTC

sunkarapk wrote: post #7

htuao wrote: post #3

Earlier quoted context omitted.

How do you differ from Swagger, Blueprint, I/O Docs, RAML and all these API endpoint descriptions?

I tried searching for a program which generates client libraries in different programming languages and failed. Could you please link if something does it? From what I gather, the above mentioned sites only provide methods of describing the API and/or Automating the API on the server side. Nothing is said about client libraries. Thanks

http://thrift.apache.org/

Re: Show HN: Given an API, Generate client libraries in Node, Python, PHP, Ruby

#10

Post by michaelmior » Fri, Jan 03, 2014, 2:42 PM UTC

sunkarapk wrote: post #7

htuao wrote: post #3

Earlier quoted context omitted.

How do you differ from Swagger, Blueprint, I/O Docs, RAML and all these API endpoint descriptions?

I tried searching for a program which generates client libraries in different programming languages and failed. Could you please link if something does it? From what I gather, the above mentioned sites only provide methods of describing the API and/or Automating the API on the server side. Nothing is said about client libraries. Thanks

Why create a new format for describing APIs instead of using something like RAML? The client library generation is very useful, but it would be nice if there wasn't yet another format needed to describe the API.