During API discovery, APIs with the same name are merged across environments. With this setting, the naming strategy for an API in the OpenAPI Specification can be configured, which is then used as the basis for finding duplicates and merging APIsthat are present in multiple environments are merged into one API in the API Control Plane. This setting configures which strategy is used to identify APIs across the different environments.
...
Name in gateway: Use the API name as configured in the gateway. This is also the fallback if any other strategy fails to find a name.
Title in API specification: Use the title field from inside the API specification file.
First tag in API specification: Use the name of the first tag in the API specification file.
This only affects the technical API name, which is used to determine if two APIs are the same. The displayName will still be as configured in the gateway (for new APIs) and not be changed when merging a discovered API with an existing one.