Connect to Sweap on Zapier
Sweap uses session authentication to authenticate your account on Zapier.
Required authentication fields
- API key.
- API secret.
Optional authentication fields
Additional authentication instructions
Request keys from Sweap's support at email@example.com.
Learn more about authenticating your Sweap account in Zapier.
About Sweap's app
|Are self-hosted or cloud-hosted accounts supported?||Cloud-hosted accounts only|
|Is a paid Sweap plan required?||No||All plans include API usage. You might have to request a Key at firstname.lastname@example.org
View Sweap's plans.
|Are any special account permissions required?||No||
As soon as we have the API keys and secrets ready to be displayed in all user accounts: Only Admins or Users with API-Permission can view, create or delete API credentials.
All users can use API credentials if they are provided (either by Sweap support or Account admins).
|Are there usage limits?||Yes||50 requests per second|
|Are there pagination limits?||Yes||Page must be equal or greater than 0 (default = 0) Size must be between 1 and 1000 (default = 100).|
|Do trigger samples use real data from your account or generic data?||Generic trigger samples|
|Are custom fields supported?||Yes||Learn more about Sweap's custom fields.|
|Do update actions overwrite or append to existing data?||Overwrite existing data||You can Use "Update Guest" and "Update Contact" actions to update limited fields. Do not modify the Ticket ID/Code once a guest received his Ticket/QR-Code (e.g. via email), otherwise the QR-Code won't work as expected when scanned with the Sweap App. Ticket ID must be unique per Event.|
|Is there any additional info?||Yes||Find additional info about using Sweap in Zapier.|