Customisation of Mock Entity and Responses
Last updated
Last updated
This page explains how to use APIs to create custom mock entities for integration purposes. Additionally, responses for any scenario can be simulated by adding a custom expected response to a specific mock entity. The behavior of the created mock entities will default to the Response Simulator.
The Response Simulator is built to handle custom entities and responses for any request, while also mimicking the behavior of real Entity Protocol APIs. It offers a controlled environment for developers to test and validate custom scenarios without depending on the default behavior of the Response Simulator.
All the APIs listed below require a user token for authorization. Onboarded users can generate a token using their credentials, which can then be used to create mock entities, configure custom responses, and more.
We recommend to use below postman collection for quicker access
Register a new custom mock entity using user token.
"1.0"
"2024-08-28T01:58:50.505Z"
"1fbb-11ed-861d-0242"
"FIP"
Successful onboarding of the entity
"1.0.0"
"2024-09-25T10:01:19.942498808Z"
"1fbb-11ed-861d-0242"
"Entity successfully onboarded."
Add a custom response simulation for a given entity, endpoint, response code, and scenario.
"FIP-SIMULATOR"
"/Consent/Notification"
400
"FIP-SIMULATOR-400-Error"
Successfully added the response simulation.
"1.0.0"
"2024-09-25T06:52:19.750Z"
"FIP-SIMULATOR"
"FIP-SIMULATOR added successfully."
To list all the custom responses configured for the given entity
"FIP-SIMULATOR"
Successfully retrieved response list
"1.0.0"
"2024-09-25T07:05:54.036Z"