Rest v2 bug - 400 error listLeadsources

API Q&A
1

Hey @OmarAlmonte

I mentioned this in Facebook message back in April, but just wanted to post it here to keep things consolidated for you.

I have a Keap application “dh106” - I’m basically just calling listLeadsources and getting all leadsources for this application. When it reaches Leadsource ID 747 - it throws a 500 server error. I have renamed this leadsource to make sure it doesn’t have any weird non-printable ascii characters, but it still breaks.

I don’t want to do delete the Leadsource since I think a server side solution that needs to be implemented by Keap & this is a good reproducible example for the Keap developers to look at.

You can re-produce it by calling listLeadsources and just paginating through all records. You can get 50 records at a time, 500 records, it doesn’t matter - whenever this specific leadsource is included in the results, a 500 error is returned.

Thanks,

Casey

2

@Casey_Page , you’ll have to open a support ticket with our Advanced Support team to investigate that specific instance; while we on the Engineering side can investigate code, we don’t have access to production data by intention as a security precaution. They can assist by pulling the actual values from the live database to determine if there’s something in the record that needs to be corrected or to ticket us for a fix.

3

ok will do. Thanks!