We all started somewhere! Share your experience on the Get Advice: Let's Get Started Sweepstakes thread and be entered to win a $100 credit on your Constant Contact account.

Redirect URI error. 'http://localhost:8888/scribe' isn't accepting while configuring the application

SOLVED
Go to solution
sasik67
Regular Participant

Redirect URI error. 'http://localhost:8888/scribe' isn't accepting while configuring the application

Hi everyone..

                        I am trying to integrate Constant contact with our application. I have to debug it in my local system. I am trying to give http://localhost:8888/scribe as redirect uri but it isn't accepting showing error that This value does not match the required expression. Without this i can't debug in my local system.

 

                        Please help me to solve this.

 

  

1 ACCEPTED SOLUTION
DaveBerard
Moderator

Thanks for reporting this.  It looks like the validation we are using for the redirect uri field doesn't currently accept localhost.  It currently requires an valid top level domain in the URI.  We are opening up an issue with Mashery, our provider for API key management, to update the validation to allow localhost domains to be submitted. 

 

Apologies for the inconvenience here, it will take some time to get this updated.  Currently, the formatting requirements are: http{s}://{optional_sub_domain}.{domain}.{top_level_domain}:{optional_port}/{optional_path}

Dave Berard
Senior Product Manager, Constant Contact

View solution in original post

4 REPLIES 4
DaveBerard
Moderator

Thanks for reporting this.  It looks like the validation we are using for the redirect uri field doesn't currently accept localhost.  It currently requires an valid top level domain in the URI.  We are opening up an issue with Mashery, our provider for API key management, to update the validation to allow localhost domains to be submitted. 

 

Apologies for the inconvenience here, it will take some time to get this updated.  Currently, the formatting requirements are: http{s}://{optional_sub_domain}.{domain}.{top_level_domain}:{optional_port}/{optional_path}

Dave Berard
Senior Product Manager, Constant Contact

View solution in original post

sasik67
Regular Participant

Thanks for your response..

We are opening up a ticket to allow the following valid redirect_uri formats as well, will update when we have this done:

 

http://localhost:{optional_port}/{optional_path}

http://x-{some_dummy_name}/{optional_path}

 

Both of these are reserved by the HTTP spec as special URLs with special meanings and will be added to our redirect_uri validation support.  Hope to have this fixed soon!

Dave Berard
Senior Product Manager, Constant Contact
sasik67
Regular Participant

Greate...Please let me know when it is completed..

Developer Portal

View API documentation, code samples, get your API key.

Visit Page