Trying to connect an API via HTTP API enrichment but getting errors. See screenshot attached and here is the API Documentation. Trying to use the GET/validation/email https://app.swaggerhub.com/apis/NYMBLR/NymblrDataAPIv1/1.0.0#/Validation/get_validation_email
If you're experiencing errors with the HTTP API enrichment, here are the key steps to resolve them: 1. Check your Body section formatting: • Ensure all text strings are enclosed in double quotes • Remove any trailing commas • Verify proper JSON syntax 2. For dynamic variables: • Enclose string variables in quotation marks • Numbers don't need quotes (except for numbers with trailing zeros) • If combining plain text with dynamic column tags, create a Formula column first 3. Additional troubleshooting steps: • Check for extra spaces, colons, and brackets • Copy-paste the body into a text editor to spot hidden characters • Verify you're using the correct API keyFor quick validation, you can use a JSON validator like JSONLint to check your formatting. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Hi Doug, could you let me know which specific table you're working in? Based on the error, I'm guessing they don't like the [] brackets. So you'll want to use Bearer ReplaceThisWithYourToken.
ID/URL is fine, just drop it here! https://downloads.intercomcdn.com/i/o/w28k1kwz/1347419411/65baf32e1d2a789ffba395c6d35c/CleanShot+2025-01-22+at+_42I1FzxXHf%402x.png?expires=1737990900&signature=abbcd23b31fe6145e981ed2df1682527563de918faa019bd8012295759f6d4e4&req=dSMjEc1%2FlIVeWPMW1HO4zVws4pY%2BBFShgvYjA82bedDmjA%3D%3D%0A Authorization tokens are entered in the "Select HTTP API (Headers) account" section when editing the HTTP API column. (Step 6 here: https://www.clay.com/university/guide/http-api-integration-overview
Thank you very much! Nimbler just wanted us to simplify the Authorization value. Removing the quotes and brackets does the trick. Before: https://downloads.intercomcdn.com/i/o/w28k1kwz/1353533669/a06ec6fc72ba99ce94d2c4352031/20250127-before.png?expires=1737998100&signature=61da6003f407b0cf6f306abde68cc7823b677df8d32bf8a3c2c3eb40f2b7a1fe&req=dSMiFcx9nodZUPMW1HO4zYS39lBL7r0Maz3knvOPd1Mnsc32piu4Wjg1T%2FSz%0A5Fji%0A After: https://downloads.intercomcdn.com/i/o/w28k1kwz/1353533800/a08623e19c147a2bb9aae985fcc9/20250127-after.png?expires=1737998100&signature=b0b2352f765597b216c401a9ce7035ba97ab9d63a163b6f40dbb3a3b0be967d0&req=dSMiFcx9nolfWfMW1HO4zeKoB6FU3SJscL8uszd5ieKKUX9vrbSeEAD3w705%0AYirn%0A From here, try out a few rows/cells where the emails need to be verified, and let's make sure that works out. I'll also mention, to save some credits, you'll probably want to update the conditions for that – "Only run if..." there is no verified email. https://docs.clay.com/en/articles/9642377-conditional-formulas Let me know if you have any trouble!
Based on their API docs, they were expecting the email to be included as a query string appended to the request URL: https://downloads.intercomcdn.com/i/o/w28k1kwz/1353561895/4bf9e3d50cc8a467c97e33910669/20250127-email-parameter-query-string.png?expires=1737999000&signature=31596806e2a4dbca31e5919d289147dd3866b2d85bed1eb8372640ca1433e029&req=dSMiFcx4nIlWXPMW1HO4zVmU1T5JBrxEisdz7iEGWDwLhdWOGyy4gb8px2Kr%0ARxJt%0A
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
.png){kind=logo}
