PikPak

Connect a PikPak account with automatic login and token refresh, file reads/writes, and directory management.

Adapter type: pikpak. See Common configuration for mounting instructions.

Setup

Set a usable account password and verify login in the official client.
Start with username, password, and the default platform: android. Normal setup does not require manual tokens, CAPTCHA tokens, or a device ID.
Leave root_id empty for the drive root, or obtain a subfolder ID from an official web directory request.
Resolve login verification in the official client first. Supply matching platform/device tokens only when needed for troubleshooting.

Configuration

Field	Type	Required	Default	Description
`username`	string	Yes	—	Remote account username.
`password`	password	Yes	—	Remote account password.
`platform`	select	No	`"android"`	Client platform: android, web, or pc.
`refresh_token`	password	No	—	PikPak login refresh token, normally maintained automatically; manual values must match the account and platform.
`access_token`	password	No	—	Optional access token, normally maintained automatically; it does not replace the required username and password.
`expires_at`	number	No	—	Access token expiry as Unix seconds; normally maintained automatically.
`captcha_token`	password	No	—	Verification token matching the account/device; normally maintained automatically.
`device_id`	string	No	—	Device ID; generated if blank. Avoid changing it unnecessarily.
`root_id`	string	No	`""`	Root folder ID; an empty string means the drive root.
`disable_media_link`	boolean	No	`true`	Disable media transcoding links to prefer originals.
`enable_direct_download_307`	boolean	No	`false`	Allow HTTP 307 redirects to an upstream download URL; the client must be able to reach it.

Example

This is a config object. In the admin form, fill the corresponding fields rather than pasting the whole object. Replace credential placeholders with your own values.

json

{
  "username": "YOUR_ACCOUNT",
  "password": "YOUR_PASSWORD",
  "platform": "android",
  "root_id": "",
  "disable_media_link": true,
  "enable_direct_download_307": false
}

Behavior and limitations

Username and password remain required even when tokens are supplied.
Platforms are android, web, and pc; do not mix temporary credentials from different platforms or devices.
Login tokens, expiry, and device details are saved back to configuration; avoid overwriting them manually.
Media transcoding links are disabled by default to prefer originals. Redirect downloads require client access to the upstream URL.

Troubleshooting

CAPTCHA / verification: complete official verification and check platform/device consistency.
Invalid token: check account ownership of supplied tokens; clear manually entered tokens and log in again if needed.
Unexpected video quality: keep disable_media_link: true and check that an original download URL exists.

References

External documentation provides service and authorization context. Use this page and the current Foxel adapter for configuration fields and limitations.