Gotchas & Common Pitfalls

Common integration issues encountered by partners, along with guidance on how to avoid them during development and testing.

These issues are drawn from real integration journeys and support queries. Reviewing them early can save time and prevent unnecessary rework.

Missing registration confirmation email

After registering on the developer portal, you should receive a confirmation email containing a link to activate your account. In some cases, this email may be automatically filtered into your junk or spam folder by your email provider.

✔ Review your junk / spam folder for the registration confirmation email
✔ Ensure emails from the developer portal domain are allowed or whitelisted
✔ If you cannot locate the email, contact your administrator or reach out for support

Registration confirmation link not working

The registration confirmation email contains a link that must be used to activate your developer portal account. For security reasons, this confirmation link expires 48 hours after the email is sent. If the link is opened after this period, it will no longer work and your account will remain inactive.

✔ Use the confirmation link as soon as you receive the email
✔ Ensure the 48‑hour expiry window has not passed

Access tokens expiring mid‑process

Access tokens are short‑lived and are not refreshed automatically. Some integrations request a new token per call, while others forget to refresh expired tokens.

✔ Cache and reuse tokens for their full lifetime.
✔ Refresh tokens proactively before expiry.

Using the wrong subscription key for an environment

A common issue is reusing subscription keys across environments (for example, cloning Test Environment settings into Production).

✔ Ensure each environment uses its own subscription key.
✔ Verify keys in your developer portal profile.