Login & Logout

​

Login

​

Authentication

​

Headers

Authorization: Bearer <your_jwt_token>

Content-Type: application/json

Accept: application/json

Origin: https://pump.fun

​

Request Body

​

Response

​

Response Schema

​

Example Usage

curl -X POST "https://frontend-api-v3.pump.fun/auth/login" \
  -H "Authorization: Bearer <your_token>" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -H "Origin: https://pump.fun" \
  -d '{
    "wallet": "<wallet_address>",
    "signature": "<signature>",
    "message": "<signed_message>"
  }'

​

Error Responses

{
  "statusCode": 400,
  "message": "Invalid signature or wallet address"
}

{
  "statusCode": 401,
  "message": "Invalid credentials"
}

​

Logout

​

Authentication

​

Headers

Authorization: Bearer <your_jwt_token>

Accept: application/json

Origin: https://pump.fun

​

Response

​

Example Usage

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

​

Best Practices

• Always call the logout endpoint when the user explicitly logs out
• Clear the JWT token from local storage after logout
• Handle logout on token expiration
• Implement automatic logout after a period of inactivity

​

Authentication Flow

1. Request Message: Request a message to sign from the platform
2. Sign Message: User signs the message with their wallet
3. Login: Submit wallet address, signature, and message to /auth/login
4. Receive Token: Store the JWT token securely
5. Use Token: Include token in Authorization header for all API requests
6. Logout: Call /auth/logout to invalidate the session

​

Related Endpoints

• GET /auth/my-profile - Get current user profile
• POST /users/register - Register new user
• GET /auth/is-valid-jurisdiction - Check jurisdiction validity