Skip to content

Clarify API key registration fields#5585

Open
ekamran wants to merge 1 commit into
WordPress:mainfrom
ekamran:sftq/clarify-api-key-registration-fields
Open

Clarify API key registration fields#5585
ekamran wants to merge 1 commit into
WordPress:mainfrom
ekamran:sftq/clarify-api-key-registration-fields

Conversation

@ekamran
Copy link
Copy Markdown

@ekamran ekamran commented Jun 3, 2026

Summary

  • Clarifies that API key registration names must be unique across registered Openverse API applications
  • Adds clearer schema help text for registration fields
  • Fixes minor grammar in the registration endpoint documentation

Fixes #1803

@ekamran ekamran requested a review from a team as a code owner June 3, 2026 07:10
@ekamran ekamran requested review from dhruvkb and obulat and removed request for a team June 3, 2026 07:10
@openverse-bot openverse-bot added 🧱 stack: api Related to the Django API 🟨 priority: medium Not blocking but should be addressed soon ✨ goal: improvement Improvement to an existing user-facing feature 📄 aspect: text Concerns the textual material in the repository labels Jun 3, 2026
@openverse-bot openverse-bot moved this to 👀 Needs Review in Openverse PRs Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📄 aspect: text Concerns the textual material in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API

Projects

Status: 👀 Needs Review

Development

Successfully merging this pull request may close these issues.

Registration for an API key doesn't disclose constraints on fields

2 participants