Skip to content

Brendan O'Brien

← CHALLONGE! Feedback & Support

My feedback

1 result found

  1. Add Webhooks for the API

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Brendan O'Brien commented  · 

    I think, at least initially, this might be simplest to implement as a "something has changed" event that hits the necessary 3rd party endpoint and sends the tournament id/name, time, maybe an event id? If the tournament log were exposed as an api endpoint, then the connected app could query the log securely for any and all events since that event occurred and process them as needed. That could also be paginated to prevent lengthy API calls.

    That allows the outgoing http POST request to be open because it contains nothing but a time and some ids. The subsequent incoming requests for more information would then be secured by Basic Auth. In theory, that should reduce the need for automatic polling of the API by 3rd party apps and allow you to scale the number of required instances based on real demand.

    Brendan O'Brien supported this idea  · 

Feedback and Knowledge Base

(thinking…)