Skip to content

Add new API key guides and improve existing documentation#985

Open
martyndavies wants to merge 2 commits intomainfrom
add-new-api-key-guides
Open

Add new API key guides and improve existing documentation#985
martyndavies wants to merge 2 commits intomainfrom
add-new-api-key-guides

Conversation

@martyndavies
Copy link
Copy Markdown
Contributor

New pages:

  • When to Use API Keys: API keys vs JWT/OAuth decision guide with comparison table, decision checklist, retrievable vs irretrievable keys, HTTPS and client-side warnings.
  • API Key Best Practices: 8 practices mapped to Zuplo features covering format, checksum, leak detection, rotation, caching, retrievable keys, masked display, and creation dates.
  • Build Self-Serve API Key Management: end-to-end implementation guide for embedding key management into your own product using the Zuplo Developer API. Includes architecture, Express.js backend example, security with tags, and integration options.

Improved existing pages:

  • api-key-management.mdx: trimmed from 155 to 75 lines, refocused as a landing page that routes to dedicated pages for depth.
  • concepts/api-keys.md: expanded "How validation works" with the explicit 4-step flow and cacheTtlSeconds guidance.
  • api-key-end-users.mdx: expanded Developer API section.
  • api-key-react-component.mdx: explained backend architecture.
  • api-key-api.mdx: added callout linking to self-serve guide.
  • sidebar.ts: added all three new pages to API Keys category.

New pages:
- When to Use API Keys: API keys vs JWT/OAuth decision guide with
  comparison table, decision checklist, retrievable vs irretrievable
  keys, HTTPS and client-side warnings.
- API Key Best Practices: 8 practices mapped to Zuplo features
  covering format, checksum, leak detection, rotation, caching,
  retrievable keys, masked display, and creation dates.
- Build Self-Serve API Key Management: end-to-end implementation
  guide for embedding key management into your own product using
  the Zuplo Developer API. Includes architecture, Express.js
  backend example, security with tags, and integration options.

Improved existing pages:
- api-key-management.mdx: trimmed from 155 to 75 lines, refocused
  as a landing page that routes to dedicated pages for depth.
- concepts/api-keys.md: expanded "How validation works" with the
  explicit 4-step flow and cacheTtlSeconds guidance.
- api-key-end-users.mdx: expanded Developer API section.
- api-key-react-component.mdx: explained backend architecture.
- api-key-api.mdx: added callout linking to self-serve guide.
- sidebar.ts: added all three new pages to API Keys category.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@claude claude bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

Tip: disable this comment in your organization's Code Review settings.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 16, 2026 0:48am

Request Review

The React component is being updated, so remove references to it
as a "drop-in" option from the new pages until the new version is
ready. Removes the tip callout, integration table row, and Next
Steps link from the self-serve guide, and the mention from the
best practices page.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

1 participant