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

The endpoint https://wallet.walt.id/exchange/issuance could not be found in the current API. #289

Closed
ChangoBuitrago opened this issue Apr 1, 2024 · 3 comments

Comments

@ChangoBuitrago
Copy link

Based on the documentation:

"authorizeBaseUrl - is used to modify the start of the UR OID4VC request URL. If you are using the cross-device flow, where you will display the URL as a QR code, you can leave the value as openid4vp://authorize or if you don't know the wallet the user will be using to claim the credential. If you are using the same device flow, where you already know the user's wallet and want the user to be able to go directly to it, you can use the wallet URL path that is able to receive an OIDC request as a query parameter. Our wallet for example can receive OID4VC requests here https://wallet.walt.id/exchange/issuance."

Is the documentation outdated, or is the endpoint no longer supported? I appreciate this feature because it allows me to enhance interoperability with other wallets, which is a strong requirement for me.

Thank you for your help.

Copy link

This issue has been marked as stale.

@github-actions github-actions bot added the Stale label May 31, 2024
@waltkb waltkb removed the Stale label Jun 4, 2024
@waltkb
Copy link
Contributor

waltkb commented Jun 25, 2024

The /exchange/issuance exists on a wallet level (= /wallet/{wallet-id}/exchange/issuance), you can use /api/siop/initiateIssuance and /api/siop/initiatePresentation, which have a wallet selector.

@taminobaumann update docs?

@SuperBatata
Copy link
Contributor

@ChangoBuitrago Thank you for bringing this issue to our attention. After reviewing the details, I found that my colleague has already addressed this issue. Therefore, I am closing it now. If you have any further questions or concerns, feel free to let us know.

Thank you for your understanding and support.

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

3 participants