Podium Installation Instructions

Go to Subscriptions, click Search Certified Integration Marketplace, and Subscribe.
​

Click the Podium integration tile.
​

Click the Subscribe button.

Enter the name of the subscription and select a version. It can be set to any relevant and unique subscription name within the company where this subscription is created.

Select Create Default Mappings (recommended). If you don’t want to create default mappings and want to create all mappings by yourself then un-check this box.

Enter the value for the System to Perform Duplicate Invoice Checking, the System ID from iPaaS.com that is used to verify whether an invoice already exists in another system before creating it again. Its primary purpose is to prevent the creation of duplicate transactions or invoices across integrated systems, ensuring that only unique records are created while existing ones are updated when necessary.

Enter the Webhook Subscription to Organization or Location, needed to determine whether webhooks should be created for the entire organization or for all locations. When you create a webhook in Podium, you must associate it with either a location or an organization, providing the locationUid or the organizationUid. See the Podium documentation on Webhooks.

Enter the Location name, needed to tell the system which specific Podium location the webhook should be created for. The value should be either the location UID (GUID) or the exact location name (e.g., “Mt. Mansfield Ski Park”).

Enter the API URL endpoint. The Podium API URL is instance-based and different for all instances.

Enter the value for Excluded Invoice Characters for Matching, which tells the system which specific symbols or characters to ignore when linking your POS/ERP to Podium. For example, your POS might generate INV#1066 but Podium or your payment processor might only record 1066.
The system sees INV#1066 and 1066 as two different identifiers. In this case, you would enter INV# and the integration will reduce the ID to 1066.

Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests. It protects system performance by controlling the number of API requests that can run simultaneously, ensuring fair usage.

Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured. If an integration makes too many requests within this time window, additional requests are rejected until the window resets.

Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that the subscription can process for a user or integration. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can process for an integration at one time. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Click Apply to save the settings.

Go to your Podium Subscription Settings.

Click the Authentication icon :
​

A new browser window opens, requesting permissions for the application.

While logged into Podium, click Authorize when prompted.

On the next page, click Close Page.

Refresh the subscription, and the access token value should now be present.
​

Initiate a sample data pull. (To iPaaS.com).

Initiate a sample data push. (From iPaaS.com).

Run an end-to-end business process.

Validate key features like field mappings, workflow triggers, and logging.

Review integration logs in iPaaS.com.