search

adamthedeveloper / wepay-rails

Collect payments from wepay in your rails application.
MIT License
32 stars 24 forks source link

Update to use the correct API endpoints #16

Closed LeBlanc closed 12 years ago

LeBlanc commented 12 years ago

We request that all API calls go to either https://wepayapi.com or https://stage.wepayapi.com so we can keep browser traffic separate from API traffic. See: https://stage.wepay.com/developer/reference/endpoints

Please let me know if you have any questions! Thanks for writing this Rails gem!

SteveAquino commented 12 years ago

Ok I've just pushed the latest update to accommodate the new endpoints. There is now a "UI" endpoint and an "API" end point, so following LeBlanc's code I added accessor methods and lines for the wepay.yml file. Everything is working fine, but if you update your gem you will also have to update your config/wepay.yml file to include the following lines: development/test: wepay_ui_endpoint: "https://stage.wepay.com/v2" wepay_api_endpoint: "https://stage.wepayapi.com/v2" production: wepay_ui_endpoint: "https://wepayapi.com/v2" wepay_api_endpoint: "https://wepayapi.com/v2"

Note that the new endpoint for production does NOT have www in the url. I sincerely apologize for any inconvenience this update may cause, as you will need to change the wepay config file for your app to work properly. Generator templates and tests are all adjusted to the new endpoint, so going forward this error will be resolved.

adamthedeveloper commented 12 years ago

Thanks Andrew for the DOS update. It looks like Steve got it fixed on our end. I'll also add an issue and keep it open for a while so people using the gem can get up to speed. Sorry you guys had that happen. Give my regards to the rest of the Wepay team!

Steve, thanks for putting the fire out.

Adam

SteveAquino commented 12 years ago

Just another update, it looks like we also need to specify a User-Agent in the header when making API calls (including getting an access token). I've added the update and also have Travis back up with 1.9.2 and 1.9.3, it seems that one test was the troublesome one. Hopefully will get the tests redone sometime during the next week.