Do wildcards still work?

[JasonK108]

This post says wildcards work on subdomains: 

https://community.constantcontact.com/t5/API-Developer-Support/New-Authorization-Service-and-Using-W...

This one mentions it's deprecated in certain places: 

https://community.constantcontact.com/t5/API-Developer-Support/Wildcard-deprecation/m-p/397017?light...

Is there documentation/examples on what is actually supported?

I just tested the following, which was accepted by the UI but didn't work: 

https://*.dev.mydomain.com:1234/TestingPath/

I had to change it to: 

https://myname.dev.mydomain.com:1234/TestingPath/ 

And that worked. 

Is it not working because the wildcard is on a 2nd level subdomain or because wildcards are now simply deprecated?

[John__B]

Hello JasonK108,

Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.

I can confirm that wildcards are only supported in the redirect URI at the lowest level subdomain. Wildcards can’t be used to pass query parameters or specify a port. 

That being said, we are currently investigating an issue where redirect URIs with a wildcard in the lowest level subdomain work successfully with authorization requests when the wildcard character is included in the redirect URI being sent in the request, but result in a 400 error response when the wildcard character is replaced with a variable. We will post again in this thread as soon as we have an update on this issue.

Please have a look and let us know if you have any other questions!

Regards,