docs: require a user agent for proof verification#143
Draft
realmehmetali wants to merge 1 commit into
Draft
Conversation
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.
Changes
User-Agentas a required header on the v4 verify OpenAPI operation403responsesWhy
Backend requests without a user agent can be rejected by bot protection, but neither the generated API reference nor the integration examples made that requirement visible.
Impact
Human readers, generated clients, and coding assistants now receive consistent verification-request guidance.
Closes #82.
Checks
jq empty openapi/developer-portal.jsoncorepack pnpm spellcheck(131 files, 0 issues)mint broken-linksunder Node 24 LTS (no broken links)Disclosure
This contribution was prepared with AI assistance and reviewed against the public repository and public issue #82 only. No private code, production data, or internal implementation details were used.