Unable to connect to Sandbox about algosigner HOT 5 CLOSED

Thank you for bringing this to our attention, we initially required the header construct and then switched to requiring it OR just the Algod token value. Neither expected value would be clear unless you've worked with the APIs and the JS SDK. I'll set up a webpage to document what should be done.

In the meantime, the Algod API expects a key to be sent in with the request headers (X-Algo-API-Token), in the case of a Sandbox instance you can find the value by ./sandbox enter algod and then cat algod.token;and placing the value into the Network Headers field. More about this token here (https://developer.algorand.org/docs/reference/sdks/#security-token)

For the PureStake APIs, for example to add BetaNet to AlgoSigner you need to use a full header object in the Network Headers field like {"Algod":{"X-API-key":"<PS API KEY>"},"Indexer":{"X-API-Key":"<PS API KEY>"}} The Key here is one you are assigned when registering at https://developer.purestake.io

from algosigner.

Ahhh. Thanks for clearing that up. I was able to put just the token value in and successfully pull my transactions. I had tried all kinds of variations for the X-Algo-API-Token struct but never tried just putting in the key by itself. I appreciate the help.

from algosigner.

This does not work. I did the cat algod.token as suggested and it returned the aaa... long stream of a's key. I tried to to use this with the sandbox and it responded with a 500 ""message": "failed to retrieve information from the ledger"" message.

from algosigner.

Also the https://developer.algorand.org/docs/reference/sdks/#security-token page is invalid.

from algosigner.

Hello @mkelly1495, here's the updated link to the Algorand documentation: https://developer.algorand.org/docs/rest-apis/restendpoints/#security-token

I recreated the key using goal node generatetoken and was able to connect to it successfully using AlgoSigner.

from algosigner.