API Routes Overview

Complete reference for all server API endpoints.

Base URL

Most routes require authentication. Include the JWT token in the Authorization header:


Authorization: Bearer <your-jwt-token>

Create a new user account.

Body:


{
  "name": "John Doe",
  "email": "john@example.com",
  "password": "securepassword",
  "repeatPassword": "securepassword"
}

Response:


{
  "user": {
    "id": "123",
    "name": "John Doe",
    "email": "john@example.com",
    "plan": "pro"
  },
  "accessToken": "jwt-token"
}

Body:


{
  "email": "john@example.com",
  "password": "securepassword"
}

Body:


{
  "credential": "google-id-token"
}

Get current user information. Requires authentication.

Response:


{
  "user": {
    "id": "123",
    "name": "John Doe",
    "email": "john@example.com",
    "plan": "pro",
    "isAdmin": false
  }
}

Get list of all users (admin only).

Query Parameters:

Get specific user details (admin only).

Update user information (admin only).

Delete a user (admin only).

Get billing information for current user.

Response:


{
  "billing": {
    "currentPlan": "pro",
    "stripeCustomerId": "cus_123",
    "oneTimePurchases": [...],
    "subscriptions": [...]
  }
}

Get billing history for current user.

Stripe webhook endpoint for payment events.

Events handled:

This endpoint must be publicly accessible and verify Stripe signatures.