Add test coverage for the api-keys lifecycle and prefix deletion

[mikewheeleer]

Test the API-key create, list, and delete lifecycle

Description

The api-key endpoints in src/index.ts — POST /api/v1/api-keys, GET /api/v1/api-keys, and DELETE /api/v1/api-keys/:prefix — have no tests. The srk_ key format, the 1–64 char label validation, the list projection that returns only the 8-char prefix (never the raw key), and the prefix-match deletion (including the 404 path) are all uncovered. This issue adds end-to-end lifecycle coverage.

Requirements and context

• Repository scope: StableRoute-Org/Stableroute-backend only.
• Assert POST returns 201 with a key starting srk_ and the echoed label.
• Assert POST rejects an empty label and a label over 64 chars with 400 invalid_request and requestId.
• Assert GET returns items containing prefix, label, createdAt and never the full key.
• Assert DELETE /api/v1/api-keys/:prefix removes the key (204) using the 8-char prefix, and that an unknown prefix returns 404 not_found.

Suggested execution

• Fork the repo and create a branch
• git checkout -b test/api-keys-35-lifecycle
• Implement changes
  • Write comprehensive tests in: create src/__tests__/apiKeys.test.ts.
  • Add documentation: none beyond test names.
  • Derive the prefix from the created key for the delete step.
  • Validate security: explicitly assert the raw key never appears in the list response.
• Test and commit

Test and commit

• Run npm run build, npm run lint, and npm test.
• Cover edge cases: empty label, 65-char label, delete by valid prefix, delete unknown prefix.
• Paste the full npm test output and a coverage summary in the PR.

Example commit message

test(api-keys): cover create/list/delete lifecycle and prefix match

Guidelines

• Minimum 95 percent test coverage for impacted code.
• Clear, reviewer-focused documentation.
• Timeframe: 96 hours.

Community & contribution rewards

• 💬 Join the StableRoute community on Discord for questions, reviews, and faster merges: https://discord.gg/37aCpusvx
• ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — if this issue and the maintainers helped you ship, we'd be grateful for a 5-star rating. Clear questions in Discord and tidy, well-tested PRs are the fastest path to a merge and a reward.

[Jagadeeshftw]

Hi, I’d love to take on this issue! With my expertise in Rust, Stellar, and smart contract development, I can implement a clean and efficient solution.

🚀 Why Me?

• Proven Blockchain Experience – Hands-on work with Stellar, Solidity, and Rust, building secure and optimized smart contracts.
• Open Source Contributor – Actively contributed to 50+ open-source projects, showcasing adaptability and collaboration.
• Efficient & Reliable – I deliver high-quality, production-ready solutions quickly, ensuring security and scalability.

⏱ Timeline

I estimate completing this within 24 hours. Let me know if I can proceed!

[grantfox-oss]

🦊 GrantFox — @Jagadeeshftw has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #83)
2. Your PR will be reviewed by the StableRoute-Org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Jagadeeshftw's PR #87 was approved and merged by @mikewheeleer.

🏆 @Jagadeeshftw: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (398 total points). Track your full progress on GrantFox.

👏 Great work, @Jagadeeshftw! Keep contributing to StableRoute-Org.