Config

Configuration Management

Endpoints for managing the general application configuration, uploaded files, and currencies.

Configuration

GET /config

Retrieves the current application configuration.

Authorization: None (public).

cURL Example:

curl -X GET "http://127.0.0.1:9154/config"

Response Body (200 OK):

{
  "id": 1,
  "businessType": "store",
  "businessName": "Ambrosia Restaurant",
  "businessAddress": "123 Main Street, Anytown",
  "businessPhone": "555-1234",
  "businessEmail": "contact@ambrosia.com",
  "businessTaxId": "ABC123456",
  "businessLogoUrl": null,
  "businessTypeConfirmed": false
}

Response Body (404 Not Found):

"Config not found"

PUT /config

Updates the application configuration.

Authorization: settings_update

Full object

This endpoint requires the complete configuration object. Omitting required fields (businessName, businessType) results in 500 Internal Server Error.

Request Body:

{
  "businessType": "store",
  "businessName": "string",
  "businessAddress": "string (optional)",
  "businessPhone": "string (optional)",
  "businessEmail": "string (optional)",
  "businessTaxId": "string (optional)",
  "businessLogoUrl": "string (optional)",
  "businessTypeConfirmed": false
}

cURL Example:

curl -X PUT "http://127.0.0.1:9154/config" \
  -H "Cookie: accessToken=$ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "businessType": "store",
    "businessName": "Ambrosia Updated",
    "businessAddress": "456 Oak Avenue, Anytown",
    "businessPhone": "555-5678",
    "businessEmail": "info@ambrosia.com",
    "businessTaxId": "XYZ987654",
    "businessLogoUrl": null,
    "businessTypeConfirmed": true
  }'

Response Body (200 OK):

{ "message": "Config updated successfully" }

Response Body (404 Not Found):

"Failed to update config"

Files

POST /uploads

Uploads one or more files to the server (images, logos, etc.).

Authorization: requires accessToken if the system is already initialized; open during initial setup.

Content-Type: multipart/form-data.

cURL Example:

curl -X POST "http://127.0.0.1:9154/uploads" \
  -H "Cookie: accessToken=$ACCESS_TOKEN" \
  -F "file=@/path/to/logo.png"

Response Body (201 Created):

{
  "uploads": [
    {
      "path": "/uploads/logo.png",
      "url": "http://127.0.0.1:9154/uploads/logo.png"
    }
  ]
}

Response Body (400 Bad Request):

{ "message": "No files uploaded" }

GET /uploads/{filename}

Accesses a previously uploaded file (static files, no authentication).

cURL Example:

curl -X GET "http://127.0.0.1:9154/uploads/logo.png"

Currencies

GET /currencies

Lists all currencies available in the system.

Authorization: settings_read

cURL Example:

curl -X GET "http://127.0.0.1:9154/currencies" \
  -H "Cookie: accessToken=$ACCESS_TOKEN"

Response Body (200 OK):

[
  {
    "id": "1",
    "acronym": "USD",
    "name": "US Dollar",
    "symbol": "$",
    "countryName": "United States",
    "countryCode": "US"
  },
  {
    "id": "2",
    "acronym": "EUR",
    "name": "Euro",
    "symbol": "€",
    "countryName": "European Union",
    "countryCode": "EU"
  }
]

GET /base-currency

Retrieves the base currency configured for the business.

Authorization: none — this endpoint is public.

Duplicated endpoint: the public version wins

GET /base-currency is registered twice: a public version in Routing.kt and one protected by settings_read in Currency.kt. Api.kt calls configureRouting() before configureCurrency(), so the public route is registered first and is the one that answers. The authenticated version is unreachable, along with its 404 { "message": "Base currency not set" } response.

cURL Example:

curl -X GET "http://127.0.0.1:9154/base-currency"

Response Body (200 OK - base currency configured):

{
  "currencyId": "bccfc932-d89b-477a-b65b-04f97cae4aae",
  "id": "bccfc932-d89b-477a-b65b-04f97cae4aae",
  "acronym": "USD",
  "name": "United States Dollar",
  "symbol": "$",
  "countryName": "United States",
  "countryCode": "US"
}

currencyId and id are duplicated

BaseCurrencyResponse declares both fields and the server fills them with the same UUID. Redundant, but that is how it responds today.

Response Body (200 OK - no base currency configured):

{ "currency_id": null }

Naming inconsistency

Note the key change: when a base currency exists, the object uses currencyId (camelCase); when it does not, the response is { "currency_id": null } (snake_case), because that branch is built from a literal mapOf in Routing.kt. Clients must handle both shapes.

PUT /base-currency

Sets the base currency by acronym.

Authorization: settings_update

Request Body:

{ "acronym": "USD" }

cURL Example:

curl -X PUT "http://127.0.0.1:9154/base-currency" \
  -H "Cookie: accessToken=$ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "acronym": "USD" }'

Response Body (200 OK):

{
  "id": "1",
  "acronym": "USD",
  "name": "US Dollar",
  "symbol": "$"
}

Response Body (400 Bad Request):

{ "message": "Acronym is required" }

Response Body (404 Not Found):

{ "message": "Unknown currency acronym: XYZ" }