API Reference
The App Config.json REST API allows you to programmatically manage application configurations, sync changes across environments, and version control your settings. All API requests must be made over HTTPS.
All requests require a Bearer token in the Authorization header. Generate tokens from your dashboard under Settings → API Keys.
Authentication
App Config.json uses API keys to authenticate requests. Keep your keys secure and never expose them in client-side code or public repositories.
Refresh an expired access token using a valid refresh token. Tokens expire after 1 hour by default.
| Parameter | Type | Required | Description |
|---|---|---|---|
| refresh_token | string | Required | Your valid refresh token |
| grant_type | string | Optional | Must be `refresh_token` |
List Applications
Returns a paginated list of all applications associated with your API key.
| Query Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | Optional | Number of items per page (max 100) |
| cursor | string | Optional | Pagination cursor from previous response |
Create Application
Registers a new application and initializes its configuration namespace.
| Body Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | Required | Unique application identifier |
| environment | string | Required | Target environment (`dev`, `staging`, `prod`) |
| region | string | Optional | Deployment region (`us-east-1`, `eu-west-1`, etc.) |
Update Configuration
Updates or creates a configuration key-value pair for an application. Changes are queued for real-time sync.
| Body Parameter | Type | Required | Description |
|---|---|---|---|
| value | any | Required | Configuration value (string, number, bool, object, or array) |
| description | string | Optional | Human-readable description |
| encrypt | boolean | Optional | Enable server-side encryption for this key |
Sync Configurations
Triggers an immediate configuration push to all connected application instances. Use this after bulk updates.
Error Codes
App Config.json uses standard HTTP status codes and returns detailed error payloads.
| Status | Code | Description |
|---|---|---|
| 200 | OK | Request successful |
| 201 | Created | Resource successfully created |
| 202 | Accepted | Request accepted for async processing |
| 400 | Bad Request | Invalid parameters or malformed JSON |
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | Insufficient permissions for this resource |
| 404 | Not Found | Resource does not exist |
| 429 | Too Many Requests | Rate limit exceeded (100 req/min) |
| 500 | Internal Error | Unexpected server failure |