Configs
Get or Create Config
Get or create an application config for a linked account.
POST
Get or create the config (app installation) for an app on a linked account. If a config already exists it is returned; otherwise a new one is created. The
config_id defaults to the linked account ID.
Only slug is required. With just a slug, this installs the config’s field and workflow skeleton (the app’s definitions, with default values) — it does not need any field values up front. You can optionally seed workflows (enable/disable) and labels in the body. Field values are normally set afterward via Update Config Field Value, which is the reliable way to populate them.
Multiple configs per account. Omit
config_id to manage the single default config (its ID is the linked account ID). Pass a custom config_id (e.g. production, staging) to create and manage additional named configs for the same linked account and app. Each is retrieved with Get Config by ID and all are returned by List Config IDs.Authentication
Configs are scoped to a linked account via thelinked_account_id header.
Your Refold API key. Find it in Settings → Credentials.
The linked account to install the config for.
Body Parameters
The app slug to install. This is the only required field. Example:
hubspotA custom ID to create/manage a distinct named config for this account+app (e.g.
production). Omit it to use the single default config (ID = the linked account ID).Workflows to enable or disable at install, each
{ "id": "...", "enabled": true }.Arbitrary key/value labels for the config.
Optional initial field definitions, each
{ "id": "...", "value": ... }. Field values are more reliably set after install via Update Config Field Value.Response
- 200 OK
- 404 Not Found