Overview
This article catalogs the user-facing error messages that can appear when synchronizing customers through the Stamped.io integration, along with what causes each error and how to resolve it. Errors appear in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs. Each error carries a stable code you can search for on this page.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Some resolutions below refer to your Managed Integration Service Provider (MiSP) — the partner who set up and manages your iPaaS.com integration.
Supported Flows
Add/Update Stamped.io Customer FROM iPaaS.com
Error Collection
Add/Update Stamped.io Customer FROM iPaaS.com
Customer create or update failed
STMD-EXTN-1001 - Error communicating with Stamped.io. {Stamped.io response} (Http Code: {status})
Description: The integration called Stamped.io to create or update the customer and Stamped.io returned an error response. The logged message includes the HTTP status code and the message returned by Stamped.io. Common causes are invalid or expired credentials, an incorrect store identifier, a malformed or rejected value on the customer (often the email address), or Stamped.io being temporarily unavailable.
Resolution: Review the Stamped.io response and HTTP status code in the error log. Confirm the API Public Key, API Private Key, and API Store Hash on the subscription are correct and active, and review the customer's mapped values — in particular the email address — for anything Stamped.io would reject. Re-run the transfer from the Manual Sync page. If the response indicates a temporary condition, try again shortly. If it persists, your MiSP can review the mapping and connection.
Subscribe or unsubscribe failed
STMD-EXTN-1002 - An error occurred running the call to subscribe/unsubscribe{Stamped.io error detail}
Description: After creating or updating the customer, the integration made a follow-up call to set the customer's survey and review-email subscription state, and Stamped.io returned an error (the status code and Stamped.io's message are included in the logged error). This step runs only when the subscription field is mapped and the desired state differs from the customer's current state in Stamped.io.
Resolution: Confirm the customer has a valid email address mapped, since the subscribe and unsubscribe operations identify the customer by email. Confirm the Stamped.io credentials are active, then re-run the transfer. If it persists, your MiSP can review the mapping.
Note: The customer create/update and the subscription reconciliation are separate operations. A customer can be created or updated successfully and then report an error only on the subscription step; in that case the customer exists in Stamped.io but its subscription state may not yet match the mapped value. Re-running the transfer reconciles it.