Integrations · Getting started
Integration connection errors and how to fix them
Most failed tests are a wrong or incomplete key (401 or 403), a missing field, or a vendor that has not turned API access on. The result names which.
Updated Open this in Tezify
Read the test result first
Test connection shows the vendor's own answer, and the card's guide highlights the matching fix. The table covers what most cards can return.
| What you see | What it means | What to do |
|---|---|---|
| Missing: field names | A required field is empty. | Fill in the named fields and save again. |
| 401 or 403, refused, invalid | The vendor rejected the key or login. | Create a new key, paste it with no spaces, check you used the API password and not a website login. |
| Could not reach the vendor | The request did not get an answer. | Leave the API base URL blank unless the vendor gave you one. Try again in a minute. |
| 429, too many requests | The vendor's rate limit. | Wait a minute and test again. |
| Keys are filled in, but no test call | That vendor has no test Tezify can run. | The first real request proves the keys. Watch the first sync or post. |
| Settings could not be read | Tezify could not read your saved settings just now. | Nothing is wrong with your keys. Try again in a moment. |
When a test fails
- Read the exact message on the card.
- Open the card's guide and find the highlighted fix.
- Fix the key or setting, press Save keys, then Test connection again.
- If the vendor must turn on API access, contact them and wait for their reply before testing again.
Email errors
Gmail 535 or 534 means you used your normal password: see Gmail App Password for SMTP. Microsoft 535 5.7.139 means Authenticated SMTP is off: see Microsoft 365 SMTP email.
Ready to do it? This lives at /admin/integrations in Tezify.