- ago
I have an App Key and Secret code when I try to log in and get a token, I get a pop-up window from Schwab and after log in and verification I get a second pop Schwab login window which gives the message " We are unable to complete your request. Please contact customer support for further assistance."

I communicated with Schwab and got the following response;
QUOTE:
Thank you for reaching out to the Schwab Trader API Support Team.

In most cases, when the "We are unable to complete your request. Please contact customer support for further assistance." error message is returned after going through the CAG process, it is due to an improperly formatted Auth URL. The Auth URL used for the Trader API would be:

https://api.schwabapi.com/v1/oauth/authorize?client_id={CONSUMER_KEY}&redirect_uri={APP_CALLBACK_URL}

If you are able to successfully login into your account (using your brokerage account login credentials), but are redirected to the origin LMS screen with an error message at the top (instead of the expected 404 page), either an incorrect Auth URL format is being used, or there is an incorrect 'callback url' and/or 'consumer key' value being used in the Auth URL.

Since the callback url & app key values are specific to your developer application, if they are not entered correctly in the Auth URL, it will result in an error response following the completion of the CAG process.

You would want to ensure that both the 'callback url' & 'consumer key' (aka app key) values used in the Auth URL are copied exactly as they appear on the 'App Details' page for that application. You can find these values by logging into the Developer Portal, and going to "Dashboard" > "Apps" > "View Details". By default both the 'App Key' and 'Secret' values are hidden. To display the values click the 'Show' icon (šŸ‘) to the right of the value.

*Sending the Auth URL in a browser will prompt the LMS, where you would need to enter the login credentials for your brokerage account (not your dev account). This would be the User ID & Password you use to login on Schwab.com (not https://developer.schwab.com/).

Note: All applications that are distributed or made available to retail investors for use with their personal self-directed brokerage account(s) (for free or for a fee) must be registered as a Commercial application for the Trader API. Commercial applications must go through additional review process(s). If 3rd party application has a registered integration developed for the Trader API, they should have a secure method of connecting/authenticating an users Schwab brokerage account with their application. This is done through a token based authentication flow, which allows the app to provide the user with the ability to securely authenticate without the app ever interacting with that individualā€™s username/password directly. (Schwab does not guarantee that any given commercial application will be available.)


If you have any further questions, please let us know.

Best regards,


This does not help me figure out the problem. Any suggestions?
0
332
14 Replies

Reply

Bookmark

Sort
Cone8
 ( 6.64% )
- ago
#1
What is the status of your App on the Schwab dev site?
Probably you have to wait for step 12.

0
- ago
#2
I have created the App and its active for use, have an APP Key and Secret Key. Linked it to my account. But when I go to get a token login to Schwab depending on authentication type either hangs up or after log in a second log in pops up to log in again. I have installed WebView29078-WL-screen-pdf
0
Cone8
 ( 6.64% )
- ago
#3
You said "active". That's not the same as "Ready for use".
It must say, precisely, "Ready for use".

Assuming it's "Ready for use", make sure that your firewall is allowing a connection to https://schwab.wealth-lab.com. This is required for the authentication callback.
0
- ago
#4
Hi, I also use Schwab and when i follow the instructions provided by WL on create an App in Schwab Development portal. I get to a page in which i cant click into the fields for my email address and to create a password, I have tried a bunch. Does Schwab support handle this. ?
0
Cone8
 ( 6.64% )
- ago
#5
If it's on the Schwab website, then someone there must support it.

I'm not having any trouble at their dev site with login or register. If you don't have a dev login (not the same as your schwab account), you need to Register first:
https://developer.schwab.com/register
0
- ago
#6
I checked everything and turned off firewalls and the problem remains the same

The following is what's on the Schwab Dev portal APP detail if it helps anything
QUOTE:
App Details - Geo day
Modify App
Activate App
App Details
App Analytics
Time Frame

Select Time Frame:

Last Hour
App Usage

Total Api Calls:
12

Average Api Calls Per Hour:
12

App Health

Average Response Rate:
32 ms

Total Errors:
6

Error Rate:
50 %

Device Analytics

Unique User IP Address Count:
1

Device Type:
Desktop/Laptop:
6

Tablet:
0

Smartphone:
0

Unknown:
6

Device Geo Location:
United States:
12
0
Cone8
 ( 6.64% )
- ago
#7
Does middle of your app details page match these items?



If your data look the same as the above, the only thing I can suggest it to start over. Delete that app and create a new one, following our instructions to the letter. Incidentally, I don't remember actually entering the 127.0.0.1 local callback. That just appeared on its own, but it's not used by our Schwab provider.
0
- ago
#8
everything looks the same except the Callback URL is "https://schwab.wealth-lab.com"
0
Cone8
 ( 6.64% )
- ago
#9
Its worth a try adding that local callback url. Even though it's not used, its absence could be something that confuses them.

You'll probably have to wait for "Ready for Use" approval again, but if that doesn't work, delete the app and start over.
0
- ago
#10
I started everything from the beginning and have a new app ready to use but the problem remains. All firewalls are off
the call back URL
QUOTE:
https:// 127.0.0.1, https://schwab.wealth-lab.com
 can't be used it gives an error message
QUOTE:
The URL entered is either not a valid URL or contains unsupported characters.

Any other suggestions?
0
Cone8
 ( 6.64% )
- ago
#11
How did you get a "Ready for use" with that error? It sounds like you entered the callback urls in one record - that's invalid.
1. Enter https://127....
2. Then there will be a button to add another.
3. Enter https://schwab.wealth...

If that sounds like what happened, back to the drawing board!
0
- ago
#12
@giorgos, did you figure out the issue, im having the same issue as we speak lol
0
Cone8
 ( 6.64% )
- ago
#13
They've made this hard for us, but it shouldn't be this hard. A lot of us are using the Schwab provider.

In the response from Schwab (first post) they pointed to not only the callback url (which is clear) but also the App Key and Secret Keys that you need to enter. Make sure those are correct too. -


As a long shot, if one of your keys starts or ends with a whitespace let me know because we're trimming those entries. Check your keys by revealing them on your Schwab app page.
0
- ago
#14
After many attempts at starting over it is finally working. I used a different computer and URL
QUOTE:
https://127.0.0.1,https://schwab.wealth-lab.com
1

Reply

Bookmark

Sort