New Webhook Endpoint Capability Now Live – OAuth2 Credential Support 🚀

We’ve just rolled out an enhancement to the Webhook Endpoint configuration API. This update introduces support for specifying OAuth2 credentials when creating or updating webhook endpoints on the Ophelos platform.

📌 Link to API Reference (please read carefully and share widely):
🔗 https://ophelos-api.readme.io/reference/createwebhook

⸻

✅ Summary of What’s New

Ophelos tenants can now include OAuth2 credential configuration directly when registering a webhook endpoint. This removes the need for manual, ad-hoc engineering intervention by the Ophelos team to manage or apply these credentials on behalf of tenants.

This is a positive step forward in our broader initiative to improve Self-Serve capabilities for tenants, empowering them to configure their Ophelos instance with more autonomy and precision.

⸻

🧠 Why This Matters

Previously, any OAuth2 credential handling for webhook endpoints required involvement from our internal engineering team. This often introduced overhead, bottlenecks, and delays.

With this change:

• Tenants gain direct control over their webhook auth config.
• We reduce support burden and operational friction for our internal teams.
• It improves the scalability and maintainability of tenant-specific integrations.

⸻

🔒 Not Breaking Anything

This is a non-breaking, backward-compatible update. There is no action required from tenants who are not using this new capability.

However, we strongly recommend that new or updated webhook configurations now make use of the credentials field to securely handle authentication flows where appropriate.

⸻

✍️ Example Request (with OAuth2 credentials)

curl --request POST  
     --url <https://api.ophelos.dev/webhooks>  
     --header 'accept: application/json'  
     --header 'authorization: Bearer $TOKEN'  
     --header 'content-type: application/json'  
     --data '  
{  
  "url": "<https://example.com">,  
  "enabled_events": ["*"],  
  "version": "v20250401",  
  "credentials": {  
    "oauth2": {  
      "token_url": "<https://example.com/oauth2/token">,  
      "client_id": "client_id",  
      "client_secret": "client_secret"  
    }  
  }  
}'

⸻

📣 What We Need From You

Please proactively share this update with any relevant teams—especially those responsible for:

• Client integrations
• API usage and onboarding
• Support, success, or solution engineering functions

Clear internal communication ensures we avoid duplicate questions or confusion down the line 🙌

⸻

Thanks everyone! This is part of our continued work to improve developer experience and reduce dependencies on our core engineering workflows.