Author

Topic: [HELP] BlockChain.info RECEIVE MONEY API does not execute the callback (Read 1504 times)

newbie
Activity: 17
Merit: 0
Is it just me, or did the "address" parameter just disappear?

edit: just came back...
newbie
Activity: 17
Merit: 0
Does anyone know if there is a similar service for Litecoin btw?
newbie
Activity: 17
Merit: 0
Works now Smiley Thanks!
hero member
Activity: 910
Merit: 1005
....and everythings works fine except one thing: the http callback is not executed for real transactions. Everythings goes fine, the money flows from one address to another but the callback is not executed. The test callback works fine.

Was the callback should not called once? What is the URL in question I will check the logs?

I can confirm there was an issue with the callback not being retried every block until the "*ok*" is given which should be fixed now.

legendary
Activity: 1498
Merit: 1000
legendary
Activity: 1102
Merit: 1014
I doubt anyone would design an API that keeps calling the callback indefinitely. I read that API document to mean that the API doesn't care what you do with the callback. After all, your service is dependent on blockchain.info's API not the other way around.
newbie
Activity: 17
Merit: 0
I have just been playing around with this API myself, and I receive only one callback for every payment, even when I don't echo "*ok*" ... Shouldn't the callbacks keep coming until I echo "*ok*"?
full member
Activity: 121
Merit: 100
Hi there,

I know this is not the best place to ask for help regarding an API from a third-party but I've contacted blockchain several times without response. I am creating a simple Bitcoin application using the Receive Payments API from Blockchain:
https://blockchain.info/api/api_receive

....and everythings works fine except one thing: the http callback is not executed for real transactions. Everythings goes fine, the money flows from one address to another but the callback is not executed. The test callback works fine.

I have contacted them several times without response. Can anyone guess or has experienced this problem before?

Thanks in advance!
Jump to: