Closed lafidi closed 3 years ago
Thanks for your contribution. Since the onboarding team just propagate the API given by backend developers we requested a confirmation.
DCC-Server will be fixed for correct HTTP code (201)
Does that mean you are adapting the server to the documentation? So every developer and software provider has to adapt his software again?
If the '200' status code is currently used by an unknown number of 3rd party providers within their work flow, and the submission of DCCs to the clients (CWA) is based/dependent from successfully reiceiving a '200' response, this will result in thousands of non-delivered DCCs when TSI can't manage to push that information to all parties and warranting enough time (weeks?) to adapt their implementations.
usage shows that the result is always HTTP status code 200 instead of 201. Correction in api description would be nice.