Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel3
typeflat

...

Overview

The following operations allow you to work with Users. Click an operation name to see details on how to use it.

For a sample proxy service that illustrates how to work with Users, see Sample configuration .

For more details click Users.

OperationDescription
1Working with Users getCurrentUserRetrieves the details of the current user .
1Working with UsersgetAllUsersRetrieves all Users' public details.
getAUser Retrieves the details of specified user id.
1Working with UsersupdateAUserUpdates details of a user associated with the specified user id.

Operation Details

This section provides further details on the operations related to Users.

Anchor
getCurrentUser
getCurrentUser
Get Current User

The getCurrentUser operation retrieves the information of current user.

Code Block
languagexml
titlegetCurrentUser
<eloqua.getCurrentUser>
    <depth>Complete</depth>
    <extensions></extensions>
</eloqua.getCurrentUser>
properties

  • depth      : The RequestDepth. It can be 'complete' or 'Reference' or 'Minimal' or 'Partial'.

  • extensions : The extensions to filter. Must follow the pattern : ^[A-Za-z0-9]+$.

Sample request

Following is a sample REST/JSON request that can be handled by the getCurrentUser operation.

Code Block
languagexml
titleSample request for getCurrentUser
{
   "username":"myusername",
   "password":"mypassword",
   "siteName":"mysiteName",
   "depth":"Complete"
}

Anchor
getAllUsers
getAllUsers
Get All Users

The getAllUsers operation retrieves all users' details.

Code Block
languagexml
titlegetAllUsers
<eloqua.getAllUsers>
    <count>2</count>
    <depth>1</depth>
    <search></search>
    <page>1</page>
    <orderBy></orderBy>
    <lastUpdatedAt>1426066807</lastUpdatedAt>
    <extensions></extensions>
</eloqua.getAllUsers>
properties

  • count         : The number of results in a page to display. This must me in between 1 and 1000.

  • depth         : The RequestDepth. It can be 'Complete' or 'Reference' or 'Minimal' or 'Partial'.

  • search        : The search field, to search for that field.

  • page          : The page number to display. This must be greater than 1.

  • orderBy       : The order by property to order the fields.

  • lastUpdatedAt : The date time of the last update.

  • extensions    : The extensions to filter. Must follow the pattern : ^[A-Za-z0-9]+$.

Anchor
sampleRequest
sampleRequest
Sample Request

Following is a sample REST/JSON request that can be handled by getAllUsers operation.

Code Block
languagexml
titleSample request for getAllUsers
{   
   "username":"myusername",
   "password":"mypassword",
   "siteName":"mysiteName",
   "count":2,
   "page":1,
   "lastUpdatedAt":1426066807,
   "depth":"Complete"
}

Anchor
getAUser
getAUser
Get A User

The getAUser operation retrieves the details of a user details associated with the specified user id.

Code Block
languagexml
titlegetAUser
<eloqua.getAUser>
	<userId>10</userId>
	<depth>Complete</depth>
    <extensions></extensions>
</eloqua.getAUser>
properties

  • userId     : Unique identifier of the user.

  • depth      : The RequestDepth. It can be 'Complete' or 'Reference' or 'Minimal' or 'Partial'.

  • extensions : The extensions to filter. Must follow the pattern : ^[A-Za-z0-9]+$.

Sample request

Following is a sample REST/JSON request that can be handled by the getAUser operation.

Code Block
languagexml
titleSample request for getAUser
{   
   "username":"myusername",
   "password":"mypassword",
   "siteName":"mysiteName",
   "userId":"1",
   "depth":"Complete"
}

Anchor
updateAUser
updateAUser
Update A User

The updateAUser operation updates the user details associated with the specified user id.

Code Block
languagexml
titleupdateAUser
<eloqua.updateAUser>
	<name>new user</name>
	<userId>10</userId>
	<loginName>iamcool</loginName>
	<company>my company</company>
	<emailAddress>iamcoolmail@gmail.com</emailAddress>
	<preferences>{"type": "UserPreferences","isMasterViewDocked": "false","timezoneId": "64"}</preferences>
	<typePermissions>[{"type": "TypePermission","objectType": "Campaign","permissions": {"type": "TypePermissions","create": "true","read": "true"}},{"type": "TypePermission","objectType": "Email","permissions": {"type": "TypePermissions","create": "true","read": "true"}}]</typePermissions>
	<capabilities>["manageStrictWebTracking", "mailer.updateContacts"]</capabilities>
	<betaAccess>["chatter_inside", "sfdc_sso", "sfdcidp"]</betaAccess>
	<loggedInAt>1297278692</loggedInAt>
	<defaultContactViewId>1</defaultContactViewId>
	<defaultAccountViewId>1</defaultAccountViewId>
	<interfacePermissions>[{"type": "InterfacePermission","interfaceCode": "campaigns","nestedInterfacePermissions":[{"type": "InterfacePermission","interfaceCode": "campaigns","nestedInterfacePermissions":[{"type": "InterfacePermission","interfaceCode": "campaigns"}]}]}]</interfacePermissions>
	<productPermissions>[{"type": "ProductPermission","productCode": "EngageiPad"},{"type": "ProductPermission","productCode": "EngageWeb"}]</productPermissions>
</eloqua.updateAUser>
properties

  • userId               : Unique identifier of the user.

  • name                 : The name of the user to update the name as it is.

  • loginName            : Username of the user to log in.

  • company              : Company name of the user.

  • emailAddress         : Email address of the user.

  • loggedInAt           : Integer value, this indicates where the user logged in.

  • preferences          : User preferences object, this will contain timezoneId and isMasterViewDocked properties.

  • typePermissions      : List of type permission objects.

  • capabilities         : List of string values.

  • betaAccess           : List of string values.

  • defaultContactViewId : The default view id of Contacts.

  • defaultAccountViewId : The default view id of Accounts.

  • interfacePermissions : List of interfacePermission objects.

  • productPermissions   : List of productPermission objects.

Sample request

Following is a sample REST/JSON request that can be handled by the updateAUser operation.

Code Block
languagexml
titleSample request for updateAUser
{  
   "username":"myusername",
   "password":"mypassword",
   "siteName":"mysiteName",
   "name":"new user",
   "userId":"10",
   "loginName":"iamcool",
   "company":"my company",
   "emailAddress":"iamcoolmail@gmail.com",
   "loggedInAt":1297278692,
   "preferences":{"type": "UserPreferences","isMasterViewDocked": "false","timezoneId": "64"},
   "typePermissions":[{"type": "TypePermission","objectType": "Campaign","permissions": {"type": "TypePermissions","create": "true","read": "true"}},{"type": "TypePermission","objectType": "Email","permissions": {"type": "TypePermissions","create": "true","read": "true"}}],
   "capabilities":["manageStrictWebTracking", "mailer.updateContacts"],
   "betaAccess":["chatter_inside", "sfdc_sso", "sfdcidp"],
   "defaultContactViewId":"1",
   "defaultAccountViewId":"1",
   "interfacePermissions":[{"type": "InterfacePermission","interfaceCode": "campaigns","nestedInterfacePermissions":[{"type": "InterfacePermission","interfaceCode": "campaigns","nestedInterfacePermissions":[{"type": "InterfacePermission","interfaceCode": "campaigns"}]}]}],
   "productPermissions":[{"type": "ProductPermission","productCode": "EngageiPad"},{"type": "ProductPermission","productCode": "EngageWeb"}]
}

Anchor
sampleProxy
sampleProxy
Sample Configuration

Following is a sample proxy service that illustrates how to connect to Eloqua Standard API with the init operation to use the getAllUsers operation. The sample request for this proxy can be found in getAllUsers sample request . You can use this sample as a template for using other operations in this category.

...