Overview
This article lists every error the Podium integration can record in the iPaaS.com error logs, with the cause of each and what to do about it. Subscribers and their Managed Integration Service Provider (MiSP) — the partner who owns the subscription's mappings, connection settings, and reconciliation — can review these entries in the iPaaS.com Dashboard under Integration Monitoring > Error Logs.
Every error carries a stable code in the form PODM-{CATEGORY}-{NUMBER}. The code appears at the start of the message in the error log and never changes once published, so you can search this page for the code you see to find its cause and resolution.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Authentication
Contacts and Customers
Invoices and Payments
Configuration and Internal Processing
Error Collection
Connection and Authentication
Access token could not be refreshed
PODM-AUTH-1001 - Authentication failed: unable to retrieve a new access token using the stored refresh token.
Description: The integration presented its stored refresh token to Podium to obtain a new access token, and Podium did not return one. Refresh tokens are invalidated when the Podium app's credentials change, when access is revoked, or after a long period without use.
Resolution: Re-authorize the Podium connection in the iPaaS.com Dashboard so a fresh token pair is issued. If it fails again, confirm the Podium app is still installed and authorized for the account.
Client ID or Client Secret missing
PODM-AUTH-1002 - Authentication failed: the Client ID or Client Secret is missing from the connection settings, so a new access token cannot be generated.
Description: Refreshing the access token requires both the Client ID and Client Secret from your Podium app. One or both are absent from the connection settings.
Resolution: Enter both the Client ID and Client Secret from your Podium app into the Podium connection, then re-authorize.
No valid refresh token
PODM-AUTH-1003 - Authentication failed: no valid refresh token was found, so a new access token cannot be generated.
Description: The integration holds no usable refresh token for this connection, so it has no way to obtain a new access token without a fresh authorization.
Resolution: Re-authorize the Podium connection in the iPaaS.com Dashboard. This happens most often on a connection that was never completed, or one whose stored credentials were cleared.
Client ID not specified
PODM-AUTH-1004 - Unable to complete the Podium authorization: Client ID is not specified in the connection settings.
Description: Raised while completing the Podium authorization. The connection settings contain no Client ID, so no token can be requested.
Resolution: Enter the Client ID from your Podium app into the Podium connection, then re-authorize.
Client Secret not specified
PODM-AUTH-1005 - Unable to complete the Podium authorization: Client Secret is not specified in the connection settings.
Description: Raised while completing the Podium authorization. The connection settings contain no Client Secret, so the token request cannot be signed.
Resolution: Enter the Client Secret from your Podium app into the Podium connection, then re-authorize. A Podium secret is shown only at creation, so a new one must be generated if the original was not retained.
Redirect URL not specified
PODM-AUTH-1006 - Unable to complete the Podium authorization: Redirect URL is not specified in the connection settings.
Description: Podium requires the authorization to return to a registered redirect URL, and none is configured on this connection.
Resolution: Enter the Redirect URL into the Podium connection, and confirm the identical value is registered against your Podium app. The two must match exactly.
Authorization code exchange failed
PODM-AUTH-1007 - Unable to complete the Podium authorization: the temporary code could not be exchanged for a lasting access token.
Description: Podium issued the temporary authorization code, but the follow-up call that exchanges it for a lasting token did not succeed. Common causes are a Client ID and Secret from different Podium apps, an expired code, or a redirect URL that does not match the one registered with Podium.
Resolution: Confirm the Client ID, Client Secret and Redirect URL all belong to the same Podium app, then re-run the authorization so a fresh code is issued.
Contacts and Customers
iPaaS.com customer not linked by email
PODM-BIZL-1002 - Unable to link to the existing iPaaS.com customer using the email address. This may result in duplicate customer records.
Description: Customers are matched on email address before being written to iPaaS.com. That lookup did not resolve a match, so a second customer may be created for the same person.
Resolution: Confirm the contact's email address is populated in Podium and matches the address on the iPaaS.com customer. Contacts whose email differs between systems cannot be matched and will duplicate.
Podium customer not linked by email
PODM-BIZL-1005 - Unable to link to the existing Podium customer using the email address. This may result in duplicate customer records.
Description: Writing a contact to Podium first looks for an existing Podium customer with the same email address. That lookup did not resolve a match.
Resolution: Confirm the iPaaS.com customer's email address matches the one on the Podium contact, and check Podium for an existing contact before re-transferring.
Customer delete not supported
PODM-BIZL-1006 - The delete operation is not supported for customer records in this integration.
Description: A mapping collection is configured to delete customers, which this integration does not implement.
Resolution: Change the mapping collection so it does not request a delete for customers. The integration creates and updates customers but does not remove them.
Customer create failed
PODM-EXTN-1004 - Could not create the customer in Podium.
Description: Podium rejected the call that creates a contact.
Resolution: Confirm the contact supplies the fields Podium requires, in particular a valid phone number or email address, and that the target location accepts new contacts.
Customer update failed
PODM-EXTN-1005 - Could not update the customer in Podium.
Description: Podium rejected the call that updates a contact.
Resolution: Confirm the contact is still linked to a Podium contact that exists, and that no required field was mapped to an empty value.
Invoices and Payments
Location preset name not found in Podium
PODM-VALD-1002 - Cannot create the transaction in iPaaS.com because the location named in the Location preset does not exist in Podium.
Description: The Location preset on the subscription names a Podium location, and no location with that name exists in the connected Podium account.
Resolution: Correct the Location preset so it matches a location name exactly as it appears in Podium. Location names are set in Podium, not in iPaaS.com.
Location preset is empty
PODM-VALD-1003 - Cannot create the transaction in iPaaS.com because the Location preset is empty. Provide a location in this preset.
Description: The Location preset on the subscription has no value, and the integration needs it to decide which Podium location an invoice belongs to.
Resolution: Enter a Podium location name into the Location preset on the subscription, then re-transfer.
Transaction not linked by number
PODM-BIZL-1001 - Unable to link to the existing iPaaS.com transaction using the transaction number. This may result in duplicate transaction records.
Description: Before capturing an invoice, the integration looks for a matching iPaaS.com transaction by transaction number so it updates rather than duplicates. That lookup did not resolve a match.
Resolution: Confirm the transaction number on the Podium invoice matches the transaction already in iPaaS.com. Check iPaaS.com for an existing transaction before re-transferring, and remove any duplicate that results.
Prerequisite customer could not be created
PODM-BIZL-1003 - Unable to create the customer required by this invoice. This will prevent the transfer of the invoice.
Description: Before writing the invoice, the integration creates the customer it belongs to, because the invoice cannot exist without one. That create did not succeed.
Resolution: Look for the customer's own error in the same transfer, which names the specific cause. Resolving it and re-transferring the invoice resolves this error too.
Prerequisite customer could not be created from the email address
PODM-BIZL-1004 - Unable to create the customer required by this invoice from the email address. This will prevent the transfer of the invoice.
Description: When no customer is linked, the integration falls back to creating one from the email address on the invoice. That fallback did not succeed.
Resolution: Confirm the invoice carries a valid email address, and look for the customer's own error in the same transfer for the specific cause.
Invoice delete not supported
PODM-BIZL-1007 - The delete operation is not supported for invoice records in this integration.
Description: A mapping collection is configured to delete invoices, which this integration does not implement.
Resolution: Change the mapping collection so it does not request a delete for invoices.
Invoice payment delete not supported
PODM-BIZL-1008 - The delete operation is not supported for invoice payment records in this integration.
Description: A mapping collection is configured to delete invoice payments, which this integration does not implement.
Resolution: Change the mapping collection so it does not request a delete for invoice payments.
Invoice line total below the minimum
PODM-BIZL-1009 - The total amount of all line items must be greater than 50.
Description: Raised by the Invoice Line mapping filter. Podium will not accept an invoice whose line items total 50 or less, so the transfer is stopped before the call is made.
Resolution: Confirm the invoice's line items total more than 50 before transferring. An invoice below that threshold cannot be created in Podium; the filter can be adjusted in the mapping interface if your Podium account permits a different minimum.
Invoice create failed
PODM-EXTN-1006 - Could not create the iPaaS.com transaction as an invoice in Podium.
Description: Podium rejected the call that creates the invoice.
Resolution: Confirm the invoice has a linked customer, a valid location, and line items totalling more than the Podium minimum. Any accompanying Podium error in the same transfer names the specific field rejected.
Configuration and Internal Processing
Webhook location not specified
PODM-VALD-1001 - At least one of the Webhook Subscription (Organization / Location) setting or a location must be specified.
Description: Podium webhooks are registered against either the whole organization or a specific location. Neither was supplied, so the integration cannot tell Podium what to subscribe to.
Resolution: Set the Webhook Subscription (Organization / Location) setting on the subscription, or provide a location, then save the connection to re-register the webhook.
Podium returned an error
PODM-EXTN-1001 - Podium error response: {errorDetail}
Description: Raised when Podium returns an error body for a call the integration made. The trailing text is Podium's own response, including any additional detail it supplied.
Resolution: Read the Podium response appended to the message; it names the specific rejection. If the detail is not actionable, send it to your MiSP, and to iPaaS.com Support at support@ipaas.com if they cannot resolve it.
Podium call failed without a response
PODM-EXTN-1002 - {transportError}
Description: Raised when the call to Podium failed before a response body was received, so the message is the underlying transport error rather than anything Podium said. Timeouts and DNS or TLS failures land here.
Resolution: Retry the transfer once Podium is reachable. If it persists, confirm the API URL on the connection is correct and that outbound access to Podium is not being blocked.
Podium rejected the call
PODM-EXTN-1003 - Error calling Podium {action} (Http Code: {status}) with rate-limit details and response content
Description: Raised when Podium returns a non-success HTTP status. The message names the operation attempted, the HTTP status, Podium's rate-limit headers, and the response content. The rate-limit values are included because Podium throttles per token and per account, and a burst of transfers can exhaust either.
Resolution: Read the HTTP status first. A 401 or 403 points at the connection's credentials; a 429 means a rate limit was hit, in which case the retry-after value in the message tells you how long to wait. Staggering large transfers avoids the throttle.
Connection unavailable during webhook update
PODM-INTL-1001 - Unable to locate the Podium connection while updating the webhook subscription.
Description: The integration lost its Podium connection context part-way through updating the webhook subscription, so the update could not be sent.
Resolution: Re-save the Podium connection to re-establish the webhook subscription. If it persists, report it to your MiSP; this is not caused by mapping configuration.