Portal Finder can be useful for calling OQUPIE customer portals through web views, usually in a mobile app.
In addition, through optional parameter setting, customer information can be collected at the same time when receiving customer inquiries.
Use Portal Finder to connect your desired customer portal to one endpoint.
step 1. Generate Portal finders
Portal finder setting
Checking the access key and secret key
Step 2. Build Portal finders
Step 3. Use JWT method (optional)
You can build a portal finder in> > .
The settings to be set are as follows.
Add Brand Connection
Click thein the Brand Connection Settings to set the brands to connect to the Portal Finder in the modal pop-up windows.
💡 : The combination of brand identification values must be unique within one portal finder, and the order of input can affect to connecting a portal.
💡 : Only lowercase letters and numbers are allowed.
Connected brands are displayed as follows:
💡 : If the default brand's customer portal is disabled, the page will not be invoked normally.
After completing the basic settings and brand connection settings, click thebutton to finish creating a portal finder.
Click thecreated on the Portal Finder List page and check the issued authentication key.
Portals are generally accessed via an HTTP GET method to a known URL made from web browsers like Chrome, Firefox.
You can check Basic Settings in Portal finder. All endpoint URLs in an account are the same.
Send the following parameters (query string) along with the endpoint URL.
Parameters for Portal finder authentication
Parameters defined in OQUPIE
💡 : It is recommended to use these parameter for games developed with Unreal Engine.
Special parameters other than those defined above can be added according to user definition, and can be also checked at. In the case of this parameter, the key name format is exposed. In the picture above, , corresponds to Special Parameters.
This is an example Portal Finder created by following the steps above.
There is potenial risk that the secret key can be easily exposed when the GET method uses query strings in the URL. If the access key and secret key are exposed, anyone can access your portal finder.
💡 : JWT and query string types cannot be used at the same time.