Bitcoin Forum

Economy => Services => Topic started by: Sakarias-Corporation on February 15, 2015, 10:34:38 AM



Title: Find my API problem. 60 Dollar Bounty.
Post by: Sakarias-Corporation on February 15, 2015, 10:34:38 AM
Hello! i'm using BlockChains.INFO's API and i'm having some problems, it disconnects itself from time to time. and i'm wondering if i might have a problem with my code, or if its simply Blockchains problem. i'm offering 60 Dollar bounty.

you will have access to the full code.


Title: Re: Find my API problem. 55 Dollar Bounty.
Post by: TheButterZone on February 15, 2015, 10:39:05 AM
There's been a few doh! fixes figured out on https://bitcointalk.org/index.php?topic=40264.0 IIRC. Also their github https://github.com/blockchain


Title: Re: Find my API problem. 55 Dollar Bounty.
Post by: Muhammed Zakir on February 15, 2015, 11:33:39 AM
Can you show the API code? PM me or post here. I will do for cheaper(if I can). Thanks!

P.S. You can also contact me via Skype(see profile).

   -MZ


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: HeroC on February 15, 2015, 07:12:07 PM
You might as well post the code here, it is too much of a hassle for most people to message you for the code. https://github.com is a good, poensource host.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Sakarias-Corporation on February 15, 2015, 07:31:43 PM
done some testings.

if i request 200 ''Requests per minute'' by myself then everything works great! but as soon as someone else enters my website and use the Api ONCE it starts going haywire


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Bik_z19 on February 15, 2015, 07:49:00 PM
Then I'm curious what would happen if you did 201 requests per minute yourself! Give it a go.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Sakarias-Corporation on February 15, 2015, 07:54:02 PM
Then I'm curious what would happen if you did 201 requests per minute yourself! Give it a go.


then everything works fine.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Bik_z19 on February 15, 2015, 07:57:59 PM
Ar you using the API to get information? Or to transfer actual funds? As the API website of blockchain.info offers more than one solution.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Sakarias-Corporation on February 15, 2015, 08:03:48 PM
Ar you using the API to get information? Or to transfer actual funds? As the API website of blockchain.info offers more than one solution.


Transactions.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Bik_z19 on February 15, 2015, 08:07:42 PM
Well I've been looking at the documentation about those API's, none of them say anything about a limit to requests per minute or from several different domains or IP addresses. Big chance that the error might in your code. I'd be happy to look at it, you can PM it or upload it here.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: excword on February 15, 2015, 08:22:34 PM
Try rewriting the api integration part. It will clear the issue. Help yourself.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: robmob on February 15, 2015, 08:49:07 PM
did you change the rpc to use curl I found that helped me.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: micaman on February 16, 2015, 02:30:29 PM
If you are using websockets, i have the same problem. I don't think i'm doing something wrong because the script can run for an entire day perfectly, or simply disconnect after a short period. I guess it's disconnected on the server side, not sure we can do anything to avoid it.
You can try to "re-connect on disconnect", but depending on what you are doing, it may or not solve your problem.


Title: Re: Find my API problem. 60 Dollar Bounty.
Post by: Sakarias-Corporation on February 16, 2015, 02:32:32 PM
If you are using websockets, i have the same problem. I don't think i'm doing something wrong because the script can run for an entire day perfectly, or simply disconnect after a short period. I guess it's disconnected on the server side, not sure we can do anything to avoid it.

i am not.


i might just change API completely.