Service Configuration
Appmixer allows you to save global configuration values for your service. If a component contains either an auth section or authConfig section, values for specified service will be injected.
Only users with admin scope can use these endpoints.
Get Services Configuration
GET
/service-config
Get a list of stored configurations.
Query Parameters
pattern
string
A term to filter configurations containing pattern on their service id
sort
string
Sorting parameter. Service id can be used to sort results alphabetically by their id. Example: serviceId:1
offset
number
Index of the first item returned. Default is 0. Useful for paging.
limit
number
Maximum items returned. Default is 100. Useful for paging.
Get Service Configuration
GET
/service-config/:serviceId
Get the configuration stored for the given service.
Path Parameters
string
The service id. Example: appmixer:google
Create Service Configuration
POST
/service-config
Creates a new configuration for a service. The only required parameter on the payload is the serviceId. The rest of the payload can be any key/value pairs that will be the desired configuration for the service. For example:
{
"serviceId": "appmixer:google",
"clientID": "my-global-client-id",
"clientSecret": "my-global-client-secret"
}
Request Body
whatever
string
Any value for the whatever-key
serviceId
string
The serviceId. It should be in the form vendor:service
. Example: appmixer:google
Update Service Configuration
PUT
/service-config/:serviceId
Updates the stored configuration for the given service. The payload should contain the whole configuration, as the payload content will overwrite the configuration stored under the service.
Path Parameters
serviceId
string
The service id. Example
Request Body
whatever-key
string
Any value you need
Delete Service Configuration
DELETE
/service-config/:serviceId
Removes the configuration from the given service.
Path Parameters
serviceId
string
The service id. Example: appmixer:google
Last updated