cancel
Showing results for 
Search instead for 
Did you mean: 

500 errors on some requests

Occasional Contributor

500 errors on some requests

I am using the ruby gem for the API and starting on the Sep 3, I started to get some 500 errors for some calls for some of our authorized accounts.

 

@api = ConstantContact::Api.new(api_key)

 

# This will work fine for all our accounts

@api.get_contacts(access_token, :limit => 500, :status => 'OPTOUT')

 

# This one however will explode for some of our accounts

@api.get_contacts(access_token, :limit => 500, :status => 'ACTIVE')

 

RestClient::InternalServerError: 500 Internal Server Error
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in `process_result'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in `block in transmit'
from /usr/local/lib/ruby/2.1.0/net/http.rb:853:in `start'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient.rb:68:in `get'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/bundler/gems/ruby-sdk-a4ea7bb6f0da/lib/constantcontact/services/contact_service.rb:20:in `get_contacts'
from /home/gshift/engine/shared/bundled_gems/ruby/2.1.0/bundler/gems/ruby-sdk-a4ea7bb6f0da/lib/constantcontact/api.rb:47:in `get_contacts'

2 REPLIES 2
Occasional Contributor

Re: 500 errors on some requests

bump

Honored Contributor

Re: 500 errors on some requests

Hello,

 

Based on what you've described, it sounds like this issue is specific to a few accounts and likely need to be researched while looking at those accounts. Would it be possible for you to send an email to us so that we can look into this directly and find a way to resolve the problem? You an contact our API Support team directly at webservices@constantcontact.com

 

If possible, it would help if you can include in the email your API Key and any accounts that you know have been impacted.

 

Best Regards,

Elijah G.
API Support Engineer