Config endpoints allow you to review metadata of available Redox base configs and related source links. Learn about mapping operations.
Base configs can be linked to sources within your Redox organization to convert a payload from a one data format to the appropriate Redox data model or FHIR® resource.
Anyone in a Redox organization can view metadata of base configs and source links. However, only a Redoxer can view or modify the content of base configs, and only a user assigned to an engineer or support role can manage source links.
You can:
- retrieve a list of available base configs;
- retrieve a list of links attached to a source;
- create base config links to sources;
- update base config links to sources; or
- delete base config links to sources.
Update link
Update an existing source link to a base config. All link metadata can be modified, but you only need to include the specific fields you want to update.
You must be assigned to an engineer or support role to use this endpoint.
cURL request example
Path Parameters
- configLinkIdrequired, string
Contains the unique identifier of the base config link.
Request Body Schema
- configIdstring
Displays the unique identifier of the base config to link to the source. If provided, version is required.
Format: uuid - versionstring
Specifies the version of the base config to use. Required when configId is provided.
Format: uuid - dataModelstring
Identifies the Redox data model that this config link applies to.
- eventTypenullable, string
Specifies the event types of the given Redox data model that the link applies to. If
null
, the config is linked to all event types of the data model.
Contains the fields that can be updated in an existing base config link. All fields are optional and any provided values replace the existing data.
- metaobject
- versionstring
Lists the major and minor version number for the format of the returned payload. The payload format or shape may change between minor versions, like including additional or extended fields in later versions. We include the version data in each response so that you have the option to handle the signaled differences.
- payloadobject
Contains the details about the specified base config link.
- configLinkobject
Contains a base config link and its related details.
- idstring
Displays the unique identifier of the link between the source and base config.
Format: uuid - configIdstring
Displays the unique identifier of the base config being linked to the source.
Format: uuid - processingLocationstring
Indicates whether the base config applies to request or response processing.
Possible Values:request
,response
- versionstring
Specifies the version of the base config being used.
Format: uuid - dataModelstring
Identifies the Redox data model that this config link applies to.
- eventTypenullable, string
Specifies the event types of the given Redox data model that the link applies to. If
null
, the config is linked to all event types of the data model.