Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support for IEX Cloud sandbox environment #116

Closed
addisonlynch opened this issue Mar 5, 2019 · 2 comments · Fixed by #129
Closed

Add support for IEX Cloud sandbox environment #116

addisonlynch opened this issue Mar 5, 2019 · 2 comments · Fixed by #129

Comments

@addisonlynch
Copy link
Owner

Summary

Per IEX Cloud docs

Every account will be assigned two test tokens available via the Console. All the same endpoints as production will be available in the Sandbox Environment. Please note API data will be manipulated to scramble values, and is not suitable for production usage. We’ve also updated the Usage Report to allow you to view the number of test messages the same way as production message usage.

How to use
The base url is https://sandbox.iexapis.com
Your test token is available on the console by click the “View Test Data” toggle in the nav.
All tier features are enforced at this time, but you are not limited by the number of calls you can make. Your are not charged for test usage.
Test tokens look like Tpk_ and Tsk_.
To make a call for test data, use the same url, but pass your test token.

@addisonlynch addisonlynch mentioned this issue Mar 5, 2019
29 tasks
@addisonlynch addisonlynch added this to the rls 0.4.1 milestone Mar 26, 2019
@addisonlynch
Copy link
Owner Author

There are a number of provider-related issues that have been raised in regards to migrating the iexfinance test suite to the IEX Cloud sandbox environment:

@Danabs82
Copy link

Has this been resolved? Not being able to use the sandbox basically kills the usefulness of this library.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants