@@ -216,6 +216,32 @@ can also `join our Discord server <https://discord.gg/M3vjtHj>`__ to ask
216
216
questions.
217
217
218
218
219
+ ++++++++++++++++++++++++++++++++++++
220
+ Suspicious errors during signin flow
221
+ ++++++++++++++++++++++++++++++++++++
222
+
223
+ All API endpoints require an approved app. When you app is first created and
224
+ anytime it's modified, it will go into state ``Approved - Pending ``, a
225
+ confusingly-named status indicating that the application is being manually
226
+ approved by Schwab. Until that status changes to ``Ready for Use ``, you cannot
227
+ proceed using ``schwab-py ``, and you will encounter difficult-to-debug errors. A
228
+ listing of the types of errors people have reported:
229
+
230
+ * ``401 Unauthorized `` errors in the signin flow
231
+ * ``4001 ``, ``Session rejected ``, or ``assertion_rejected `` payloads
232
+ * ``Access Denied `` and ``You don't have permission to access
233
+ "http://api.schwabapi.com/v1/oauth/authorize?" on this server" ``
234
+
235
+ .. image :: _static/access-denied.png
236
+ :width: 500
237
+ :align: center
238
+
239
+ Approval appears to be a manual process, and most users have reported
240
+ transitioning to the ``Ready for Use `` status within a few days. Please note
241
+ this behavior is implemented on Schwab's side, so the library authors have no
242
+ ability to influence this or speed up your approval time.
243
+
244
+
219
245
.. _ssl_errors :
220
246
221
247
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
0 commit comments