Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coins not loading from page call #19

Closed
satoshisound opened this issue Oct 13, 2016 · 10 comments
Closed

Coins not loading from page call #19

satoshisound opened this issue Oct 13, 2016 · 10 comments

Comments

@satoshisound
Copy link

  1. Small typo in docs. You have:
    http://www.coincap.io/page/:coin

Should be without the colon:
http://www.coincap.io/page/coin

  1. The following coins are not loading from this API call:
    ETC, OMNI, REP
@steveclifton
Copy link

Still isnt working for ETH either ..

@zoeyTM
Copy link

zoeyTM commented Feb 25, 2017

+1

Not working for several that I tested. LTC, DOGE, DASH, ETH, XMR, ZEC, XRP, just to name a few.

Interestingly, ETC returns

{
  "success": false,
  "error": "Invalid search params"
}

as opposed to an empty set like the others.

@arobbins
Copy link

Experiencing the same

@berevoescu
Copy link

Same here: it works ok for BTC. I tried ETH, LTC, XRP, DGB. For some reason it also seems to work for XLM.

@sebs
Copy link
Contributor

sebs commented May 22, 2017

uh, do i need to update the node.js api?

@jogam5
Copy link

jogam5 commented May 26, 2017

LOL, this API is like a joke!

@davedags
Copy link

to the original poster, just an fyi. In page/:coin, the colon is standard REST api syntax to denote that it is a variable, in most cases the id of the record you are fetching.

Anyways, I agree with everyone that the page endpoint is simply unusable :(

@chauey
Copy link

chauey commented Aug 17, 2017

where else can we get reliable data/service? spent all this time to set it up and only seeing "trades". not sure how to get any other data or if reliable

@iamskippy0
Copy link
Collaborator

In terms of documentation, I agree with @davedags in the sense that the colon is standard and should in-fact be there as it denotes a variable id, whereas no colon would imply the only value to ever sent to that endpoint is the static string id.

This endpoint has been refactored and will now provide the proper data. Thanks for your feedback, all.

@koltregaskes
Copy link

Any update on the historical data? Still doesn't appear to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests