Changes for page API

Last modified by David Persson on 2022/08/11 10:43
From version 6.1
edited by Mikael Widström
on 2020/01/09 11:10
To version 7.1
edited by Mikael Widström
on 2020/01/09 11:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,11 +24,10 @@
24 24  
25 25  === REST-full pattern guidance ===
26 26  
27 -The resources follows REST-full patterns including hyper-media links, we use hyper-media and backend-for-frontend principles to impose business rules and reduce duplication of business logic in front-and back-end.
27 +(% class="lead" %)
28 +The resources follows REST-full patterns including hyper-media links, we use hyper-media and backend-for-frontend principles to impose business rules and reduce duplication of business logic in front-and back-end. Errors uses HTTP friendly status codes as well as detailed "problem+json" responses.
28 28  
29 -Errors uses HTTP friendly status codes as well as detailed "problem+json" responses. All errors that can be avoided by the client is in the **"HTTP status 4XX"** ragne, all errors that must be fixed by payex is in the **"HTTP status 5XX"** range. All errors contains an instance-id, the instance-id should be provided in support questions to simplify the support process.
30 30  
31 -
32 32  ==== Basic resources ====
33 33  
34 34  (% class="box" %)
... ... @@ -94,6 +94,12 @@
94 94  
95 95  === Problems ===
96 96  
96 +(% class="box" %)
97 +(((
98 +Errors uses HTTP friendly status codes as well as detailed "problem+json" responses. All errors that can be avoided by the client is in the **"HTTP status 4XX"** ragne, all errors that must be fixed by payex is in the **"HTTP status 5XX"** range. All errors contains an instance-id, the instance-id should be provided in support questions to simplify the support process.
99 +)))
100 +
101 +
97 97  If an error occur or any validation failed, a "problem" response will be returned.
98 98  Below is a list of problems that can occur:
99 99