Skip to content
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

Incorrect base url for the Qubic Transfers API #2

Open
sallymoc opened this issue Jan 2, 2025 · 1 comment
Open

Incorrect base url for the Qubic Transfers API #2

sallymoc opened this issue Jan 2, 2025 · 1 comment

Comments

@sallymoc
Copy link

sallymoc commented Jan 2, 2025

Describe the bug
Base url for the Qubic Transfers API is currently "qxinfo.qubic.org/gotr"

To Reproduce
Executing the curl below will work
curl -X 'GET' \ 'https://qxinfo.qubic.org/gotr/api/v1/ticks/18179783/events/qu-transfer' \ -H 'accept: application/json'

Executing the curl below:

curl -X 'GET' \ 'https://rpc.qubic.org/v1/ticks/18179783/events/qu-transfer' \ -H 'accept: application/json'

returns
{"code":5, "message":"Not Found", "details":[]}%

Expected behavior
The Qubic RPC is the gateway to the Qubic Network.
Qubic Transfer API is listed in the Qubic RPC documentation (https://qubic.github.io/integration/Partners/qubic-rpc-doc.html) however is currently not accessible through the gateway.

Logs
N/A

Environment
N/A

Additional context
The base url starting with "https://rpc.qubic.org/v1" is to be consistent with the current structure of all the other APIs. However, directories and versioning per API could (should) be also considered and understandable that requires more effort and probably splitting in different technical tickets that only the integration team will know better how to do.

@sallymoc
Copy link
Author

@Bertiger I understand they are other tasks to address the integration architecture so this might be addressed there.
Feel free to close this as won't solve if this is the case.

@qubicmio qubicmio added wontfix This will not be worked on and removed wontfix This will not be worked on labels Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants