Trial Access
Trial access can be used for development and testing to integrate with the EDGE Connect platform. Trial access functions exactly the same way as production access. The only limitation of trial access is that it has a quota on the number of product requests. The default quota is 100.
Follow the steps below to implement integration using trial access:
-
The API Key is required in the header for all API access.Obtain an API Key from the EDGE Connect team -
Follow the instructions described in the “Authorization” section of this document to call theUse your favorite API client to verify your API Keyhttps://ninjafetch.com/auth/tokens
endpoint. You should store the API Key in an environment variable. -
Follow the API guides to create the frontend and backend integration with the EDGE Connect platform. Address of the Widget isUpdate your web application to include the Widgethttps://ninjafetch.com/v1/ninjafetch.js
You should store the path in an environment variable. -
The table below describes how to test your integration using the Sandbox environment.Test your integration -
Trial access plan is available for Clients who want to test the production platform with real business data. The number of requests are limited under a trial license. Contact the EDGE Connect team to obtain a production API Key once you are ready to go live with the EDGE Connect platform.Upgrade to production
Testcase | How to trigger | Expected Result |
---|---|---|
Obtain widget access token successfully | Call https://ninjafetch.com/api/v1/auth/tokens with all required information | A widget access token issued |
Invalid API Key | Call https://ninjafetch.com/api/v1/auth/tokens with an invalid API Key | Access was not authorized |
Null payload | Call https://ninjafetch.com/api/v1/auth/tokens without body | Validation error - Missing consumer_id |
Empty payload | Call https://ninjafetch.com/api/v1/auth/tokenswith empty payload {} | Validation error - Missing consumer_id |
Launch Widget | Use the widget access token obtained and correct data to launch the widget from your web application | Widget launched successfully |
Invalid widget access token | Use a random access token to launch the widget | Widget did not launch. onError called. |
Expired access token | Use an old access token generated more than 60 minutes ago to launch the widget | Widget did not launch. Auth token expired error passed to onError |
Missing required fields | Omit some of the required data fields and launch the widget with a valid token | Widget did not launch. Error with list of missing fields thrown |
Report generated successfully | Launch the widget. Click on “Connect My Account”. Search for “Dag Site” and select it as the bank. Use “ninja1.site16441.1/site16441.1” to complete the process | Widget closed. Received product_request_id in onSuccess callback. |
Retrieve report | Call https://ninjafetch.com/api/v1/ibv/requests/{request_id} with the returned product_request id | Report received |
Error retrieving report | Call https://ninjafetch.com/api/v1/ibv/requests/{request_id} with proper Mock-Repsonse-Type and Mock-Processing-Request values in the header. Refer to the Product API Specification about possible values | Error received |
Updated about 1 month ago