API endpoint should use url based version, passed as part of path.
Enpoints looks like this:
Default:
Currently Profile API has only 1 API Implementation Version
Profile Service is using 2 authentication types under different URLS
The API Implementation is exactly the same for those 2 types:
auth type | staging API | production API |
|---|---|---|
DEPRECATED CDS Authentication | https://api.cdp-rb.com/ |
...
v1 version:
| stage/profile | https://api.cdp-rb.com/ |
...
| profile |
v1.1 version:
| Nutrition Mule OAuth 2.0 Provider | https://api.cdp-rb.com/stage/ |
...
| v2/profile |
If current default version is v1.1 that means that:
| https://api.cdp-rb.com/ |
...
| v2/profile |
Its recomended that every target service should be deployed per version.
For example if profile-service will service versions v1,v1.1 - deployed two separated versions.
...
All new API Consumers will be using the /v2 path only.
Existing API Consumers will be continuing to use paths as-is untill the Authentication Migration is finished.