Configurations and ConfigPress

Overview

Read or change AAM configuration and the ConfigPress INI document. Routes use /wp-json/aam/v2 on a standard WordPress installation.

Endpoints

Method Route Input Purpose
GET /config/{key} key Get configuration.
POST /config/{key} key, value Set configuration.
GET /configpress — Get configpress.
POST /configpress ini Set configpress.
DELETE /configpress — Reset configpress.
GET /configs — Get configurations.
DELETE /configs — Reset configurations.

The Input column lists route-specific parameters. A path parameter in {braces} is required. WordPress validates body and query parameters against the registered route schema.

Parameter guide

The route table shows which operation uses each parameter. Path parameters are required; other requirements depend on the operation.

Parameter Type Meaning
ini string ConfigPress INI.
key string Configuration key.
value mixed Configuration value.

Access level and authorization

This endpoint group does not use the shared access-level selector unless a row explicitly names it.

Required permission: aam_manager and aam_manage_configs. See Authentication and Error handling.

Configuration routes do not take an access level. POST /configpress accepts an ini string; POST /config/{key} accepts value. See ConfigPress for INI syntax.

Example

GET /wp-json/aam/v2/configpress
Authorization: Basic <base64 username:application-password>

This reads the stored ConfigPress INI document. No access-level parameter is needed.

To save a new INI document, send POST /wp-json/aam/v2/configpress with JSON such as {"ini":"[aam]\nservice.secure_login.login_attempts = 5"}. AAM returns the stored ini and parsed values; the change is loaded on a later request.