You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: