Source endpoints allow you to manage sources in a specified environment.
You must be a member of the environment and be assigned to an engineer role to manage sources. Learn about roles.
Update source
Update the human readable name of an existing source within the specified environment. You must use the correct source and environment identifiers.
cURL request example
Path Parameters
- sourceIdrequired, string
Displays the unique identifier of an source within a given environment.
Request Body Schema
- namestring
Displays the human-readable name of the source.
Contains the fields that can be used to update an existing source. You can populate one or more fields. Any new or changed data replaces existing entries. If you don't use one or more fields, the existing data stays the same; in other words, it's not overwritten with a blank entry.
- 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 payload with details about the requested source(s).
- sourceobject
Contains a source and its related details.
- namestring
Displays the human-readable name of the source.
- idstring
Displays the unique identifier (i.e., client ID) of the source.
- environmentobject
Contains metadata about the environment within the associated Redox organization.
- idstring
Contains the unique identifier of the Redox environment.
Format: uuid - environmentFlagstring
Indicates whether the environment is used for development, staging, or production.
Possible Values:Production
,Staging
,Development