Overview
Ban management allows administrators to prevent specific content from appearing on the platform by filtering text, patterns, images, and blocking user addresses.
All ban management endpoints require admin authentication. Changes take effect immediately and apply platform-wide.
Ban Terms
Manage banned text terms that will be filtered from token names and descriptions.
Get Ban Terms
curl -X GET "https://frontend-api-v3.pump.fun/moderation/ban-terms" \
-H "Authorization: Bearer <your_token>"
Add Ban Term
curl -X POST "https://frontend-api-v3.pump.fun/moderation/ban-terms" \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{"term": "inappropriate_word"}'
Remove Ban Term
curl -X DELETE "https://frontend-api-v3.pump.fun/moderation/ban-terms/{id}" \
-H "Authorization: Bearer <your_token>"
The ID of the ban term to remove
Regex Ban Patterns
Use regular expressions for more sophisticated content filtering.
Get Regex Patterns
curl -X GET "https://frontend-api-v3.pump.fun/moderation/ban-regex-patterns" \
-H "Authorization: Bearer <your_token>"
Add Regex Pattern
curl -X POST "https://frontend-api-v3.pump.fun/moderation/ban-regex-patterns" \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{"pattern": "[0-9]{10,}"}'
Test regex patterns thoroughly before adding them to avoid unintended filtering. Invalid patterns may cause errors.
Remove Regex Pattern
curl -X DELETE "https://frontend-api-v3.pump.fun/moderation/ban-regex-patterns/{id}" \
-H "Authorization: Bearer <your_token>"
The ID of the regex pattern to remove
Image Ban Terms
Manage banned terms for image content filtering.
Get Image Ban Terms
curl -X GET "https://frontend-api-v3.pump.fun/moderation/ban-image-terms" \
-H "Authorization: Bearer <your_token>"
Add Image Ban Term
curl -X POST "https://frontend-api-v3.pump.fun/moderation/ban-image-terms" \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{"term": "inappropriate_image_label"}'
Remove Image Ban Term
curl -X DELETE "https://frontend-api-v3.pump.fun/moderation/ban-image-terms/{id}" \
-H "Authorization: Bearer <your_token>"
The ID of the image ban term to remove
User Bans
Manage banned user addresses.
Get Banned Users
curl -X GET "https://frontend-api-v3.pump.fun/moderation/ban-users?limit=50&offset=0&sortBy=createdAt&order=desc&searchQuery=&active=true&unbanRequest=false&fromDate=&toDate=" \
-H "Authorization: Bearer <your_token>"
Number of results to return
Number of results to skip for pagination
Field to sort by (e.g., createdAt, address)
Search term to filter users
Filter by active ban status (true/false)
Filter users with unban requests (true/false)
Filter bans from this date (ISO 8601 format)
Filter bans until this date (ISO 8601 format)
Ban User Address
curl -X POST "https://frontend-api-v3.pump.fun/moderation/ban/address/{address}" \
-H "Authorization: Bearer <your_token>"
The wallet address to ban from the platform
Ban Content by ID
curl -X POST "https://frontend-api-v3.pump.fun/moderation/ban/{id}" \
-H "Authorization: Bearer <your_token>"
The ID of the content to ban
Get Ban Details
curl -X GET "https://frontend-api-v3.pump.fun/moderation/ban?id={id}" \
-H "Authorization: Bearer <your_token>"
The ID of the ban to retrieve
Best Practices
- Start with specific terms: Add exact matches before using regex patterns
- Test patterns: Verify regex patterns don’t create false positives
- Document bans: Keep records of why terms or addresses were banned
- Review regularly: Periodically audit ban lists to ensure they’re still relevant
- Use bulk operations: For banning multiple addresses, consider using bulk endpoints
- Monitor effectiveness: Check moderation logs to see if bans are working as intended