We have implemented a new endpoint for the Rinkeby Testnet. You can now use our API to interact with the Rinkeby Testnet Blockchain!
Please check out our documentation for an overview of the endpoints for every function.
Also, the Thread design has been updated!
Topic: [ANN] 🤖 TOKENGATEWAY.IO - API to send & receive ER20 Tokens and ETH - page 3. (Read 2627 times)
October 26, 2019, 07:11:19 AM
December 31, 2018, 05:22:20 AM
bump
December 28, 2018, 12:27:24 PM
bump
October 17, 2019, 02:18:47 PM
Bump
Bump
Bump
It is great that you are following the forum rules of not bumping the thread more than once within 24hrs.But please delete your older bump posts when you create new bump. I have reported to the mods so they would be taking care from now on.
Alright thanks for the feedback. Will do it that way from now on
December 24, 2018, 10:07:02 AM
Merry Christmas to you!
October 16, 2019, 03:14:24 PM
Bump
Bump
Bump
It is great that you are following the forum rules of not bumping the thread more than once within 24hrs.But please delete your older bump posts when you create new bump. I have reported to the mods so they would be taking care from now on.
October 10, 2019, 02:04:17 PM
We just added a captcha to prevent bots from using our contact form. Also, we changed our FAQ so all answers are up to date again.
December 22, 2018, 05:53:06 AM
bump
September 29, 2019, 08:58:35 AM
You may need to delete some of your bumps in order to bring sanity to your thread.
I am a coder myself and I thought your website api can be useful to my clients but the idea of buying credit continuously turn me off.
Is there no way people can buy the api one-time instead of refilling credit ?
Hello! Thanks for your feedback. As we have continously costs for running the infrastructure, we also need to charge for API usage continously. From what I see the credits system has advantages but also some disadvantages.I am a coder myself and I thought your website api can be useful to my clients but the idea of buying credit continuously turn me off.
Is there no way people can buy the api one-time instead of refilling credit ?
The advantages are:
It's fair, as you only pay what you use.
It's easy to use: You only need to send ethereum to a deposit address to refill your credits
The disadvantages are:
You still need to refill credits continously (if you don't automate this process)
There is currently no way to pay with paypal, credit card or something
Not everyone likes the pay as you go system and a monthly subscription might work better for some users.
If you have an idea of how the pricing system can be improved, please let me hear.
My suggestion here may not be useful because your business is profit oriented and it will always come first when any critical decision are to be taking.
Regardless that, i will suggest that you should try to look for cheaper resources to build a less expensive and cheaper to maintain infrastructure, this will bring in more users and you can leverage profits on bigger number of users.
You can charge a cheap set up fees and very cheap monthly fees.
Please note that there are other alternatives to achieve what you are providing.
Thank you very much for your feedback. I guess we will be able to lower our pricing when there are more users. For now we will stay with our different monthly pricing plans and reinvest the money to build a better, more secure and feature rich solution.
December 20, 2018, 04:48:10 AM
bump
December 18, 2018, 11:32:02 AM
bump
September 27, 2019, 10:57:26 AM
You may need to delete some of your bumps in order to bring sanity to your thread.
I am a coder myself and I thought your website api can be useful to my clients but the idea of buying credit continuously turn me off.
Is there no way people can buy the api one-time instead of refilling credit ?
Hello! Thanks for your feedback. As we have continously costs for running the infrastructure, we also need to charge for API usage continously. From what I see the credits system has advantages but also some disadvantages.I am a coder myself and I thought your website api can be useful to my clients but the idea of buying credit continuously turn me off.
Is there no way people can buy the api one-time instead of refilling credit ?
The advantages are:
It's fair, as you only pay what you use.
It's easy to use: You only need to send ethereum to a deposit address to refill your credits
The disadvantages are:
You still need to refill credits continously (if you don't automate this process)
There is currently no way to pay with paypal, credit card or something
Not everyone likes the pay as you go system and a monthly subscription might work better for some users.
If you have an idea of how the pricing system can be improved, please let me hear.
My suggestion here may not be useful because your business is profit oriented and it will always come first when any critical decision are to be taking.
Regardless that, i will suggest that you should try to look for cheaper resources to build a less expensive and cheaper to maintain infrastructure, this will bring in more users and you can leverage profits on bigger number of users.
You can charge a cheap set up fees and very cheap monthly fees.
Please note that there are other alternatives to achieve what you are providing.
December 13, 2018, 08:17:16 AM
bump
September 26, 2019, 02:09:08 PM
Updated the Bitcointalk Thread to show the correct info about our new pricing system.
December 06, 2018, 04:36:36 AM
bump
September 22, 2019, 01:59:31 PM
We successfully migrated to the monthly pricing system, smaller design updates have also been made. We're looking forward to implement more features soon.
1. You do not have access to the private key, we also do not have access to it as we don't store private keys on our system. We are saving the keystore files kinda safe, whenever a password is provided, we are going to send the transaction. Also, we are working with multiple layers for ensuring security.
2. Currently we are just offering to generate addresses with our services, and using cronjob or something else the balance can be checked by using the getEthereumBalance or getTokenBalance functions. We are working on a IPN system, which will notify changes to the balances to a customer specified URL. There will be forwarding addresses, too. We just weren't able to publish this feature yet.
3. Sure! You can see this in the example response on our Docs. Currently we can get the following info about an ERC20 transaction (by just providing the transaction hash): Token name, Token symbol, blockhash, blocknumber, transaction index, sender, receiver, contract address, gas price, gas amount, confirmations. Also, this will work with any ERC20 compliant token.
- Send ERC20 tokens automatically
How does the signing operation take place? Do we get access to the private key?- Receive ERC20 tokens automatically
Do you send notification against each incoming transaction? Is there any forwarding address involved? If not, then how a sender is mapped to an incoming transaction?- Get info on ERC20 transaction by hash
Is there any list of info that you provide against an ERC20 transaction?1. You do not have access to the private key, we also do not have access to it as we don't store private keys on our system. We are saving the keystore files kinda safe, whenever a password is provided, we are going to send the transaction. Also, we are working with multiple layers for ensuring security.
2. Currently we are just offering to generate addresses with our services, and using cronjob or something else the balance can be checked by using the getEthereumBalance or getTokenBalance functions. We are working on a IPN system, which will notify changes to the balances to a customer specified URL. There will be forwarding addresses, too. We just weren't able to publish this feature yet.
3. Sure! You can see this in the example response on our Docs. Currently we can get the following info about an ERC20 transaction (by just providing the transaction hash): Token name, Token symbol, blockhash, blocknumber, transaction index, sender, receiver, contract address, gas price, gas amount, confirmations. Also, this will work with any ERC20 compliant token.
September 19, 2019, 06:37:33 PM
- Send ERC20 tokens automatically
How does the signing operation take place? Do we get access to the private key?- Receive ERC20 tokens automatically
Do you send notification against each incoming transaction? Is there any forwarding address involved? If not, then how a sender is mapped to an incoming transaction?- Get info on ERC20 transaction by hash
Is there any list of info that you provide against an ERC20 transaction? December 03, 2018, 02:05:06 PM
The issue on the Stats site has been fixed.
June 25, 2019, 05:24:27 AM
The project looks very very promising!
We are also very interested in the possibility to access our own existing addresses. Would it be possible to send the address and the key to the API and execute queries? Is that what you mean by "importing keystores" or would the importing have to be done manually? It would also be very helpful if you could create forwarding addresses such as those offered by Blockcypher for Bitcoin. And it would also be great if you could provide a function to display the history of incoming and outgoing transfers of an address.
Do you have anything planned in this direction in the near future?
We are also very interested in the possibility to access our own existing addresses. Would it be possible to send the address and the key to the API and execute queries? Is that what you mean by "importing keystores" or would the importing have to be done manually? It would also be very helpful if you could create forwarding addresses such as those offered by Blockcypher for Bitcoin. And it would also be great if you could provide a function to display the history of incoming and outgoing transfers of an address.
Do you have anything planned in this direction in the near future?
My idea was to manually allow an upload of keystore files which would then be added to the accounts ethereum addresses. However, even then this wouldn't work at all without the password. An option to do the import via API would also be possible. You would just need to send the name of the keystore, the content (json), and the password (Which won't be saved on our servers of course.)
I thought about adding an IPN feature with forwarding addresses earlier (And also began with the development of that), but we are currently lacking development resources to continue this. A history of incoming/outgoing transactions by address is not possible unless we would develop a whole block explorer unfortunately. (We would love to, but don't have the resources for this)
November 29, 2018, 04:51:48 PM
bump
Jump to: