> For the complete documentation index, see [llms.txt](https://docs.corppass.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corppass.gov.sg/what-you-need-to-know-before-onboarding-a-digital-service-in-corppass/important-things-to-note/callback-urls.md).

# Callback URLs

### **Can I configure multiple Callback URLs?**

Yes, you can configure multiple Callback URLs for a single digital service. The `redirect_uri` in the authentication request must match one of the registered Callback URLs **exactly**, including the protocol (`https://`).

***

### **What happens if my Callback URL is incorrectly configured?**

If the `redirect_uri` parameter in your request does not exactly match one of the registered Callback URLs, Corppass will reject the request with an **invalid\_request** error. Always ensure that the Callback URL is accurate and properly registered in both staging and production environments.

***

### **Can I use a wildcard in the Callback URL?**

No, wildcard characters (e.g., `*`) are not allowed in the Callback URL. Each Callback URL must be explicitly defined in the service configuration.

***

### **Can I update the Callback URL after onboarding?**

Yes, updates to Callback URLs is allowed. However, all changes should be tested in the staging environment before applying them to production.

***

### **Are there any keyword restrictions for Callback or JWKS URLs?**

Yes, both Callback and JWKS URLs cannot contain the words 'singpass', 'corppass', or 'myinfo' as part of efforts to combat scams.