Issue description
An HTTP 404 response code indicates the Fireblocks API does not recognize the URL endpoint being queried. In almost all cases, this is indicative of a misspelled endpoint. This is much more common when you develop your own API client, as the Fireblocks Python and JavaScript SDK implement the endpoint URLs directly.
Resolution
404 responses to a user-developed API Client
Find out the exact host domain, HTTP method, and URL path used when receiving the HTTP 404 response and the name of the endpoint you're attempting to query from the Fireblocks API documentation.
- Ensure the host domain is api.fireblocks.io. If not, correct the host domain.
- Check the HTTP method and URL path to ensure it matches the HTTP Request section in the Fireblocks API documentation. If the HTTP method or URL path does not match the documentation, correct the given field and retry the operation.
404 Responses to the SDK
Since the Fireblocks Python SDK and JavaScript SDK specify the host domain, HTTP methods, and URL endpoints directly, you should not receive any 404 responses unless the SDK is out-of-date or you have modified the code. If you modify the SDK's code, Fireblocks cannot support it, and you should revert all changes and use the SDK as-is.
- To check whether the SDK is up-to-date, check the latest release of the Python SDK or JavaScript SDK (look for the version with the "latest" tag).
- Then, run the following commands on the machine running the API client to compare the version installed.
For Python SDK users
pip3 show fireblocks-sdk
If it does not match the latest version, they must upgrade to the latest version:
pip3 install fireblocks-sdk -U
For JavaScript SDK users
npm list fireblocks-sdk
If it does not match the latest version, they must upgrade to the latest version:
npm upgrade fireblocks-sdk
SDK is up-to-date and has not been modified
Re-install the respective SDK while overwriting previous SDK files.
For Python SDK users
pip3 install –upgrade –force-reinstall fireblocks-sdk
For JavaScript SDK users
rm -rf node_modules/fireblocks-sdk && npm install
If the 404 issue persists, please contact Fireblocks support.