New API Go To Market Checklist

DRAFT - This is a work in progress

Documentation completed and posted in alpha preview (3 weeks prior)
- Static reference
- Swagger
Release notes posted (2 weeks prior)
Current partner communication via email (2 weeks prior)

These instructions are intended to be used for the immediate short-term. We will have documentation and a more formalized process later.

Email the following information to [email protected] so we can create an issue.

Please provide the following:

Project name or service being exposed
Target date to be in production
What path segment you want: http://us.api.concursolutions.com/YOUR-SEGMENT-HERE where “us” will be remapped to “emea” or “apac” eventually, but your segment should be the name of your service, but should not include the word “service”, should be untied to any implementation details (i.e., don’t include “dotnet”, “javascript”, etc), and should be a single segment (i.e. No “foo/bar/“).
What FQDN your service is exposed by (just http://blah.blah.com/, no path segments such as http://blah.blah.com/foo )
What your exposure is (i.e., is your FQDN addressable on the public internet, within Lynnwood, etc)
If you have a Dallas deployment as a DR for a Lynnwood deployment, confirm your fqdn is the same
What authentication you want performed (no auth check, JWT validation, or client certs required… the last is to come, so for now just JWT validation is implemented)
CORS pref - auto reject, auto accept common headers, auto accept custom list, let requests through for fronted service to handle.