app

Move a Greenhouse installation onto the config-driven Greenhouse API (or back off it)

post/v1/app/org/{orgId}/install/{appUserId}/upgrade-greenhouse

Request

  • Base URL: https://localhost
  • URL: https://localhost/v1/app/org/{orgId}/install/{appUserId}/upgrade-greenhouse
  • Auth: none declared

Path parameters

orgIdstring required

Org identifier (either id or slug)

appUserIdstring required

App user id

Query parameters

downgradeboolean

Re-pin the installation to the legacy Greenhouse API instead of upgrading it

Response

installation upgraded or downgraded

legacyApiboolean required

True when the installation is now pinned to the legacy Greenhouse API

migratedOutboundFieldMappersinteger required

How many of the installation's custom job field mappers were copied into its config-driven outbound field mappers

unmigratableFieldMappersstring[] required

Custom field mappers the config-driven path cannot express, each as "charthopFields -> remoteField: why". Non-empty means the installation is upgraded but writes fewer fields than before until these are reconfigured by hand.

Changes

No recorded changes to this operation across all 25 revisions of this API.