Suggest best practice to save 3rd party webhook requests timestamp details with in AEM 6.5 to avoid older request from processing.

Question

Hi All,

I have an use case where a 3rd party system make a post call to AEM author and post a payload (this is webhook scenario).

Based on the timestamp of the request, I should ignore older requests.

For this I’m thinking to store under /content to verify timestamp like below,

/content/abc/en

/webhooks

/webhook-id

-timestamp - Date - <time stamp value>

So that, whenever requests comes in, i can fetch respective node and compare timestamps.

If that is latest one process the request & update the timestamp.

If that is older than existed timestamp will ignore.

Please suggest me the best practice in this case.

Thanks,

Raju.

arunpatidar · Accepted Answer

Thanks for the explanation.

But i still didn't get the point of storing webhook request timestamp in each article page instead in webhook id page (as i mentioned above).

Thanks,

Raju.

Hi @rajumuddana
Creating a page solely for storing data is not the optimal solution; instead, you can create nodes under `/var`.

arunpatidar · Answer

It depends on what webhook/request payload used for

Content-related payload: If the payload affects the creation or update of content, pages, or assets, it's appropriate to store the timestamp directly as a property(e.g. webhook-sync-timestamp) in the related content node (e.g., under /content/abc/en).
Non-content-related payload: If the payload is not directly related to content, storing timestamps and other webhook-related data under /var is more appropriate. The /var directory is designed for storing system-related or process-related data that isn’t directly tied to the content hierarchy. Example/var/webhooks/abc/en/webhook-id - timestamp - Date - <time stamp value>

Sign up