Contact Lists

Get multiple Contact Lists

Read the data for multiple Contact Lists.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

SecurityHeaderToken
Request
query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
$filter
string

Use the $filter parameter to filter returned data Items in a manner similar to the Alliant User Applications column filter. This parameter uses the following format: {filterBy} {operator} {value}

  • filterBy is the name of a property, the name of a Reference property specified as referenceProperty.property, or the name of Reference property for quality or inequality comparisons to null.

  • operator – specify one of the following operators:

    Operator Description filterBy datatype
    contains Contains String/Text
    endswith Ends with String/Text
    startswith Starts with String/Text
    eq Equals String/Text, Integer, Small Integer, Flag/Boolean, Reference property eq null
    ne Does not equal String/Text, Integer, Small Integer, Flag/Boolean, Reference property ne null
    le Less than or equal to String/Text, Integer, Small Integer, Flag/Boolean, DateTime
    lt Less than String/Text, Integer, Small Integer, Flag/Boolean, DateTime
    ge Greater than or equal to String/Text, Integer, Small Integer, Flag/Boolean, DateTime
    gt Greater than String/Text, Integer, Small Integer, Flag/Boolean, DateTime
  • value is the value to which the operator is applied. The value should be enclosed in single quotes unless the value is an Integer or Small Integer

You can use the and and or operators to combine multiple filter parameter criteria.

Examples:
The response includes only data Items with a displayName value that contains 'rin'
$filter=displayName contains 'rin'
The response includes only data Items with a comment value that ends with 'ing'
$filter=comment endswith 'ing'
The response includes only data Items with a description value that starts with 'str'
$filter=description startswith 'str'
The response includes a single data Item with an id value equal to 'ABC123'
$filter=id eq 'ABC123'
The response includes only data Items with a udfVersionNumber value equal to 1
$filter=udfVersionNumber ge 1
The response includes only data Items with a displayName value that starts with 'rin' or data Items with a comment value that ends with 'ing' and data Items with description value that starts with 'str'
$filter=(displayName contains 'rin' or comment endswith 'ing') and description startswith 'str'
The response includes only data Items that have no Admin Class
$filter=adminClassReference eq null
$orderby
string

Use the $orderby parameter to specify the sort order of the returned data Items. You can specify a property or a property of a Reference property followed by asc or desc to sort returned data Items by a property in ascending or descending order.

Note: When this parameter is not specified, the returned data Items are sorted by Display Name in ascending order.

Examples:
ascending sort by property1
$orderby=property1
descending sort by property1 of the referenceProperty
$orderby=referenceProperty.property1 desc
$top
integer

Use the $top parameter to specify the maximum number of Items to return. When you do not specify this parameter, 20 Items are returned by default. When you specify the verbose parameter, the maximum number of Items that you can request 100. When you specify the minimal or default parameters, the maximum number of Items that you can request 1000. This query parameter combined with $skip query parameter can be used to facilitate paging.

Examples:
The response includes 30 data Items
$top=30
$skip
integer

Use the $skip parameter to specify the number of Items to skip from the first result. This query parameter combined with the $top query parameter can be used to facilitate paging. For example, $skip=20&$top=20 returns the second page of 20 Items.

Examples:
The response includes data Items that follow the first 30 data Items
$skip=30
autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Responses
200

Success

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

get/api/data/contactListHeaders
Response samples
application/json
{
  • "result": {
    },
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Create a Contact List

Create a Contact List.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

If getOrCreateWithHashCategory query parameter is added then this endpoint gets an existing User-Defined Contact List or creates a new Contact List. If an existing User-Defined Contact List matches List Definition specified in a request (ListDetails and ListXrefs) for a Hash Category specified as a value of getOrCreateWithHashCategory query parameter then this Contact List is returned in a response. In this case, the successful response is indicated with a 200 status code. If no Contact List matches List Definition and Hash Category, then a new Contact List is created. In this case, the successful response is indicated with a 201 status code.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

SecurityHeaderToken
Request
query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
getOrCreateWithHashCategory
string [ 1 .. 60 ] characters

This parameter provides functionality to assist with having an upstream system manage lists within Alliant. The value assigned to this parameter should be an identifier of the specific integration making the call. This will effectively create a namespace for that integration so that if seperate upstream systems are creating and managing lists within Alliant, then these will not impact eachother.

When submitting a list using this parameter, the call should contain all items that are desired to be contained in the list. The response will return details of a list that is either created or matched with those contents. If a list with the same contents exists with a matching getOrCreateWithHashCategory value, indicating that it has previously been created by the same integration, then the list detail will be returned with a 201 status code. If no such list exists, then it will be created and returned with a 200 status code.

Examples:
Get or Create a Contact for a Hash Category 'Data Bridge integration'.
getOrCreateWithHashCategory=Data bridge integration
autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Request Body schema: application/json
required

Include as much information as possible regarding the Contact List

comment
string (Comment) <= 1000 characters

Specify any additional information for the List, when applicable. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

description
required
string (description) [ 1 .. 255 ] characters

Specify the unique “name” of the List. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

includeOnlyCommonItemsFlag
boolean (Flag)

Specify whether to include only the Items that are common to all of the Lists and Items that are specified in the Lists and the Items collections.

Array of objects (List Item Details POST Request Properties)

Contact List Items. Include the guid of the List Item that you want to update or delete when updating the List Details Child Collection.

Array of objects (List List Details POST Request Properties)

Contact List Lists. Include the guid of the List List that you want to update or delete when updating the List List Cross-reference Collection.

Responses
200

Successful Operation

201

Created

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

409

Conflict

415

Unsupported Media Type

500

Internal Server Error

post/api/data/contactListHeaders
Request samples
application/json
{
  • "comment": "string",
  • "description": "string",
  • "includeOnlyCommonItemsFlag": true,
  • "contactListDetails": [
    ],
  • "contactListXrefs": [
    ]
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Get a single Contact List

Read the data for a specific Contact List.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
getWarnings
boolean

When you specify this parameter, warning validation messages are returned.

autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Responses
200

Successful Operation

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

get/api/data/contactListHeaders/{guid}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Delete a Contact List

Delete a specific Contact List.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Responses
200

OK

403

Forbidden

405

Method Not Allowed

409

Conflict

500

Internal Server Error

delete/api/data/contactListHeaders/{guid}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Update a Contact List

Update the data for a specific Contact List.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

The request body that you submit should include all of the properties that you want to update. When you want to update a Child Data Item or Cross-Reference Item, you must specify a value for the _action subproperty. The following actions are available for Child Data Items:

· add - specify this action when you want to add a new Item.

· delete - specify this action when you want to delete an Item.

· update - specify this action when you want to update data for an Item.

The following actions are available for Cross-Reference Items:

· add - specify this action when you want to add a Cross-Reference Item.

· update - specify this action when you want to update data for a Cross-Reference Item.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

Note: When you submit a request to add or delete Child or Cross-reference Items, the request is not idempotent. When you specify an _action value for a Child or Cross-reference Item, the action supercedes the behaviour indicated by the HTTP verb for the Child or Cross-reference Item. In this scenario, the request is similar to an HTTP PATCH request.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
forceTimestampValidation
boolean

Use the forceTimestampValidation parameter to validate the Timestamp for the Items that you want to update. When you use this parameter, you must include the following in the request body:

  • Timestamp properties that correspond to the Timestamp properties for all of the data Items (root and Child) that you want to update. When the _timestamp property is missing in the request body for any of the data Items, a 409 (Conflict) error response is returned.

  • Values for the Timestamp properties that correspond to the Timestamp values for the Items in Alliant. When the Timestamp values do not match, this endpoint returns a 409 (Conflict) error response.

autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Request Body schema: application/json
required

Specify the changes that you want to make to the Contact List

comment
string (Comment) <= 1000 characters

Specify any additional information for the List, when applicable. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

description
required
string (description) [ 1 .. 255 ] characters

Specify the unique “name” of the List. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

includeOnlyCommonItemsFlag
boolean (Flag)

Specify whether to include only the Items that are common to all of the Lists and Items that are specified in the Lists and the Items collections.

Array of objects (List Item Details PUT Request Properties)

Contact List Items. Include the guid of the List Item that you want to update or delete when updating the List Details Child Collection.

Array of objects (List List Details PUT Request Properties)

Contact List Lists. Include the guid of the List List that you want to update or delete when updating the List List Cross-reference Collection.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

409

Conflict

415

Unsupported Media Type

500

Internal Server Error

put/api/data/contactListHeaders/{guid}
Request samples
application/json
{
  • "comment": "string",
  • "description": "string",
  • "includeOnlyCommonItemsFlag": true,
  • "contactListDetails": [
    ],
  • "contactListXrefs": [
    ]
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Update a Contact List

Update the data for a specific Contact List.

A Contact List identifies a dynamic set of Contacts and Contact Lists. You create a Contact List by including and excluding specific Contacts and Contact Lists. Currently, you can use Contact Lists only for Internet Delivery purposes.

The request body that you submit should include all of the properties that you want to update. When you want to update a Child Data Item or Cross-Reference Item, you must specify a value for the _action subproperty. The following actions are available for Child Data Items:

· add - specify this action when you want to add a new Item.

· delete - specify this action when you want to delete an Item.

· update - specify this action when you want to update data for an Item.

The following actions are available for Cross-Reference Items:

· add - specify this action when you want to add a Cross-Reference Item.

· update - specify this action when you want to update data for a Cross-Reference Item.

Note: The List Details that you access in Alliant API reflect the List definition and not the resolved set of Items and Lists ultimately defined by the List.

Note: As well as partial updates, it is possible to use an _action to add or delete records. When there is an _action included within the body, then this action supercedes the behaviour indicated by the HTTP verb.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
forceTimestampValidation
boolean

Use the forceTimestampValidation parameter to validate the Timestamp for the Items that you want to update. When you use this parameter, you must include the following in the request body:

  • Timestamp properties that correspond to the Timestamp properties for all of the data Items (root and Child) that you want to update. When the _timestamp property is missing in the request body for any of the data Items, a 409 (Conflict) error response is returned.

  • Values for the Timestamp properties that correspond to the Timestamp values for the Items in Alliant. When the Timestamp values do not match, this endpoint returns a 409 (Conflict) error response.

autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Request Body schema: application/json
required

Specify the changes that you want to make to the Contact List

comment
string (Comment) <= 1000 characters

Specify any additional information for the List, when applicable. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

description
required
string (description) [ 1 .. 255 ] characters

Specify the unique “name” of the List. This property is ignored when getOrCreateWithHashCategory query parameter is specified and an existing List is returned.

includeOnlyCommonItemsFlag
boolean (Flag)

Specify whether to include only the Items that are common to all of the Lists and Items that are specified in the Lists and the Items collections.

Array of objects (List Item Details PUT Request Properties)

Contact List Items. Include the guid of the List Item that you want to update or delete when updating the List Details Child Collection.

Array of objects (List List Details PUT Request Properties)

Contact List Lists. Include the guid of the List List that you want to update or delete when updating the List List Cross-reference Collection.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

409

Conflict

415

Unsupported Media Type

500

Internal Server Error

patch/api/data/contactListHeaders/{guid}
Request samples
application/json
{
  • "comment": "string",
  • "description": "string",
  • "includeOnlyCommonItemsFlag": true,
  • "contactListDetails": [
    ],
  • "contactListXrefs": [
    ]
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Copy an existing Contact List

Copy a specific Contact List.

This PUT does not behave as a standard HTTP PUT and is NOT idempotent. This PUT will create a new resource. Its behaviour is that of a POST and it should be treated as such.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
minimal
boolean

When you specify this Verbosity parameter, the _timestamp, _type, displayName, and guid properties are returned.

default
boolean

Use this Verbosity parameter option when you want Alliant API to return a response that includes all properties for the Item, including UD Fields. This is the default option that is used when no Verbosity parameter is provided.

verbose
boolean

Use this Verbosity parameter option when you want Alliant API to return UD Field Lookups, Adjustments on Tab, Child Collection, and Cross-Reference properties in addition to the properties from the default Verbosity level.

Note: Using this parameter may affect performance and should only be used when necessary.

include
string

Use this Verbosity parameter to specify the properties to include in the response, separated by commas. You can also specify that you want to include Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields in the response. When you set the Verbosity of the response to minimal or default, Items only display as much information as the Verbosity parameter allows. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to return additional Child properties.

Note: When the values specified in the include parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes property1, childItem1 child collection, childProperty2 of childItem2 collection, udLookup_UDField1 UD Field lookup collection.
include=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
exclude
string

Use this Verbosity parameter to specify the properties to exclude from the response, separated by commas. You can also specify that you want to exclude Adjustments on Tab, Cross-Reference data Items, Child Items, and Child fields from the response. You can use the ChildDataItem.ChildPropertyName syntax to specify when you want to exclude specific Child properties.

Note: When the values specified in the exclude parameter are not valid, the query parameter is ignored and a warning is added to warnings property of the Standard Response.

Examples:
response includes all properies according to Verbosity parameter, except for property1, childItem1 collection, childProperty2 of childItem2 collection, and udLookup_UDField1 UD Field lookup collection.
exclude=property1,childItem1,childItem2.childProperty2,udLookup_UDField1
contextReplace
string

Use this parameter to specify the properties with context replaced values in the response, separated by commas. You can also specify that you want to context replace values for all properties by specifying all.

Note: When the values specified in the contextReplace parameter are not valid, the query parameter is ignored.

Examples:
displayName and ud_UDField1 properties in the response have context replaced values.
contextReplace=displayName,ud_UDField1
All properties in the response have context replaced values.
contextReplace=all
getWarnings
boolean

When you specify this parameter, warning validation messages are returned.

autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Responses
200

Successful Operation

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

put/api/data/contactListHeaders/copy/{guid}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Execute the Resolve Tool for an existing Contact List

Execute the Resolve Tool on an existing Contact List.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact List Unique Identity

query Parameters
autoLogOff
boolean

Use the autoLogOff parameter to log off Alliant API, discard the Alliant session Security Token, and release the Alliant license currently in use by Alliant API once the request completes.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

put/api/data/contactListHeaders/resolve/{guid}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}