WEBVTT

00:00:01.300 --> 00:00:05.479
Now let's walk through the connection flow from beginning to end. We

00:00:05.479 --> 00:00:09.657
are describing an intentional setup, using a demonstration account. Your own setup

00:00:09.657 --> 00:00:13.836
can wait until you understand the fields. The current TraderLobby form uses

00:00:13.836 --> 00:00:18.014
exchange API credentials. It is not asking you to enter your ordinary

00:00:18.014 --> 00:00:20.800
exchange sign-in password into the API secret field.

00:00:21.300 --> 00:00:25.464
API is a name for a way that software systems communicate. An

00:00:25.464 --> 00:00:29.628
API key identifies a particular access credential. Its matching secret or private

00:00:29.628 --> 00:00:33.791
key helps prove that a request is authorized. These values belong together.

00:00:33.791 --> 00:00:37.955
A key from one setup and a secret from another will not

00:00:37.955 --> 00:00:41.425
become a working pair just because both fields contain text.

00:00:41.925 --> 00:00:45.521
Open the exchange's own account settings through its official site or app

00:00:45.521 --> 00:00:49.117
and follow the instructions for the supported credential type. Keep that work

00:00:49.117 --> 00:00:52.713
private. Return to TraderLobby with the correct provider selected, then enter the

00:00:52.713 --> 00:00:56.309
API key and its matching secret in the named fields. If the

00:00:56.309 --> 00:00:59.904
form offers a passphrase, use it only when the provider's credential flow

00:00:59.904 --> 00:01:03.500
requires one. Do not invent an extra passphrase or substitute a sign-in

00:01:03.500 --> 00:01:03.800
password.

00:01:04.300 --> 00:01:08.063
Robinhood Crypto has a different branch in the desktop form. Generate secure

00:01:08.063 --> 00:01:11.826
key pair creates a public and private pair in the browser. The

00:01:11.826 --> 00:01:15.590
public part is the one the instructions tell you to copy into

00:01:15.590 --> 00:01:19.353
Robinhood's desktop Add key form. Robinhood then supplies its API key. That

00:01:19.353 --> 00:01:23.116
API key returns to the Robinhood API key field in TraderLobby; the

00:01:23.116 --> 00:01:25.625
matching private key is already filled and hidden.

00:01:26.125 --> 00:01:29.873
Public and private do not mean two values you can swap freely.

00:01:29.873 --> 00:01:33.620
The provider needs the public part for this setup, while the private

00:01:33.620 --> 00:01:37.368
part must remain protected. Generating a different pair partway through can break

00:01:37.368 --> 00:01:41.116
the match with the public key you already registered. Follow one complete

00:01:41.116 --> 00:01:44.863
setup deliberately. The mobile form accepts the matching credentials but does not

00:01:44.863 --> 00:01:46.425
offer that desktop key-generation helper.

00:01:46.925 --> 00:01:50.701
Before saving, inspect the account name, provider, currency, and cash limit. The

00:01:50.701 --> 00:01:54.477
desktop field says Maximum cash TraderLobby may use, with U.S. dollars as

00:01:54.477 --> 00:01:58.254
its unit. It begins at zero. This is a control for the

00:01:58.254 --> 00:02:02.030
app's trading budget, not a transfer of funds. Leave it unchanged for

00:02:02.030 --> 00:02:05.806
the lesson. We will explain its relationship to the reported balance on

00:02:05.806 --> 00:02:06.750
a later page.

00:02:07.250 --> 00:02:10.991
When you intentionally submit a real setup, Validate and save sends the

00:02:10.991 --> 00:02:14.732
connection for validation. Read the result and check that the intended connection

00:02:14.732 --> 00:02:18.473
appears in the list. A message may say that it was validated

00:02:18.473 --> 00:02:22.214
and saved, and it may also say it became the default Live

00:02:22.214 --> 00:02:25.955
connection. That last part matters: inspect the default label rather than assuming

00:02:25.955 --> 00:02:27.825
saving only added an unused item.

00:02:28.325 --> 00:02:32.487
If validation fails or times out, read the message before trying again.

00:02:32.487 --> 00:02:36.649
If the result is unclear, inspect the connection list before creating another

00:02:36.649 --> 00:02:40.810
entry. Do not keep submitting credentials just because the button is still

00:02:40.810 --> 00:02:44.972
visible. A visible card, its status, and the returned message together give

00:02:44.972 --> 00:02:47.400
you a better picture of the outcome.

00:02:47.900 --> 00:02:52.513
For your check, describe the path from choosing a provider to confirming

00:02:52.513 --> 00:02:57.125
a saved connection. Include the special public-and-private-key steps for Robinhood if that

00:02:57.125 --> 00:03:01.738
is your provider. Keep every real credential hidden. The skill we are

00:03:01.738 --> 00:03:06.350
practicing is recognizing a complete setup, not collecting screenshots of sensitive fields.