Troubleshooting Leadmagic API Internal Server Error with Batch Requests

Denis S. · 2025-11-18T09:23:42.549Z

I am running a column using my Leadmagic API key ( Company/Job openings API). On a 1000 row batch, I get Error message for half of it: The integration failed to run Internal Server Error Is it common, or temporary? Am I doing something wrong in my column (it's a 1 column-active waterfall - I deactivated the rest)? FYI table is here (https://app.clay.com/workspaces/539104/workbooks/wb_0t2z3kcT6H3mC6xzabc/tables/t_0t2z4k7CykCPskcPz47/views/gv_0t5749jgD5NqDwivTEw).

Troubleshooting Leadmagic API Internal Server Error with Batch Requests | Clay

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
It's not typical for half of your rows to return errors when using the LeadMagic Company/Job openings API. Common causes include running out of API credits or issues with your API key. First, check your LeadMagic credit balance. If credits are available, try generating a new API key and reconnecting it. For more details on specific errors, click into the error cells in your table to view the full error message, which can help pinpoint the issue. [1]
Clay Support
APP
·
·
Was that helpful?
Denis S.
·
·
My credit balance is OK. When I run an "Error" row manually, it works. Error message is:
The integration failed to run Internal Server Error
Clay Support
APP
·
·
If your credit balance is fine and error rows work when run manually, the issue may be related to how the batch is processed or temporary API rate limits. It's not typical for half of the rows to error in a batch. Try generating a fresh API key and reconnecting it. For more details, click into the error cells to view the full error message, which can help pinpoint the cause . You can also review your column setup to ensure all required inputs are correct [1].
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you still need help resolving the errors in your batch processing, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?
Denis S.
·
·
I can't see what to add here, as my API keys are working.
Clay Support
APP
·
·
If your credit balance is fine and error rows work when run manually, the issue may be related to how the batch is processed or a temporary API limitation. It's recommended to try generating a fresh API key from LeadMagic and reconnecting it. You can also click into the specific error cells in your table to view more details about each error, which may help identify the cause. If the problem persists, you may need to request a human agent for further assistance.
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
I apologize for the ongoing trouble with your batch processing errors and am here to help if you need further assistance. Would you like to share more details about your setup or the specific errors you’re seeing so we can continue troubleshooting?
Abdul S.
·
·
Hey Denis S. if single rows work but half the batch fails, that’s usually leadmagic rate limits choking the batch, not your setup clay fires multiple calls at once and leadmagic returns internal server rrror when it can’t handle the concurrency regenerate a key if you want, but the real fix is lowering batch size to five to ten or running sequential that stabilizes it instantly
Clay Support
APP
·
·
Batch failures with LeadMagic API, even when single rows work and your API keys are valid, are often due to API rate limits or concurrency issues. Clay may send multiple requests at once, which can overwhelm LeadMagic and result in errors for many rows. Lowering your batch size to 5–10 rows or running the column sequentially can help stabilize results and reduce errors instantly. [1]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with resolving the batch errors or adjusting your setup, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?

Clay Support
APP
·
·
It's not typical for half of your rows to return errors when using the LeadMagic Company/Job openings API. Common causes include running out of API credits or issues with your API key. First, check your LeadMagic credit balance. If credits are available, try generating a new API key and reconnecting it. For more details on specific errors, click into the error cells in your table to view the full error message, which can help pinpoint the issue. [1]
Clay Support
APP
·
·
Was that helpful?
Denis S.
·
·
My credit balance is OK. When I run an "Error" row manually, it works. Error message is:
The integration failed to run Internal Server Error
Clay Support
APP
·
·
If your credit balance is fine and error rows work when run manually, the issue may be related to how the batch is processed or temporary API rate limits. It's not typical for half of the rows to error in a batch. Try generating a fresh API key and reconnecting it. For more details, click into the error cells to view the full error message, which can help pinpoint the cause . You can also review your column setup to ensure all required inputs are correct [1].
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you still need help resolving the errors in your batch processing, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?
Denis S.
·
·
I can't see what to add here, as my API keys are working.
Clay Support
APP
·
·
If your credit balance is fine and error rows work when run manually, the issue may be related to how the batch is processed or a temporary API limitation. It's recommended to try generating a fresh API key from LeadMagic and reconnecting it. You can also click into the specific error cells in your table to view more details about each error, which may help identify the cause. If the problem persists, you may need to request a human agent for further assistance.
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
I apologize for the ongoing trouble with your batch processing errors and am here to help if you need further assistance. Would you like to share more details about your setup or the specific errors you’re seeing so we can continue troubleshooting?
Abdul S.
·
·
Hey Denis S. if single rows work but half the batch fails, that’s usually leadmagic rate limits choking the batch, not your setup clay fires multiple calls at once and leadmagic returns internal server rrror when it can’t handle the concurrency regenerate a key if you want, but the real fix is lowering batch size to five to ten or running sequential that stabilizes it instantly
Clay Support
APP
·
·
Batch failures with LeadMagic API, even when single rows work and your API keys are valid, are often due to API rate limits or concurrency issues. Clay may send multiple requests at once, which can overwhelm LeadMagic and result in errors for many rows. Lowering your batch size to 5–10 rows or running the column sequentially can help stabilize results and reduce errors instantly. [1]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with resolving the batch errors or adjusting your setup, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?