Discussions
Security Groups - API
Would like to get the option to create/update security groups via the API. In enterprise level implementations we often see the need for different security groups per business unit, where assets created should not always be shared with the entire enterprise.
This results in a lot of clicks in the UI after cloning a security group to set the correct default asset permissions.
If we could handle this via the API that could save us a massive amount of time in these large implementations.
Comments
-
Hi Simon this is the endpoint the Eloqua is using.
https://secure.p06.eloqua.com/API/REST/2.0/assets/email/group
this is the body of the request.
{
"name": "Untitled Email Group",
"id": "-500002",
"createdBy": "297",
"createdAt": "1509709681",
"type": "EmailGroup",
"permissions": ["Retrieve", "Update", "Delete", "SetSecurity"],
"emailHeaderId": "9",
"emailFooterId": "16",
"isVisibleInOutlookPlugin": "true",
"isVisibleInPublicSubscriptionList": "true",
"subscriptionLandingPageId": "67",
"unsubscriptionLandingPageId": "67",
"x_e10_isTemplate": "false",
"depth": "complete"
}
-
Hi Simon this is the endpoint the Eloqua is using.
https://secure.p06.eloqua.com/API/REST/2.0/assets/email/group
this is the body of the request.
{
"name": "Untitled Email Group",
"id": "-500002",
"createdBy": "297",
"createdAt": "1509709681",
"type": "EmailGroup",
"permissions": ["Retrieve", "Update", "Delete", "SetSecurity"],
"emailHeaderId": "9",
"emailFooterId": "16",
"isVisibleInOutlookPlugin": "true",
"isVisibleInPublicSubscriptionList": "true",
"subscriptionLandingPageId": "67",
"unsubscriptionLandingPageId": "67",
"x_e10_isTemplate": "false",
"depth": "complete"
}
the only problem is the Permission but you may get around it by using a different user with the default asset permissions
-
Hi Simon this is the endpoint the Eloqua is using.
https://secure.p06.eloqua.com/API/REST/2.0/assets/email/group
this is the body of the request.
{
"name": "Untitled Email Group",
"id": "-500002",
"createdBy": "297",
"createdAt": "1509709681",
"type": "EmailGroup",
"permissions": ["Retrieve", "Update", "Delete", "SetSecurity"],
"emailHeaderId": "9",
"emailFooterId": "16",
"isVisibleInOutlookPlugin": "true",
"isVisibleInPublicSubscriptionList": "true",
"subscriptionLandingPageId": "67",
"unsubscriptionLandingPageId": "67",
"x_e10_isTemplate": "false",
"depth": "complete"
}
Thanks Jacob, but it's security groups I'm looking for, not email groups.
-
API updates to Security Group membership would be useful in situations where we need to restrict access to certain contacts based on actions or triggers that happen in CRM or other external systems.
Adjusting contacts security model via a Program is not always timely, especially since contacts can only enter once a day at the moment.
Thanks for voting this up.
-
API updates to Security Group membership would be useful in situations where we need to restrict access to certain contacts based on actions or triggers that happen in CRM or other external systems.
Adjusting contacts security model via a Program is not always timely, especially since contacts can only enter once a day at the moment.
Thanks for voting this up.
The label assignment workflow allows for contacts to enter every hour.
-
The label assignment workflow allows for contacts to enter every hour.
with the new feeder (field listener) you could add up to 3 fields as a feeder, as if a new contact was created.
-
We have the same requirement for our client, the recent updates to the API allow for more SSO standard funcitons but are not incouding the provisioning of groups at this time. This will make the adoption alot easier compared to other competing systems and provide a simpler operations step for enterprise customers with established user and role automated creation.
