The gigs.added webhook is sent only when an account’s data is refreshed (does not include initial data retrieval) and a new gig is retrieved.
Sent when gigs are added, updated, or removed. If you need to access to gig data as soon as it is available:Documentation Index
Fetch the complete documentation index at: https://docs.argyle.com/llms.txt
Use this file to discover all available pages before exploring further.
gigs.partially_synced webhook is sent when gigs going back a specified number of days prior (starting from the date when the account was added) have been retrieved during initial data retrieval for a newly connected account.gigs.fully_synced webhook is sent when all gigs have been retrieved during initial data retrieval for a newly connected account.gigs.partially_synced webhook when especially time-sensitive. The gigs.fully_synced webhook will only be sent when all gig data has been retrieved, which may take up to several hours in these cases.Username = api_key_id, Password = api_key_secret
gigs.added
Your name for the webhook subscription.
Where you want to receive webhook delivery. This can be either a backend URL that you manage, or a URL provided by a webhook management service. Argyle handles URL encoding for webhook URLs. Send the URL in its normal, unencoded form.
Optional secret used to verify webhooks.