API to get group properties

On of the group name is having forward slash so the URL to get properties of group is like https://api.hubapi.com/properties/v1/contacts/groups/named/forward/slash?hapikey=

Here forward/slash is the name of group. How to handle forward slash in above URL

?

Hi @nachiket

I imagine it is best practice to not use a forward slash in your group name. But, we do allow you to create that naming convention so even if you knew not to do it, someone else could…

I am asking around internally about this, but just in case, I will also shout out to @Mike_Eastwood to see if he has a clever idea (he usually does :grinning_face:)

Hi @nachiket

If you change your slash to %2F does it work?

Using your example:

https://api.hubapi.com/properties/v1/contacts/groups/named/forward%2Fslash?hapikey=

Also, you may want to check your Group Name’s variable name – I’d assume HubSpot had changed the variable name to a dash.

https://api.hubapi.com/properties/v1/contacts/groups/named/forward-slash?hapikey=

Personally I avoid using any Speacial Charaters (& amphersand, / slash, – ndash, etc.) in my property names and group names.

Have fun

Mike

@Mike_Eastwood ,

sadly the %2f does not work. (I thought this was going to be an easy one and that was the first thing I tried)

This is being investigated and I will report back when I have more info

Hi @nachiket

I’ve tried using

https://api.hubapi.com/properties/v1/contacts/groups/named/forward%2Fslash/?hapikey=XXXXXX-XXXXXX-XXXhttps://api.hubapi.com/properties/v1/contacts/groups/named/forward\/slash/?hapikey=XXXXXX-XXXXXX-XXX

When I use the API to get all Property Groups the Name and the displayName so you may need to rename your Group.

 {
 "name": "forward/slash",
 "displayName": "forward/slash",
 ...
 }

So, if you really want to use a name with a slash (which isn’t ideal as you’ve found) here’s what to do:

1. create a new property group called “forward_slash”

2. rename the group to “forward/slash”

3. move your properties to the new group.

You end up with this:

{
 "name": "forward_slash",
 "displayName": "forward/slash",
 ...
}

Now when you call the Property Group – with your code – use “forward_slash”.

Have fun

Mike

p.s. this is tested using Postman in a Demo Portal

@nachiket , @Mike_Eastwood

Just a heads up that this will not be fixed for the v1 endpoint.

You can use the v3 endpoint with the url encoded slash and it will work. I am really not sure why I didn’t try that first :roll_eyes:

example:

https://api.hubapi.com/crm/v3/properties/contacts/groups/forward%2Fslash