Wildcards in query parameters

1

Hello

I've discovered that it is possible to use * as a wildcard in the filter query parameters in some requests. For example: GET api/v2/telephony/providers/edges/phones?name=*Adrian* gives me the list of phones with "Adrian" in their name.

I did not find any documentation about this. So my question is: Is this an intended behavior? Can we rely on it? If it does, then, are there any more wildcards available?

Thank you!

2

It's not documented, but the dev team has confirmed that the wildcard syntax is officially supported.

1 Like
3

Thank you Tim. Is * the only wildcard available?

4

yes, as far as I know.

5

I've made another test and it looks like it does not work with all entities... for example: GET /api/v2/routing/queues?name=Sampl*_queue do not match a queue named Sample_queue...

Also... I've found that [] works too, but only for some entities, to define a list of characters... For example:

  • GET /api/v2/authorization/roles?name=M[ai]ster Admin do match with the role named Master Admin
    but
  • GET /api/v2/telephony/providers/edges/phones?name=W[ei]bRTC_Adrian does not match with the phone named WebRTC_Adrian

I mean, this is quite inconsistent... Could you please check it and confirm which wildcards are valid for which queries?

Thank you

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.