Kuaishou · Authentication Profile
Kuaishou Authentication
Authentication
Kuaishou declares 0 security scheme(s) across its OpenAPI definitions.
CompanyConsumerSocialVideoShort VideoLive StreamingAdvertisingMarketingSocial MediaContentChina
Methods:
Schemes: 0
OAuth flows:
API key in:
Security Schemes
Source
Authentication Profile
generated: '2026-07-19'
method: searched
source: https://open.kuaishou.com/oauth2/authorize (HTTP 200), https://open.kuaishou.com/oauth2/access_token (HTTP 200, JSON)
notes: >-
Verified by live HTTP probe on 2026-07-19. The Kuaishou Open Platform developer documentation is served
as a JavaScript single-page application and its written scope/permission reference is gated behind
developer registration, so only the endpoints and behaviours observed directly on the wire are recorded
here. No scope list is asserted because none could be verified without an approved developer account.
apis:
- api: kuaishou:open-platform
base_url: https://open.kuaishou.com/openapi
schemes:
- id: kuaishou_oauth2
type: oauth2
flow: authorization_code
authorization_url: https://open.kuaishou.com/oauth2/authorize
token_url: https://open.kuaishou.com/oauth2/access_token
evidence:
authorization_endpoint_status: 200
authorization_endpoint_content_type: text/html
authorization_endpoint_behaviour: >-
Returns the Kuaishou Open Platform authorization / login interface, consistent with an OAuth 2.0
authorization-code front channel.
token_endpoint_status: 200
token_endpoint_content_type: application/json;charset=UTF-8
token_endpoint_unparameterised_response: >-
{"result":100200100,"error":"invalid_request","error_msg":"请求参数错误,请检查参数是否合法"}
token_endpoint_note: >-
The token endpoint answers an unparameterised request with the OAuth 2.0 `invalid_request` error
identifier wrapped in Kuaishou's own result/error_msg envelope.
scopes_documented: unverified
scopes_source: null
- api: kuaishou:kwai-for-business
base_url: https://developers.kwai.com/rest/n/mapi
schemes:
- id: kwai_business_unverified
type: unverified
evidence:
probe_status: 404
probe_content_type: application/json;charset=UTF-8
probe_response: >-
{"timestamp":"...","status":404,"error":"Not Found","message":"No message available",
"path":"/rest/n/mapi/..."}
note: >-
The host routes /rest/n/mapi/* through a JSON application server, but no authorization or token
endpoint could be confirmed without an approved Kwai for Business advertiser account. No scheme
is asserted.
gaps:
- No /.well-known/openid-configuration or /.well-known/oauth-authorization-server document is published
on any Kuaishou or Kwai host (all requests are absorbed by the SPA catch-all; see
well-known/kuaishou-well-known.yml).
- No public OAuth scope / permission reference could be retrieved; scopes/ is intentionally not produced
rather than fabricated.