The Request API Access form at https://api-docs.quran.foundation/request-access/ fails on submit with a server error, so it's impossible to obtain API credentials. 1. Operating system: Windows 11 2. The browser: Chrome Version 149.0.7827.103 (Official Build) (64-bit) 3. Screenshots of the bug: (attached) - The filled-in form - DevTools → Network showing the failed request: Request URL: https://qf-form-handler.fly.dev/api/v1/webhook Request Method: POST Status Code: 500 Internal Server Error Response body: {"error":"Failed to process registration"} 4. Steps to reproduce: a. Go to https://api-docs.quran.foundation/request-access/ b. Fill the required fields only — App Name and Email — and tick the "I have read and agree…" checkbox. Leave all the optional OAuth2 fields (Redirect URIs, Logo/Client/Privacy/Terms URLs, Post-logout URIs) blank. c. Click "Submit Request". d. The POST to qf-form-handler.fly.dev/api/v1/webhook returns HTTP 500 with {"error":"Failed to process registration"}. No application record is created. Example payload: { "appName": "BetterMuslim", "email": " mohamadsafwan.1905@gmail.com ", "agreementsAccepted": true } Additional notes: - This is a server-side 500 (not a validation 4xx). It reproduces even with a truly minimal payload — only the required fields: {"appName":"<app>","email":"<email>","agreementsAccepted":true} …so it is not input-dependent; the form handler appears to throw unhandled. - We only need server-to-server content access (client_credentials, scope=content), so no redirect URIs are provided — in case the handler errors when an OAuth client is created without redirect URIs. Impact: blocks new developers from registering for any API access.