See what the Podium integration can do →

This article lists the Podium API endpoints the integration uses, grouped by the type of record they act on. It is useful for firewall allow-listing, understanding data flow, and checking whether the integration is affected when Podium publishes a change to its API.

The integration uses Podium's REST API (version 4). The base URL is the value configured in the subscription's API URL setting; in the endpoint patterns below, [Base URL] stands for that value (for example, https://api.podium.com).

Retrieves a Podium contact by its identifier (contact Uid, email address, or phone number). Used during TO iPaaS.com transfers to read the full contact record.

Creates a contact in Podium. Used during FROM iPaaS.com transfers.

Updates an existing Podium contact, located by email address or phone number. Used during FROM iPaaS.com transfers.

Every invoice call requires a location. The location is taken from the subscription's Location setting (for TO iPaaS.com reads) or from the invoice's locationUid (for FROM iPaaS.com writes).

Retrieves a single Podium invoice by its Uid for a given location.

Lists invoices for a location.

Creates an invoice in Podium. Used during FROM iPaaS.com transfers.

Lists the Podium locations available to the connected account.

Retrieves a specific Podium location by its identifier.

Finds a Podium location by name. Used to resolve the Location setting to a location identifier.

The integration manages the Podium webhook subscription on your behalf, using the endpoints below.

The integration authenticates with Podium using OAuth 2.0. Access tokens are obtained and refreshed against Podium's OAuth token endpoint. iPaaS.com manages this exchange automatically once you authorize the connection; no subscriber action is required for routine token refresh.