You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sample-server/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
## Endpoints
4
4
5
-
- GET `/start`: Call Incode's `/omni/start` API to create an Incode session which will include a token in the JSON response. This token can be shared with Incode SDK client apps to do token based initialization, which is a best practice.
5
+
- GET `/start`: Call Incode's `/omni/start` API to create an Incode session which will include a `token` in the JSON response. This token can be shared with Incode SDK client apps to do token based initialization, which is a best practice.
6
6
7
7
It also performs basic storage of sessions in the `sessions` directory to help implement `renderRedirectToMobile`in frontend.
8
8
9
-
At session generation it will generate an `uuid` and save the session in `session/<UUID>.json`, later if you call `/start` again passing a valid `uuid` it will retrieve the stored session instead of creating a new one.
9
+
At session generation it will generate an `uniqueId` and save the session in `session/<uniqueId>.json`, later if you call `/start` again passing a valid `uniqueId` it will retrieve the stored session instead of creating a new one.
10
10
11
11
- GET `/onboarding-url`: Calls incodes `/omni/start` and then with the token calls `/0/omni/onboarding-url` to retrieve the unique onboarding-url for the newly created session.
12
12
@@ -94,7 +94,7 @@ Open the `Forwarding` adress in a web browser. The URL should look similar to th
94
94
95
95
Now you should be able to visit the following routes to receive the associated payloads:
0 commit comments