Documentation on protocol page pointing to endpoint that does not respond #14
Description
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:
{
"versions": ["1.0-draft"],
}However, doing that doesn't return anything. But this works:
curl https://beta-bridge.simplefin.org/simplefin/info
Which returns:
{"versions":["1.0-draft"]}Also the QuickStart mentions the sample token of aHR0cHM6Ly9icmlkZ2Uuc2ltcGxlZmluLm9yZy9zaW1wbGVmaW4vY2xhaW0vZGVtbw== which decodes to https://bridge.simplefin.org/simplefin/claim/demo (and in theory should return https://user123:[email protected]/simplefin via curl), but it doesn't behave like so. Instead, calling curl returns a redirect to beta-bridge.simplefin.org.
Likewise, calling curl "https://user123:[email protected]/simplefin/accounts" also returns no data due to this redirect.
On the other hand, if I decode aHR0cHM6Ly9iZXRhLWJyaWRnZS5zaW1wbGVmaW4ub3JnL3NpbXBsZWZpbi9jbGFpbS9ERU1P into https://beta-bridge.simplefin.org/simplefin/claim/DEMO, provided by the Developer's Guide, and then curl -X POST "https://beta-bridge.simplefin.org/simplefin/claim/DEMO", I successfully retrieve https://demo:[email protected]/simplefin and then I'm able to follow the quick start with ACCESS_URL="https://demo:[email protected]/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.