There are multiple ways to access lookup transforms via REST, including:
Which one should I be using?
Here is when you ought to use each endpoint:
Generally, it is recommended that you avoid using data/transforms/lookups/ since this endpoint triggers some activity that can cause some unnecessary performance reduction and will generate a substantial number of log messages in the internal index.
If you need to access ACL information (i.e. namespace and owner) then you will need to use configs/conf-transforms since properties/transforms/ won't include it.
Here is when you ought to use each endpoint:
Generally, it is recommended that you avoid using data/transforms/lookups/ since this endpoint triggers some activity that can cause some unnecessary performance reduction and will generate a substantial number of log messages in the internal index.
If you need to access ACL information (i.e. namespace and owner) then you will need to use configs/conf-transforms since properties/transforms/ won't include it.
We recommend the following GET arguments when pinpointing lookups using configs/conf-transforms. This is because transforms.conf houses all manner of properties.
getargs = {'output_mode': 'json', 'count': 0, 'search': 'filename=* OR collection=* OR external_type=*'}
Of course, if you're targeting a specific transform by name, this is not needed.