This page documents how Filly Discord Token Filler integrates with the Discord API, including endpoints, headers, authentication, and response handling.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Nuu-maan/Filly-Discord-Token-Filler/llms.txt
Use this file to discover all available pages before exploring further.
API Endpoints
Filly uses the Discord v9 API for all operations.Join Server Endpoint
Joins a Discord server using an invite code.Location: index.py:187URL Format:Request Body:Headers Required:
authorization- Discord token- All standard headers from
_setup_session()
Join Server with Captcha Solution
Joins a Discord server with captcha solution headers.Location: index.py:206-209URL Format:Request Body:Additional Headers:
authorization- Discord tokenx-captcha-key- Captcha solution from solverx-captcha-rqtoken- Token from captcha challenge response
HTTP Session Setup
TheDiscordJoiner class uses curl_cffi to impersonate Chrome and bypass bot detection.
Session Creation
Location: index.py:76-80- Creates two sessions:
self.sessionandself.client - Both impersonate Chrome browser
- Retry mechanism if session creation fails
Proxy Configuration
Location: index.py:83-88- Loads proxies from
input/proxies.txt - Randomizes session ID in proxy URL
- Applies to both HTTP and HTTPS
HTTP Headers
All headers are configured in the_setup_session() method (index.py:90-108).
Complete Headers List
Accept header for all content types.Value:
Language preferences for responses.Value:
Content type for request bodies.Value:
Origin header indicating request source.Value:
Request priority hints.Value:
Referrer URL indicating navigation source.Value:
Chrome user agent client hints.Location: index.py:28, 97Value:Generated From:
Indicates not a mobile browser.Value:
Operating system platform.Value:
Fetch destination type.Value:
Fetch mode for CORS requests.Value:
Indicates same-origin request.Value:
User-Agent string identifying the browser.Location: index.py:29, 103Value:Generated From:
Discord debug options.Value:
Discord locale preference.Value:
Discord timezone setting.Value:
Base64-encoded browser fingerprint data.Location: index.py:107Encoded Value:Decoded JSON:
Dynamic Headers
Discord token for authentication.Location: index.py:186, 201Set Before Each Request:Format:
- Token only (not with email:password prefix)
- Extracted from token using
.split(":")[-1]
Captcha solution from solving service.Location: index.py:202Set When Captcha Detected:
Captcha request token from Discord challenge.Location: index.py:203Set When Captcha Detected:
Authentication
Token Format
Location: index.py:183-184- Tokens may be in
email:password:tokenortokenformat - Only the token part (after last
:) is used - Tokens are masked in logs for security
Token Authorization
Location: index.py:186- Set in the
authorizationheader - Updated before each join request
- Not prefixed with “Bot” or “Bearer”
Response Handling
Response handling is implemented in_handle_response() method (index.py:138-179).
HTTP Status Codes
Successfully joined the server.Location: index.py:145-149Actions:
- Log success message
- Append token to
output/joined.txt - Increment
stats.joinedcounter
Invalid or unauthorized token.Location: index.py:151-156Actions:
- Log failure message
- Append token to
output/invalid.txt - Remove token from tokens list
- Increment
stats.invalidcounter
Token is locked or banned.Location: index.py:158-163Actions:
- Log locked message
- Append token to
output/locked.txt - Remove token from tokens list
- Increment
stats.lockedcounter
Rate limited by Discord.Location: index.py:141-143Actions:
- Log rate limit message
- No file output
- Token remains in rotation
Response Body Checks
Indicates captcha challenge is required.Location: index.py:189Check:Actions:
- Log captcha detection
- Append token to
output/captcha.txt - Increment
stats.captchacounter - Initiate captcha solving flow
Captcha challenge data for solving.Location: index.py:195Usage:
Captcha request token for validation.Location: index.py:196, 203Usage:
Indicates captcha solution was invalid.Location: index.py:171-175Actions:
- Log solver failure
- Append token to
output/failed_captcha.txt - Increment
stats.failedcounter
Indicates token-related issue.Location: index.py:165-169Actions:
- Log token issue
- Append token to
output/failed_token.txt - Increment
stats.failedcounter
Captcha Integration
Captcha solving is handled by theSolver class from data/solver.py.
Captcha Detection Flow
Location: index.py:189-210- Check if response contains
"captcha_sitekey" - Extract
captcha_rqdataandcaptcha_rqtokenfrom response - Call appropriate solver based on config
- Update headers with solution
- Retry join request with captcha headers
Supported Captcha Solvers
RazorCap API integration.Location: solver.py:55-89Endpoint:
https://api.razorcap.xyz/Timeout: 120 secondsHCOptcha API integration.Location: solver.py:127-164Endpoint:
https://api.hcoptcha.com/api/CSolver API integration.Location: solver.py:33-53Endpoint:
https://api.csolver.xyz/solveHardcoded API Key: 71144850f4fb4cc55fc0ee6935badddfCapMonster Cloud integration.Location: solver.py:203-239Endpoint:
https://api.capmonster.cloud/Error Handling
Session Creation Retry
Location: index.py:76-80- Infinite retry on session creation failure
- Uses recursion to retry
Join Request Error Handling
Location: index.py:213-217- Catches all exceptions during join
- Logs error with thread number
- Always closes sessions in finally block
Session Cleanup
Location: index.py:216-221- Sessions always closed after each join attempt
- Delay applied after cleanup if configured
- New joiner instance created for each token