Docs: Incorrect parameter naming in API docs #5753
Unanswered
Muhammad-Owais-Warsi
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
That's expected. Our API uses snake_case in its output, so the docs are correct to show The thing is, our JS SDK automatically converts to camelCase, hence |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for the clarification. But while using the SDK, it was a bit confusing for me, as nothing seemed to be mentioned. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
- 6B89
Uh oh!
There was an error while loading. Please reload this page.
-
While testing the APIs, I found that there are several naming errors in the documentation. This leads to errors or unexpected results.
For example, in the Create Checkout Session documentation, it mentions that the body can include
success_url: string | null. However, usingsuccess_urlresults in an error. The correct key to use issuccessUrl, which is not mentioned anywhere in the documentation.Beta Was this translation helpful? Give feedback.
All reactions