Skip to content

Issues: w3c-ccg/vc-api

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.

Sign up for GitHub

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

45 Open 200 Closed
45 Open 200 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider to introduce a manifest describing entry points ('static' endpoints)
#433 opened Nov 24, 2024 by filip26
An asynchronous issuance
#432 opened Nov 22, 2024 by filip26
1
Allow generic/unwrapped VC/VP and specific media types where appropriate
#431 opened Nov 20, 2024 by filip26
OAS rendering for arrays of objects
#430 opened Nov 19, 2024 by brianorwhatever
Add GET Exchange Response endpoint
#429 opened Nov 7, 2024 by jrhender
Clarify the distinction between exchangeId and localExchangeId
#425 opened Oct 3, 2024 by jrhender
3
Clarify how EnvelopedVerifiableCredential and JWTs can be verified
#424 opened Oct 1, 2024 by robdefeo
1
Add support for proofChain to VC API POST credential/issue endpoint
#422 opened Sep 24, 2024 by aljones15
4
Add <fullExchangeId>/protocols endpoint that serves interaction "protocols" object ready for PR Issue ready to be resolved via a Pull Request
#421 opened Sep 13, 2024 by dlongley
@PatStLouis
4
Document that endpoint instances have specific behaviour by default, but can have options ready for PR Issue ready to be resolved via a Pull Request
#419 opened Sep 10, 2024 by msporny
@jrhender
2
Should returning ProblemDetail objects be mandatory? pr exists A Pull Request exists to address this issue.
#414 opened Aug 20, 2024 by msporny
@PatStLouis
6
Create WorkflowConfig object to re-use across API calls ready for PR Issue ready to be resolved via a Pull Request
#413 opened Aug 20, 2024 by PatStLouis
@PatStLouis
2
Make naming scheme for path parameters consistent ready for PR Issue ready to be resolved via a Pull Request
#412 opened Aug 13, 2024 by msporny
@PatStLouis
1
Details of DELETE /credentials/{id} endpoint should be added ready for PR Issue ready to be resolved via a Pull Request
#407 opened Jul 21, 2024 by laysakura
1
Proposal to Recommend Coordinators to Expose the Same Endpoints as Services ready for PR Issue ready to be resolved via a Pull Request
#406 opened Jul 19, 2024 by laysakura
2
Should Issuer Service be directly called? ready for PR Issue ready to be resolved via a Pull Request
#405 opened Jul 19, 2024 by laysakura
@eric-schuh
4
Add presentationSchema option to workflow step ready for PR Issue ready to be resolved via a Pull Request
#403 opened Jul 18, 2024 by dlongley
1
Review uses of challenge and domain and ensure those terms are used for VerifiablePresentaitons ready for PR Issue ready to be resolved via a Pull Request
#402 opened Jul 16, 2024 by aljones15
2
Add examples showing an exchange client sending different VPRs with only acceptedCryptosuites or acceptedEnvelopes ready for PR Issue ready to be resolved via a Pull Request
#399 opened Jul 16, 2024 by dlongley
1
Update /credentials/{{id}} endpoint to return {verifiableCredential} to be consistent with other APIs ready for PR Issue ready to be resolved via a Pull Request
#398 opened Jul 9, 2024 by dlongley
1
Add support for advanced BBS features like pseudonyms
#396 opened Jun 25, 2024 by msporny
1
Should the API define error codes? ready for PR Issue ready to be resolved via a Pull Request
#395 opened Jun 25, 2024 by msporny
2
workflowId should be id in posted and returned workflow configuration ready for PR Issue ready to be resolved via a Pull Request
#393 opened Jun 18, 2024 by dlongley
@PatStLouis
1
Update OAS to latest version ready for PR Issue ready to be resolved via a Pull Request
#385 opened May 14, 2024 by msporny
Verifying and Validating issued VC's ready for PR Issue ready to be resolved via a Pull Request
#379 opened Mar 26, 2024 by PatStLouis
@PatStLouis
5
ProTip! Updated in the last three days: updated:>2024-11-24.