Skip to Content

Changes for page Validation

Last modified by Danniar Firdausy on 2024/09/19 08:56
From version 27.7
edited by Danniar Firdausy
on 2024/09/19 08:56
Change comment: There is no comment for this version
To version 27.6
edited by Danniar Firdausy
on 2024/09/12 12:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In the previous microlearning session, we covered how to configure a REST service. Now, we will focus on validating the data structure of incoming messages to ensure they meet the required format. This includes how to handle errors when validation fails and how to notify the client about these issues. By the end of this microlearning, you’ll understand how to implement validation for REST endpoints effectively
2 +In the previous microlearning, we learned how to configure a REST service. In this microlearning, we will discuss how you can validate whether the party calling your REST endpoint is sending the correct information in terms of the structure of the message. We will also learn how you can subsequently report back to the client that a validation error occurred.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -10,11 +10,12 @@
10 10  == 2. Key concepts ==
11 11  
12 12  This microlearning centers around validating incoming messages when hosting a REST web service.
13 -* With REST, we mean: A web service that adheres to the RESTful principles.
14 -* With validation, we mean: Verifying whether the data structure we received is valid according to our definition.
13 +With REST, we mean: A web service that adheres to the RESTful principles
14 +With validation, we mean: Verifying whether the data structure we received is valid according to our definition
15 +
15 15  * The external application pushes data to a REST web service (or API) hosted by eMagiz
16 -** When doing so, the external application should adhere to the defined data structure
17 -** If not, we need to refuse the call and respond with an error message
17 +* When doing so, the external application should adhere to the defined data structure
18 +* If not, we need to refuse the call and respond with an error message
18 18  
19 19  == 3. Validation ==
20 20  
... ... @@ -38,10 +38,11 @@
38 38  
39 39  == 4. Key takeaways ==
40 40  
41 -* External applications must follow the defined data structure when sending information to a REST web service (or API) hosted by eMagiz.
42 -* If the incoming data does not meet the required structure, the request should be rejected, and an appropriate error message should be sent back to the client.
43 -* eMagiz automatically handles much of the validation process when using the API Gateway, simplifying error management and reporting.
44 -* For messaging flows, additional configuration is needed to replicate the same validation and error-handling functionality.
42 +* The external application pushes data to a REST web service (or API) hosted by eMagiz
43 +* When doing so, the external application should adhere to the defined data structure
44 +* If not, we need to refuse the call and respond with an error message
45 +* eMagiz auto generates a lot when using the API Gateway
46 +* You need to recreate this when using the same functionality in a messaging flow
45 45  
46 46  == 5. Suggested Additional Readings ==
47 47