Select to view content in your preferred language

ArcGIS Online webhook > scheduleInfo > startAt

188
3
Jump to solution
01-27-2025 07:59 AM
Labels (2)
coryeicher
Frequent Contributor

Hello,

We are using ArcGIS Online Feature Service webhooks. When creating a wh, how does `scheduleInfo.startAt` work?

https://developers.arcgis.com/rest/enterprise-administration/server/create-webhook/

Specifically, we have a Feature Service with existing features...

  • If we create a webhook and specify startAt == "now", will we receive "FeaturesUpdated" payloads for features that were _created_ before "now", but _updated_ afterwards? This is what we want.
  • If we create a wh and specify startAt == "1 month ago", will we receive "FeaturesUpdated" payloads for all the updates that happened in the past? We want to avoid this because we are not interested in payloads from older changes.

To sum it up, we are trying to sort out how to initialize our system to start capturing "FeaturesCreated" and "FeaturesUpdated" from "now" forward. We need to know about updates to older features, but we do not want to be notified of creates/updates which happened before "now". How we control this from the AGOL webhook side?

Thanks,

 

CORY EICHER
www.eichcorp.com
cory@eichcorp.com
Tags (3)
0 Kudos
1 Solution

Accepted Solutions
EddieIdolyantes
New Contributor

Hello Cory,

The "startAt" property in the scheduleInfo is exactly what you describe, the property is used to designate a specific start date and can also be set to an older date. For online you are allowed to create up to 10 webhooks.

One possible solution that may be helpful in your case is to create multiple webhooks that would send webhook payloads for 'FeaturesCreated' and 'FeatureUpdated' with a 'startAt' == now. You could also create two more webhooks with the same trigger events but with a 'startAt' == last month and possibly set the 'frequency' in the 'recurrenceInfo':

"frequency":"<"second","minute","hour","day","week","month","year">

This is the url to our online REST API documentation that may be of more help: https://developers.arcgis.com/rest/services-reference/online/web-hooks-create-feature-service-.htm

 

Regards,

Eddie

View solution in original post

0 Kudos
3 Replies
EddieIdolyantes
New Contributor

Hello Cory,

The "startAt" property in the scheduleInfo is exactly what you describe, the property is used to designate a specific start date and can also be set to an older date. For online you are allowed to create up to 10 webhooks.

One possible solution that may be helpful in your case is to create multiple webhooks that would send webhook payloads for 'FeaturesCreated' and 'FeatureUpdated' with a 'startAt' == now. You could also create two more webhooks with the same trigger events but with a 'startAt' == last month and possibly set the 'frequency' in the 'recurrenceInfo':

"frequency":"<"second","minute","hour","day","week","month","year">

This is the url to our online REST API documentation that may be of more help: https://developers.arcgis.com/rest/services-reference/online/web-hooks-create-feature-service-.htm

 

Regards,

Eddie

0 Kudos
coryeicher
Frequent Contributor

Hi Eddie,

Great to hear from you!

Thanks for your explanation.

Can you clarify your answer please?

To capture "FeaturesCreated" and "FeaturesUpdated" from "now" forward, we created 2 webhooks (1 for FeaturesCreated and 1for FeaturesUpdated)... Both have a startDate of "now".

Will those webhooks broadcast a payload when an older feature is updated? I.e. the feature was created before "now" but then it is updated after "now". We need to receive those payloads. I am hopeful that I can achieve this with our current setup and not need to add other webhooks to capture edits to older features.

Thanks and again great to hear from you here,

-Cory

CORY EICHER
www.eichcorp.com
cory@eichcorp.com
0 Kudos
coryeicher
Frequent Contributor

Hi Eddie

I did some additional testing. I AM receiving "FeaturesUpdated" webhook payloads  for features created before "now". That is what I want, so I think we are good.

-Cory

CORY EICHER
www.eichcorp.com
cory@eichcorp.com
0 Kudos