REST API

BuddyWoo exposes a small read-only REST API under the buddywoo/v1 namespace, for building custom or mobile front ends. Every personal endpoint returns only the current user’s own data and never accepts a user id.

Endpoints

Method and route	Auth	Returns
GET /buddywoo/v1/config	Public	Bridge config: version, profile stack, and every tab’s enabled, label, slug, and position
GET /buddywoo/v1/me/orders	Logged in	The current user’s orders
GET /buddywoo/v1/me/downloads	Logged in	The current user’s available downloads
GET /buddywoo/v1/me/reviews	Logged in	The current user’s approved product reviews

Requests to the /me/* routes when not logged in return a 401 error.

Pagination

GET /me/orders and GET /me/reviews accept these query parameters:

Parameter	Type	Default	Range
page	integer	1	minimum 1
per_page	integer	12	1 to 100

GET /me/downloads is not paginated; it returns all of the current user’s available downloads in one response.

Response shape

The list endpoints return the items plus paging metadata, for example GET /me/orders:

{
  "orders": [
    {
      "id": 123,
      "status": "processing",
      "currency": "USD",
      "total": "49.00",
      "item_count": 2,
      "created_at": "2026-01-05T10:00:00+00:00",
      "updated_at": "2026-01-05T10:05:00+00:00",
      "view_url": "https://example.com/my-account/view-order/123/"
    }
  ],
  "total": 1,
  "pages": 1,
  "has_more": false
}

GET /me/reviews returns reviews with id, product_id, product_name, rating, content, and created_at. GET /me/downloads returns downloads with product_id, product_name, download_id, download_name, download_url, downloads_remaining, access_expires, and order_id.

Filtering the output

Each response can be shaped with a filter: buddywoo_rest_app_config for /config, and buddywoo_rest_prepare_order, buddywoo_rest_prepare_download, and buddywoo_rest_prepare_review for each item on the respective list endpoints.