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
The backend application will receive selected escrow_address, chain_id and EXCHANGE_ORACLE_URL, then sends a POST [EXCHANGE_ORACLE_URL]/assignment request to the Exchange Oracle.
The user will be able to see all of the jobs assigned to him by given Exchange Oracle using GET [EXCHANGE_ORACLE_URL]/assignment. This solution should support all fields mentioned in the tech-docs.
Acceptance criteria:
The backend must be capable of communicating with the Exchange Oracle via POST and GET requests to the specified endpoint.
The backend can send a POST request to [EXCHANGE_ORACLE_URL]/assignment with the escrow_address and chain_id included in the request body or as parameters, according to the Exchange Oracle's API specifications.
Users should be able to retrieve a list of jobs assigned to them from the Exchange Oracle by sending a GET request to [EXCHANGE_ORACLE_URL]/assignment. This request must support all additional parameters mentioned in tech-docs.
The text was updated successfully, but these errors were encountered:
The backend application will receive selected escrow_address, chain_id and EXCHANGE_ORACLE_URL, then sends a POST [EXCHANGE_ORACLE_URL]/assignment request to the Exchange Oracle.
The user will be able to see all of the jobs assigned to him by given Exchange Oracle using GET [EXCHANGE_ORACLE_URL]/assignment. This solution should support all fields mentioned in the tech-docs.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: