Post on Mar 19, 2025

To get help with the issue shown in your screenshot, we'll need a few more details: 1. A summary of what's happening 2. Any specific error messages you're seeing 3. A link to the table, workbook, or page in the app where you're experiencing this issue If you're seeing an "Error evaluating formula" in the output column, try refreshing your browser using Cmd + Shift + R (on Mac) or Ctrl + Shift + R (on Windows). This often resolves such issues. If the problem persists after trying this, please provide the additional details mentioned above so we can better assist you.

To use your BounceBan API key in a request with Clay, you can follow these steps: 1. In Clay's HTTP API integration, set up your request with the following details: • Method: Choose the appropriate HTTP method (GET, POST, etc.) • Endpoint: Enter the BounceBan API endpoint • Headers: Add an "Authorization" header with the value "API KEY" (replace KEY with your actual BounceBan API key) 2. Configure any necessary query parameters or body data for your specific BounceBan API request. 3. Use this setup in your Clay workflow, such as in a "write to table" operation or other HTTP API integrations. Remember to keep your API key secure and don't share it publicly.

Sources: HTTP API with Clay Guide: Integrate with Catch-all Verifier using HTTP API

If you're still having issues with your BounceBan API key in Clay, let's troubleshoot: 1. Double-check your API key: Ensure it's correctly copied from BounceBan. 2. Verify the HTTP API setup in Clay: • Confirm the correct HTTP method • Check the endpoint URL • Ensure the "Authorization" header is set to "API KEY" (replace KEY with your actual BounceBan API key) 3. Review any query parameters or body data required for your specific BounceBan API request. If the issue persists, please copy and paste the exact JSON configuration you're using in Clay (omitting the actual API key) so we can troubleshoot further.

Source: HTTP API with Clay

Hey Veena, thanks for reaching out. Looking at your table now it appears as though this column is running successfully! Let me know if I'm missing something here or how else we can help! :)