PERPETUAL FUTURES24/7 crypto, index and commodity perps
Featured Firm VestVest 5% OFF all plans · from $10 · NQ 50x · no swap fee · USDC payouts on-chain 5% Off Code JMU

RULE CHANGE

Rule Radar

Command-Line Interface

My Funded Perpetuals changed this help center article on October 13, 2026. Updated Neutral

Authentication method changed from API key creation to browser-based session approval, with manual API key option available for headless machines.


What this means

The primary authentication flow shifted from creating an API key in API Key Settings to using fperp login which opens a browser for session approval; sessions expire automatically and can be renewed by running fperp login again; for remote/headless machines, fperp login --manual provides a sign-in link to approve elsewhere; long-lived API keys remain available via fperp login --with-api-key; credentials storage location and fallback behavior (OS credential store to 0600 config file) stayed the same.

▸ View exact changes
What the page said before and after
Before Oct 11, 2026
is never installed.
Authenticate
− Create an API key in
− API Key Settings,
− then run:
bash theme={null}
fperp login
− The key is stored in your operating system's credential store (macOS
Keychain, Windows Credential Manager, or the Linux Secret Service). Where no
− credential store is available, it falls back to a 0600 config file; see
fperp login --help for the --store options. FPERP_API_KEY and
− --api-key override the stored key for one-off use.
Stay up to date
bash theme={null}
CI environment variable is set.
Uninstall
− Run fperp logout first so no API key stays behind in your OS credential
store, then remove the binary (which fperp shows where it is) and delete the
~/.config/fperp directory.
After Oct 13, 2026
is never installed.
Authenticate
bash theme={null}
fperp login
+ fperp login opens your browser to approve a new CLI session. After you
+ approve it, the CLI prints the session's expiry date and stores the
+ credential. The session expires on its own; run fperp login again to renew
+ it. Run fperp login status to see the current session.
+ On a remote or headless machine (for example over SSH), run
+ fperp login --manual. The CLI prints a sign-in link instead of waiting for
+ a browser on the same machine; open it anywhere, approve, and paste the code
+ the approval page shows.
+ To use a long-lived API key instead, create one in
+ API Key Settings
+ and run fperp login --with-api-key, which reads the key from stdin or a
+ prompt that does not echo it. fperp login --api-key also works, but
+ leaves the key in your shell history.
+ Credentials are stored in your operating system's credential store (macOS
Keychain, Windows Credential Manager, or the Linux Secret Service). Where no
+ credential store is available, they fall back to a 0600 config file; see
fperp login --help for the --store options. FPERP_API_KEY and
+ --api-key on any other command override the stored credential for one-off
+ use.
+ fperp logout revokes a browser-approved session and removes the stored
+ credential.
Stay up to date
bash theme={null}
CI environment variable is set.
Uninstall
+ Run fperp logout first so no credential stays behind in your OS credential
store, then remove the binary (which fperp shows where it is) and delete the
~/.config/fperp directory.

Every My Funded Perpetuals changeRule Radar: all firms

Scroll to Top