Data masking for API name with spaces is not working

sgarg24
Participant II

We want to utilize the Data masking management API at specific API proxy level.

https://docs.apigee.com/management/apis/post/organizations/%7Borg_name%7D/apis/%7Bapi_name%7D/maskco...

If our proxy name & display name are single word like "Accounts", the data masking is reflecting.

But if our proxy name is having spaces like "V2 - Accounts", the data masking get applied, but does not become applicable at run time. We are still able to see unmasked request content.

Is there a specific way to mention api name in POST mask config call?

We have tried following:

1) POST /apis/V2 - Accounts/maskconfigs/default

2) POST /apis/V2%20-%20Accounts/maskconfigs/default

Both formats get posted and retrieved successfully by data masking management api, but neither of them cause data masking to come in effect.

Note: For both proxies we ahve application/json Content type being passed in request headers.

1 4 179
4 REPLIES 4

You shouldn't be able to create a proxy with a name that includes spaces.

When you get the list of APIs what do you see?

GET {{MGMTSVR}}/v1/o/{{ORG}}/apis

Yes we can create.

Hmmm, I see that can be done via management APIs, but the UI does not allow it, therefore, I'd stay away from spaces in API proxy names.

Yes, we used management APIs to create proxies. Since technically it is allowed, one would expect all management APIs to be compatible with other APIs.