-
Notifications
You must be signed in to change notification settings - Fork 1
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
Unable to buy from amazon and ebay #2
Comments
Made a post here, we'll see what happens Others are complaining about other aspects of this service, so we may have to drop this app if it is no longer being supported. |
hey this is Phil from all4btc. we have gone through many necessary upgrades and had to move a lot around. after taking care of customer support issues that backed up, we'd love to be a part of this beautiful app again. |
@phillux Can you link us to the documentation for your current API? |
Not much of a API documentation to speak of. One can submit a request to https://all4btc.com/p/anywhere with the following mandatory URI encoded fields. full_name <- Mandatory, Example: curl 'https://all4btc.com/p/anywhere' --data 'full_name=phil&address_line1=Jessnerstr.+18&address_line2=&city=Berlin&state=-&postal_code=10247&country_code=DE&product_url=http%3A%2F%2Fwww.amazon.de%2Fgp%2Fproduct%2FB00F3288RC%2Fref%3Ds9_simh_gw_p147_d19_i2%3Fpf_rd_m%3DA3JWKAKR8XB7XF%26pf_rd_s%3Dcenter-2%26pf_rd_r%3D0QJSM6JPWYX0MFWH0DSA%26pf_rd_t%3D101%26pf_rd_p%3D455353807%26pf_rd_i%3D301128¬es=&price=1&shipping_price=2¤cy=EUR&email=phil%40bitcoinsberlin.com&x=70&y=18&mail_check=true&tos_check=true' Returns a redirect to https://all4btc.com/invoice?id=???? where one can pay the bitpay invoice, and give feedback/request support on said order. Kind Regards |
A small change on our page introduced the mandatory tos_check field. I have updated the above comment to reflect this. |
@pscTheOne @phillux Would you guys mind patching the app yourselves? |
@w-hive I will have a look at it. |
Getting 404s for API calls to all4btc. @w-hive can you get in touch with their team to follow up on the status of their API?
The text was updated successfully, but these errors were encountered: