ringcentral / ringcentral/engage-voice-api-docs
auth-ringcentral.md issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 12
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 3
Description
https://engage-voice-api-docs.readthedocs.io/en/latest/authentication/auth-ringcentral/
form-urlencoded vs query parameter
The docs says
POST https://engage.ringcentral.com/api/auth/login/rc/accesstoken
Content-Type: application/x-www-form-urlencoded
rcAccessToken=<rcAccessToken>&rcTokenType=Bearer
But as I tested, specifying rcAccessToken=<rcAccessToken>&rcTokenType=Bearer as query parameter works too.
Is it by design or legacy issue?
It works for some extensions but not all
For my account(direct number 1650641xxxx), it works
For 1720386xxxx*11115 it does not work. The error message is:
{"message":"Invalid argument supplied [Please specify a valid platform!]","detail":"Please specify a valid platform!","status":409,"statusDetail":"CONFLICT"}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with auth-ringcentral.md and compare the documented form-urlencoded request with the reported query-parameter behavior. Investigate the direct-number and extension cases, then clarify the supported request format and the cause or resolution for the “valid platform” error in the documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100