feat: add public v1 verify API and OpenAPI spec (#352)#437
Open
Sammy-Samy wants to merge 1 commit into
Open
Conversation
- GET /api/v1/verify/:certificateId returns full chain of custody - No authentication required (security: []) - Response includes meter ID, reading, signature, anchor tx, certificate, retirement status - Rate limited (60 req/min per IP via middleware) - Documented in OpenAPI spec with 200/400/404/429 responses - v1 route re-exports from existing /api/verify/[id] handler Closes AnnabelJoe#352
|
@Sammy-Samy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
GET /api/v1/verify/:certificateIdas a public, unauthenticated endpoint for third-party certificate verification, and documents it in the OpenAPI spec.Changes
apps/web/src/app/api/v1/verify/[id]/route.ts— re-exports from the existing/api/verify/[id]handler (no auth required)openapi.yaml— adds/api/v1/verify/{certificateId}path with full schema, example response, and 429 rate-limit responseAcceptance Criteria
GET /api/v1/verify/:certificateIdreturns full chain of custodyType of change
Related issue
Closes #352
Checklist
develop