|
Title: [ANN] KRAKEN.COM - API Documentation Now Available Post by: btcx on June 05, 2013, 08:32:39 AM https://beta.kraken.com/help/api
Input, bug reports greatly appreciated. Title: Re: [ANN] KRAKEN.COM - API Documentation Now Available Post by: monsterer on June 05, 2013, 12:36:22 PM Hmmm, what format is the return data? XML? JSON? I have no idea from looking at your docs.
Separate the description of what is returned from the actual data returned. Do this by including actual example data returned from the API. Do you have any reference implementations? Cheers, Paul. Title: Re: [ANN] KRAKEN.COM - API Documentation Now Available Post by: Dargo on June 05, 2013, 04:14:50 PM Hmmm, what format is the return data? XML? JSON? I have no idea from looking at your docs. Near the top of the doc it says, "Responses are JSON encoded in the form of:" Quote Separate the description of what is returned from the actual data returned. Do this by including actual example data returned from the API. Suggestion noted. For now, at least, you can try it out to see the response. Quote Do you have any reference implementations? http://krakenapi.everdot.org/API/ There's a reference implementation there in python. But it's for an older doc that has changed. Still it might be helpful, and may get updated soon. -D Title: Re: [ANN] KRAKEN.COM - API Documentation Now Available Post by: monsterer on June 05, 2013, 07:11:50 PM Near the top of the doc it says, "Responses are JSON encoded in the form of:" Must have missed that - but what caused me to be more confused was that the response data field names appear to have '-' symbols in them, making them unsuitable for json decoded to object format in most languages (since variables cannot have minus signs in the names); they will only ever be able to be decoded into associative array format. This made me think it was actually XML I was looking at. Title: Re: [ANN] KRAKEN.COM - API Documentation Now Available Post by: Dargo on June 05, 2013, 11:56:50 PM Near the top of the doc it says, "Responses are JSON encoded in the form of:" Must have missed that - but what caused me to be more confused was that the response data field names appear to have '-' symbols in them, making them unsuitable for json decoded to object format in most languages (since variables cannot have minus signs in the names); they will only ever be able to be decoded into associative array format. This made me think it was actually XML I was looking at. Ah, yeah, that makes sense. The aimed-at format was for associative arrays. But it can be changed to work for languages that decode to variables instead. |