No delete endpoint for cards #5

Closed
opened 2026-06-22 11:35:20 +02:00 by kalipso · 2 comments
Owner

The generated openapi spec do not provide a delete endpoint for cards. Instead there is some GET endpoint /cards/delete. Through the specs it is not clear what this endpoint is doing, or what arguments it needs.

Please provide a DELETE endpoint /cards/{card_id}, consider removing the other one if there is no special need for it.

The generated openapi spec do not provide a delete endpoint for cards. Instead there is some GET endpoint `/cards/delete`. Through the specs it is not clear what this endpoint is doing, or what arguments it needs. Please provide a DELETE endpoint `/cards/{card_id}`, consider removing the other one if there is no special need for it.
ahtlon was assigned by kalipso 2026-06-22 14:53:01 +02:00
Author
Owner

To be able to identify which card should be deleted/deactivated we need some form of identifier within the model. Adding a field "Name" of type string should be sufficient.
This value must be provided during creation within the body of the post request.

To be able to identify which card should be deleted/deactivated we need some form of identifier within the model. Adding a field "Name" of type string should be sufficient. This value must be provided during creation within the body of the post request.
Owner

No, the delete endpoint is an action for the scanner. It scans the next card, finds the key, then looks it up, deletes the db entry and clears the card . User input is not required for this action. I can change the operation to DELETE tho.

No, the delete endpoint is an action for the scanner. It scans the next card, finds the key, then looks it up, deletes the db entry and clears the card . User input is not required for this action. I can change the operation to DELETE tho.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: malobeo/gatekeeper#5