Permissions & Access Control

Overview

The Permissions API provides endpoints to verify user roles and access levels within the Pump.fun platform. These endpoints help enforce role-based access control (RBAC) for administrative and privileged operations.

Admin Check

Check if the authenticated user has administrator privileges.

Authentication

Requires JWT authentication via Authorization: Bearer <token> header.

Headers

string

required

Bearer token for authentication

Authorization: Bearer <your_jwt_token>

string

required

Response content type

Accept: application/json

string

required

Request origin

Origin: https://pump.fun

Response

object

Admin status check result

Response Schema

boolean

true if the user has admin privileges, false otherwise

Example Usage

curl -X GET "https://frontend-api-v3.pump.fun/auth/is-admin" \
  -H "Authorization: Bearer <your_token>" \
  -H "Accept: application/json" \
  -H "Origin: https://pump.fun"

import requests

url = "https://frontend-api-v3.pump.fun/auth/is-admin"
headers = {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
}

response = requests.get(url, headers=headers)
result = response.json()
print(f"Is admin: {result.get('isAdmin')}")

const url = "https://frontend-api-v3.pump.fun/auth/is-admin";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
  }
});

const data = await response.json();
console.log(`Is admin: ${data.isAdmin}`);

interface AdminCheckResponse {
  isAdmin: boolean;
}

const url = "https://frontend-api-v3.pump.fun/auth/is-admin";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
  }
});

const result: AdminCheckResponse = await response.json();
console.log(`Is admin: ${result.isAdmin}`);

Super Admin Check

Check if the authenticated user has super administrator privileges. Super admins have elevated permissions beyond regular administrators.

Authentication

Requires JWT authentication via Authorization: Bearer <token> header.

Headers

string

required

Bearer token for authentication

Authorization: Bearer <your_jwt_token>

string

required

Response content type

Accept: application/json

string

required

Request origin

Origin: https://pump.fun

Response

object

Super admin status check result

Response Schema

boolean

true if the user has super admin privileges, false otherwise

Example Usage

curl -X GET "https://frontend-api-v3.pump.fun/auth/is-super-admin" \
  -H "Authorization: Bearer <your_token>" \
  -H "Accept: application/json" \
  -H "Origin: https://pump.fun"

import requests

url = "https://frontend-api-v3.pump.fun/auth/is-super-admin"
headers = {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
}

response = requests.get(url, headers=headers)
result = response.json()
print(f"Is super admin: {result.get('isSuperAdmin')}")

const url = "https://frontend-api-v3.pump.fun/auth/is-super-admin";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
  }
});

const data = await response.json();
console.log(`Is super admin: ${data.isSuperAdmin}`);

Super admin privileges should be restricted to a minimal number of trusted users. These accounts have full system access.

Jurisdiction Check

Verify if the authenticated user’s jurisdiction (geographic location) is valid for accessing the Pump.fun platform. This endpoint enforces geographic restrictions and compliance requirements.

Authentication

Requires JWT authentication via Authorization: Bearer <token> header.

Headers

string

required

Bearer token for authentication

Authorization: Bearer <your_jwt_token>

string

required

Response content type

Accept: application/json

string

required

Request origin

Origin: https://pump.fun

Response

object

Jurisdiction validity check result

Response Schema

boolean

true if the user’s jurisdiction is allowed, false if blocked or restricted

string

The detected jurisdiction/country code

string

Explanation if jurisdiction is invalid (only present when isValidJurisdiction is false)

Example Usage

curl -X GET "https://frontend-api-v3.pump.fun/auth/is-valid-jurisdiction" \
  -H "Authorization: Bearer <your_token>" \
  -H "Accept: application/json" \
  -H "Origin: https://pump.fun"

import requests

url = "https://frontend-api-v3.pump.fun/auth/is-valid-jurisdiction"
headers = {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
}

response = requests.get(url, headers=headers)
result = response.json()

if result.get('isValidJurisdiction'):
    print(f"Access allowed from {result.get('jurisdiction')}")
else:
    print(f"Access denied: {result.get('reason')}")

const url = "https://frontend-api-v3.pump.fun/auth/is-valid-jurisdiction";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
  }
});

const data = await response.json();

if (data.isValidJurisdiction) {
  console.log(`Access allowed from ${data.jurisdiction}`);
} else {
  console.log(`Access denied: ${data.reason}`);
}

interface JurisdictionCheckResponse {
  isValidJurisdiction: boolean;
  jurisdiction: string;
  reason?: string;
}

const url = "https://frontend-api-v3.pump.fun/auth/is-valid-jurisdiction";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": "Bearer <your_token>",
    "Accept": "application/json",
    "Origin": "https://pump.fun"
  }
});

const result: JurisdictionCheckResponse = await response.json();

if (result.isValidJurisdiction) {
  console.log(`Access allowed from ${result.jurisdiction}`);
} else {
  console.log(`Access denied: ${result.reason}`);
}

Use Cases

Enforce geographic access restrictions
Comply with regional regulations
Display location-specific content or features
Block access from sanctioned countries
Implement KYC/compliance workflows

Permission Hierarchy

The Pump.fun platform uses a hierarchical permission system:

Regular User: Basic platform access
Admin: Elevated privileges for moderation and management
Super Admin: Full system access and configuration capabilities

Always check permissions before performing privileged operations. Unauthorized access attempts may result in account suspension.

Best Practices

Client-Side Checks

Use permission checks to show/hide UI elements
Check permissions on page load and route changes
Cache permission results for better performance
Revalidate permissions periodically

Server-Side Enforcement

Never rely solely on client-side permission checks
Always validate permissions on the backend
Log all permission check failures for security monitoring
Implement rate limiting on permission endpoints

Security Considerations

Permissions may change during a user session
Re-check permissions before critical operations
Handle permission denials gracefully
Provide clear error messages when access is denied

GET /auth/my-profile - Get current user profile with role information
POST /auth/login - Authenticate and obtain JWT token
POST /auth/logout - End user session

Coins

Trades

Users & Authentication

Social Features

Livestreams

Moderation

Advanced Analytics

Utilities

Permissions & Access Control

Overview

Admin Check

Authentication

Headers

Response

Response Schema

Example Usage

Super Admin Check

Authentication

Headers

Response

Response Schema

Example Usage

Jurisdiction Check

Authentication

Headers

Response

Response Schema

Example Usage

Use Cases

Permission Hierarchy

Best Practices

Client-Side Checks

Server-Side Enforcement

Security Considerations

​Overview

​Admin Check

​Authentication

​Headers

​Response

​Response Schema

​Example Usage

​Super Admin Check

​Authentication

​Headers

​Response

​Response Schema

​Example Usage

​Jurisdiction Check

​Authentication

​Headers

​Response

​Response Schema

​Example Usage

​Use Cases

​Permission Hierarchy

​Best Practices

​Client-Side Checks

​Server-Side Enforcement

​Security Considerations

​Related Endpoints

Overview

Admin Check

Authentication

Headers

Response

Response Schema

Example Usage

Super Admin Check

Authentication

Headers

Response

Response Schema

Example Usage

Jurisdiction Check

Authentication

Headers

Response

Response Schema

Example Usage

Use Cases

Permission Hierarchy

Best Practices

Client-Side Checks

Server-Side Enforcement

Security Considerations

Related Endpoints