-
Notifications
You must be signed in to change notification settings - Fork 3
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
Documentation on protocol page pointing to endpoint that does not respond #14
Comments
If you add the |
Hey, sorry for the late reply. This is what I get on both Linux and MacOS when I execute the command
|
Hello,
There are some discrepancies between the Protocol Page and the Developer Guide in terms of the demo endpoints.
For example, the protocol lists an example such as:
Request:
curl https://bridge.simplefin.org/simplefin/info
Response:
However, doing that doesn't return anything. But this works:
curl https://beta-bridge.simplefin.org/simplefin/info
Which returns:
Also the QuickStart mentions the sample token of
aHR0cHM6Ly9icmlkZ2Uuc2ltcGxlZmluLm9yZy9zaW1wbGVmaW4vY2xhaW0vZGVtbw==
which decodes tohttps://bridge.simplefin.org/simplefin/claim/demo
(and in theory should returnhttps://user123:pass456@bridge.simplefin.org/simplefin
viacurl
), but it doesn't behave like so. Instead, callingcurl
returns a redirect to beta-bridge.simplefin.org.Likewise, calling
curl "https://user123:pass456@bridge.simplefin.org/simplefin/accounts"
also returns no data due to this redirect.On the other hand, if I decode
aHR0cHM6Ly9iZXRhLWJyaWRnZS5zaW1wbGVmaW4ub3JnL3NpbXBsZWZpbi9jbGFpbS9ERU1P
intohttps://beta-bridge.simplefin.org/simplefin/claim/DEMO
, provided by the Developer's Guide, and thencurl -X POST "https://beta-bridge.simplefin.org/simplefin/claim/DEMO"
, I successfully retrievehttps://demo:demo@beta-bridge.simplefin.org/simplefin
and then I'm able to follow the quick start withACCESS_URL="https://demo:demo@beta-bridge.simplefin.org/simplefin"
I guess the question is, is it intentional to no longer hold the simplefin bridge server at bridge.simplefin.org? If so, should documentation be updated to point to beta-bridge.simplefin.org?
Kind regards,
AJ.
The text was updated successfully, but these errors were encountered: