{
    "version": "https://jsonfeed.org/version/1",
    "title": "AgeKey Changelog",
    "home_page_url": "https://docs.agekey.org/changelog",
    "description": "Stay up to date with the latest updates and changes to the AgeKey API and documentation.",
    "items": [
        {
            "id": "https://docs.agekey.org/changelog/use-agekey-create-requested-parameter",
            "content_html": "<p>We've added a new query string parameter to the Use AgeKey flow redirect so you can support users who don't have an AgeKey yet without sending them back to choose a different verification method.</p>\n<h2 class=\"anchor anchorTargetStickyNavbar_LA01\" id=\"whats-new\">What's New<a href=\"https://docs.agekey.org/changelog/use-agekey-create-requested-parameter#whats-new\" class=\"hash-link\" aria-label=\"Direct link to What's New\" title=\"Direct link to What's New\" translate=\"no\">​</a></h2>\n<h3 class=\"anchor anchorTargetStickyNavbar_LA01\" id=\"create_requested-on-use-agekey-redirect\">create_requested on Use AgeKey redirect<a href=\"https://docs.agekey.org/changelog/use-agekey-create-requested-parameter#create_requested-on-use-agekey-redirect\" class=\"hash-link\" aria-label=\"Direct link to create_requested on Use AgeKey redirect\" title=\"Direct link to create_requested on Use AgeKey redirect\" translate=\"no\">​</a></h3>\n<p>When a user starts the <a class=\"\" href=\"https://docs.agekey.org/guides/use-agekey\">Use AgeKey</a> flow but does not have an AgeKey, the AgeKey service can show a \"use or create AgeKey\" dialog. If the user chooses to create an AgeKey, they are now redirected to your <code>redirect_uri</code> with a <strong><code>create_requested=true</code></strong> query parameter (and no <code>id_token</code>).</p>\n<p>Your app can detect this and send the user to complete verification with another method (such as ID document scan). Once that verification succeeds, direct them to the <a class=\"\" href=\"https://docs.agekey.org/guides/create-agekey\">Create AgeKey</a> flow. They can then continue without having to go back and pick a different method from scratch.</p>\n<h3 class=\"anchor anchorTargetStickyNavbar_LA01\" id=\"updated-docs\">Updated docs<a href=\"https://docs.agekey.org/changelog/use-agekey-create-requested-parameter#updated-docs\" class=\"hash-link\" aria-label=\"Direct link to Updated docs\" title=\"Direct link to Updated docs\" translate=\"no\">​</a></h3>\n<ul>\n<li class=\"\"><a class=\"\" href=\"https://docs.agekey.org/guides/use-agekey\">Using an AgeKey</a> — flow overview, callback handling, and a table of redirect query parameters</li>\n<li class=\"\"><a class=\"\" href=\"https://docs.agekey.org/api/endpoints/use-agekey#response\">Use AgeKey API</a> — response section now documents <code>create_requested</code> and the two redirect outcomes</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_LA01\" id=\"how-to-handle-it\">How to handle it<a href=\"https://docs.agekey.org/changelog/use-agekey-create-requested-parameter#how-to-handle-it\" class=\"hash-link\" aria-label=\"Direct link to How to handle it\" title=\"Direct link to How to handle it\" translate=\"no\">​</a></h2>\n<p>On your Use AgeKey callback page, read the query string and branch on <code>create_requested</code>:</p>\n<ul>\n<li class=\"\">If <code>create_requested=true</code>, send the user to your verification flow so they can complete verification with another method (such as <code>/verify</code>). After successful verification, direct them to the Create AgeKey flow.</li>\n<li class=\"\">Otherwise, continue with <code>id_token</code> validation as before.</li>\n</ul>\n<p>No changes are required if you do not want to support this path; the parameter is only set when the user explicitly chooses to create an AgeKey from the dialog.</p>",
            "url": "https://docs.agekey.org/changelog/use-agekey-create-requested-parameter",
            "title": "Use AgeKey redirect parameter create_requested",
            "summary": "We've added a new query string parameter to the Use AgeKey flow redirect so you can support users who don't have an AgeKey yet without sending them back to choose a different verification method.",
            "date_modified": "2026-02-24T00:00:00.000Z",
            "tags": [
                "changelog",
                "api",
                "use-agekey"
            ]
        }
    ]
}