WOL API

Interact with the Wake-up On LAN website via its REST API using curl. There are 2 major features: A catering system, and event registration system.

Step 1 — Resolve credentials

Run these two shell commands to check for environment variables:

echo "${WOL_API_TOKEN}"
echo "${WOL_BASE_URL}"

• If WOL_API_TOKEN is empty, ask the user:

  "Please paste your API token, or configure the WOL_API_TOKEN environment variable. You can generate one at /user/api-tokens on the WOL site."

• If WOL_BASE_URL is empty, asume https://wollan.nl as the base url.

Store the resolved values as TOKEN and BASE_URL for use in the commands below.

Step 2 — Dispatch on user intent

Look at $ARGUMENTS and/or the user's message to determine which action to take.

Catering: List products / show the menu

Trigger: $ARGUMENTS contains products, or the user asks what is available / what's on the menu.

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/catering/products"

Present the result grouped by category. For each product show:

• Name
• Price formatted as €X.XX (response values are in euro cents — divide by 100)
• Stock status (inStock / out of stock)
• Product ID (the user needs this to place an order)

Catering: Place an order

Trigger: $ARGUMENTS contains order, or the user says they want to order something.

Parse items from $ARGUMENTS in the format productId:quantity,... (e.g. order 3:2,5:1 means product 3 qty 2, product 5 qty 1). If no items are provided in $ARGUMENTS, ask the user which products and quantities they want (show the menu first if needed). Assume a quantity of 1 if the user provides a product or list of products without quantities.

Build the JSON body and POST:

curl -s -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"items": [{"productId": PRODUCT_ID, "quantity": QUANTITY}]}' \
  "$BASE_URL/api/v1/catering/orders"

On 201 Created: show a confirmation with the order ID, items, and total cost (sum of quantity × productPrice for all items, formatted as €X.XX).

Catering: View order history and account balance

Trigger: $ARGUMENTS contains history, is empty, or the user asks about their orders / balance.

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/catering/orders"

Present the account summary as a table:

Then list each order with its ID, date, status, and items. Only show the detailed order list if the user asks for it.

Order status meanings:

• accepted — received, being prepared
• waiting — queued behind other orders
• ready — ready for pick-up
• complete — picked up / done
• cancelled / rejected — not fulfilled

Event registration: Check event status

Trigger: $ARGUMENTS contains eventstatus, or user asks if the WOL registrations are open or not

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/events/zijn-de-inschrijvingen-al-open-of-nie"

Returns: open: true|false, with eventId if true.

Event registration: Register for event

Trigger: $ARGUMENTS contains register, or user asks to register for the next WOL event. Use "Check event status" to check if registrations are open or not, and if so, use that eventId to register the user with the following call:

curl -s -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  "$BASE_URL/api/v1/events/{eventId}/register"

The result is a simple success:true

Event registration: Check user registration status for an event

Trigger: $ARGUMENTS contains registration-status, or user asks to check his payment status for his registration for the next WOL event. Use "Check event status" to check if registrations are open or not, and if so, use that eventId to check the users' registration status with the following call:

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/events/{eventId}/registration-status"

Error handling

Notes

• All monetary values in API responses are in euro cents. Always divide by 100 before displaying (250 → €2.50).
• The curl -s flag suppresses progress output. Pipe through | python3 -m json.tool or similar if you want to inspect raw JSON.
• Tokens are managed at /user/api-tokens (web UI, requires login). Each token can have a name and optional expiry date.