Visit Rightsline
logo
Powered by Redocly

Contacts

Get multiple Contacts

Read the data for multiple Contacts.

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

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
downloadAttachments
boolean

Use the downloadAttachments parameter to include Attachment data in the response. You must include either the verbose parameter or the include={ItemType}Attachments parameter when you want to include Attachment data in the response. Attachment data is returned in the _data property in base64 encoded format. When you do not include the downloadAttachments parameter but you include the verbose parameter or the include={ItemType}Attachments parameter, you can use the value in the the _downloadUrl properties to download Attachments directly.

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/contacts
Response samples
application/json
{
  • "result": {
    },
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Create a new Contact

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

When you want to create a Contact with Recipient Groups, if you simply want to default the contact to be its own recipient as part of your POST, simply include:

  "contactRecipientGroups": [
  {
      "_action": "add",
      "contactRecipientGroupDetails": [
      {
          "_action": "add"
      }
     ]
  }
  ],
  "contactAddresses": [
   {
      "_action": "add",
      "addressTypeReference": {
          "displayName": "Business"
      },
      "countryReference": {
          "displayName": "United States of America"
      },
      "stateReference": {
          "displayName": "Iowa"
       },   
       "city": "1",
       "postalCode": "1"                            
      }
  ] 
}

When you want to create a Contact with a linked Adjustment, you must first submit a POST Request to create the Contact. You must then submit a PUT or PATCH Request to update the Contact with the Adjustment information.

The id and sortByName properties are required. The formattedName property is also required; however, when any of following properties are provided, Alliant API generates a value the formattedName property when it is not provided: firstName, lastName, middleName, namePrefix, nameSuffix, or companyName.

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
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

ID (object) or description (object) or SID (object) or GUID (object) (Admin Class)

Specify the Admin Class for the Contact.

comment
string (Comment) <= 1000 characters

Specify the Comment for the Contact, when applicable.

companyName
string <= 60 characters

Specify the Company Name for the Contact, when applicable.

Array of objects (Contact Physical Addresses Child Collection Request)

Contact Physical Addresses

Array of objects (Attachments Child Collection Request)

Contact Attachments

Array of objects (Contact Delivery Groups Child Collection Request)

Contact Delivery Groups

Array of objects (Contact E-mail Addresses Child Collection Request)

Contact E-mail Addresses

Array of objects (Contact File System Addresses Child Collection Request)

Contact File System Addresses. The required properties vary based on the _action that you are performing and the specified transferTypeReference value.

Array of objects (Keywords Child Collection Request)

Contact Keywords

Array of objects (Links Child Collection Request)

Contact Links

Array of objects (Notes Child Collection Request)

Contact Notes

Array of objects (Reminders Child Collection Request)

Contact Reminders. The required properties vary based on the _action that you are performing and the values that you specify.

ID (object) or description (object) or SID (object) or GUID (object) (Reference)

Specify the Contact Type for the Contact.

firstName
string <= 60 characters

Specify the first name for the Contact.

formattedName
required
string [ 1 .. 255 ] characters

Specify the Full Name for the Contact. The Full Name contains the text you entered in the Prefix, First Name, Middle Name, Last Name, Suffix, and Company Name fields, in that order.

hasFileSystemAddressFlag
boolean (Flag)

Specify whether the Contact can have File System Addresses.

holdDeliveryFlag
boolean (Flag)

Specify whether to hold Deliveries for this Contact.

id
required
string (ID) [ 1 .. 60 ] characters unique

Specify the unique system ID for the Contact.

lastName
string <= 60 characters

Specify the last name for the Contact.

middleName
string <= 60 characters

Specify the middle name for the Contact.

namePrefix
string <= 20 characters

Specify the prefix for the Contact.

nameSuffix
string <= 15 characters

Specify the suffix for the Contact.

participantFlag
boolean (Flag)

Specify whether the Contact is a Participant. Only those Contacts that are specified as Participants are available for selection as a Participant for a Contract.

sortByName
required
string [ 1 .. 255 ] characters

Specify the Sort By Name for the Contact. The Sort By Name contains the text you entered in the Last Name, Prefix, First Name, Middle Name, Suffix, and Company Name fields, in that order.

ud_userDefinedStringField
string (ud_userDefinedStringField_Request)

Specify values for the single-value string UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''title'''', the UD Field property name in the collection is ud_title. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ud_userDefinedNumberField
number (ud_userDefinedNumberField_Request)

Specify values for the single-value numerical UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''weighting'''', the UD Field property name in the collection is ud_weighting. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ID (string) or description (string) or SID (number) or GUID (string) (ud_userDefinedReferenceRequest)

Single-value Reference UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with ud_ and suffixed with Reference (for example, when the UD Field name is ''''territory'''', the UD Field property name in the collection is ud_territoryReference. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item. Define the reference using an ID, Description, SID, or GUID value.

object (udLookup_LookupUDFieldRequest)

When you send a POST or PUT request for an Item that includes a Lookup UD Field and you want to modify the Lookup UD Field data, use the _action property to specify whether to add, update, or delete the corresponding Child Collection data. The properties shown below are examples of the properties that can be sent. The actual set of properties necessary varies based on the configuration on the Lookup UD Field and the data that you want to add, update, or delete. Lookup UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with udLookup_. For example, when the Lookup UD Field name is tiers, the Lookup UD Field property name in the collection is udLookup_tiers. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item.

Array of objects (Contact Recipient Groups Child Collection POST Request)

Contact Recipient Groups

When you want to create a Contact with Recipient Groups, you must first submit a POST Request to create the Contact with the Recipient Groups, but without Recipient Group Details. You must then submit a PUT or PATCH Request to update the Recipient Groups with the necessary Recipient Group Details.

Responses
201

Created

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

409

Conflict

500

Internal Server Error

post/api/data/contacts
Request samples
application/json
{
  • "comment": "New Contact",
  • "companyName": "RST",
  • "contactAddresses": [
    ],
  • "contactDeliveryGroups": [
    ],
  • "contactRecipientGroups": [
    ],
  • "contactTypeReference": {
    },
  • "firstName": "New",
  • "formattedName": "Test, New Contact",
  • "hasFileSystemAddressFlag": false,
  • "holdDeliveryFlag": false,
  • "id": "NewContactCreatedByAPI",
  • "isAlliantUserFlag": false,
  • "lastName": "Test",
  • "middleName": "Contact",
  • "participantFlag": true,
  • "sortByName": "Test, New Contact"
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Get a single Contact

Read the data for a specific Contact.

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact Unique Identity

query Parameters
downloadAttachments
boolean

Use the downloadAttachments parameter to include Attachment data in the response. You must include either the verbose parameter or the include={ItemType}Attachments parameter when you want to include Attachment data in the response. Attachment data is returned in the _data property in base64 encoded format. When you do not include the downloadAttachments parameter but you include the verbose parameter or the include={ItemType}Attachments parameter, you can use the value in the the _downloadUrl properties to download Attachments directly.

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/contacts/{guid}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Delete a Contact

Delete a specific Contact.

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact 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/contacts/{guid}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Update a Contact

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

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

· 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.

When you want to create a Contact with a linked Adjustment, you must first submit a POST Request to create the Contact. You must then submit a PUT or PATCH Request to update the Contact with the Adjustment information.

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 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

Include as much information as possible regarding the Contact

ID (object) or description (object) or SID (object) or GUID (object) (Admin Class)

Specify the Admin Class for the Contact.

comment
string (Comment) <= 1000 characters

Specify the Comment for the Contact, when applicable.

companyName
string <= 60 characters

Specify the Company Name for the Contact, when applicable.

Array of objects (Contact Physical Addresses Child Collection Request)

Contact Physical Addresses

Array of objects (Attachments Child Collection Request)

Contact Attachments

Array of objects (Contact Delivery Groups Child Collection Request)

Contact Delivery Groups

Array of objects (Contact E-mail Addresses Child Collection Request)

Contact E-mail Addresses

Array of objects (Contact File System Addresses Child Collection Request)

Contact File System Addresses. The required properties vary based on the _action that you are performing and the specified transferTypeReference value.

Array of objects (Keywords Child Collection Request)

Contact Keywords

Array of objects (Links Child Collection Request)

Contact Links

Array of objects (Notes Child Collection Request)

Contact Notes

Array of objects (Reminders Child Collection Request)

Contact Reminders. The required properties vary based on the _action that you are performing and the values that you specify.

ID (object) or description (object) or SID (object) or GUID (object) (Reference)

Specify the Contact Type for the Contact.

firstName
string <= 60 characters

Specify the first name for the Contact.

formattedName
string [ 1 .. 255 ] characters

Specify the Full Name for the Contact. The Full Name contains the text you entered in the Prefix, First Name, Middle Name, Last Name, Suffix, and Company Name fields, in that order.

hasFileSystemAddressFlag
boolean (Flag)

Specify whether the Contact can have File System Addresses.

holdDeliveryFlag
boolean (Flag)

Specify whether to hold Deliveries for this Contact.

id
string (ID) [ 1 .. 60 ] characters unique

Specify the unique system ID for the Contact.

lastName
string <= 60 characters

Specify the last name for the Contact.

middleName
string <= 60 characters

Specify the middle name for the Contact.

namePrefix
string <= 20 characters

Specify the prefix for the Contact.

nameSuffix
string <= 15 characters

Specify the suffix for the Contact.

participantFlag
boolean (Flag)

Specify whether the Contact is a Participant. Only those Contacts that are specified as Participants are available for selection as a Participant for a Contract.

sortByName
string [ 1 .. 255 ] characters

Specify the Sort By Name for the Contact. The Sort By Name contains the text you entered in the Last Name, Prefix, First Name, Middle Name, Suffix, and Company Name fields, in that order.

ud_userDefinedStringField
string (ud_userDefinedStringField_Request)

Specify values for the single-value string UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''title'''', the UD Field property name in the collection is ud_title. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ud_userDefinedNumberField
number (ud_userDefinedNumberField_Request)

Specify values for the single-value numerical UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''weighting'''', the UD Field property name in the collection is ud_weighting. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ID (string) or description (string) or SID (number) or GUID (string) (ud_userDefinedReferenceRequest)

Single-value Reference UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with ud_ and suffixed with Reference (for example, when the UD Field name is ''''territory'''', the UD Field property name in the collection is ud_territoryReference. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item. Define the reference using an ID, Description, SID, or GUID value.

object (udLookup_LookupUDFieldRequest)

When you send a POST or PUT request for an Item that includes a Lookup UD Field and you want to modify the Lookup UD Field data, use the _action property to specify whether to add, update, or delete the corresponding Child Collection data. The properties shown below are examples of the properties that can be sent. The actual set of properties necessary varies based on the configuration on the Lookup UD Field and the data that you want to add, update, or delete. Lookup UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with udLookup_. For example, when the Lookup UD Field name is tiers, the Lookup UD Field property name in the collection is udLookup_tiers. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item.

Array of objects (Contact Recipient Groups Child Collection PUT Request)

Contact Recipient Groups

When you want to create a Contact with Recipient Groups, you must first submit a POST Request to create the Contact with the Recipient Groups, but without Recipient Group Details. You must then submit a PUT or PATCH Request to update the Recipient Groups with the necessary Recipient Group Details.

Array of objects (Adjustment Cross-reference Request Properties)

Contact Adjustments

When you want to create a Contact with a linked Adjustment, you must first submit a POST Request to create the Contact. You must then submit a PUT or PATCH Request to update the Contact with the Adjustment information. The required properties vary based on the _action that you are performing and the values that you specify.

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/contacts/{guid}
Request samples
application/json
{
  • "adminClassReference": {
    },
  • "comment": "Client Contact",
  • "companyName": "Rightsline",
  • "contactTypeReference": {
    },
  • "displayName": "John Holder",
  • "firstName": "John",
  • "formattedName": "John Holder",
  • "hasFileSystemAddressFlag": false,
  • "holdDeliveryFlag": false,
  • "id": "JHolder",
  • "isAlliantUserFlag": false,
  • "lastName": "Holder",
  • "middleName": "Anthony",
  • "namePrefix": "Mr.",
  • "participantFlag": true,
  • "sortByName": "Holder, John"
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Update a Contact

Update the data for a specific Contact.

A Contact is an individual or business for which you want to maintain information in the Alliant system. A Contact can represent a Participant or Recipient in a Contract, can be associated with a Participant in a Contract, can represent a guild, and so forth. For example, you can set up a Contact that represents the accountant for a Participant, and add this Contact as a Statement Recipient to the Recipient Group for the Participant in a Contract. You can use the Alliant system to maintain information regarding Contact names, addresses, company names, and so forth.

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

· 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.

When you want to create a Contact with Recipient Groups, you must first submit a POST Request to create the Contact with the Recipient Groups, but without Recipient Group Details. You must then submit a PUT or PATCH Request to update the Recipient Groups with the necessary Recipient Group Details.

When you want to create a Contact with a linked Adjustment, you must first submit a POST Request to create the Contact. You must then submit a PUT or PATCH Request to update the Contact with the Adjustment information.

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 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

Include as much information as possible regarding the Contact

ID (object) or description (object) or SID (object) or GUID (object) (Admin Class)

Specify the Admin Class for the Contact.

comment
string (Comment) <= 1000 characters

Specify the Comment for the Contact, when applicable.

companyName
string <= 60 characters

Specify the Company Name for the Contact, when applicable.

Array of objects (Contact Physical Addresses Child Collection Request)

Contact Physical Addresses

Array of objects (Attachments Child Collection Request)

Contact Attachments

Array of objects (Contact Delivery Groups Child Collection Request)

Contact Delivery Groups

Array of objects (Contact E-mail Addresses Child Collection Request)

Contact E-mail Addresses

Array of objects (Contact File System Addresses Child Collection Request)

Contact File System Addresses. The required properties vary based on the _action that you are performing and the specified transferTypeReference value.

Array of objects (Keywords Child Collection Request)

Contact Keywords

Array of objects (Links Child Collection Request)

Contact Links

Array of objects (Notes Child Collection Request)

Contact Notes

Array of objects (Reminders Child Collection Request)

Contact Reminders. The required properties vary based on the _action that you are performing and the values that you specify.

ID (object) or description (object) or SID (object) or GUID (object) (Reference)

Specify the Contact Type for the Contact.

firstName
string <= 60 characters

Specify the first name for the Contact.

formattedName
string [ 1 .. 255 ] characters

Specify the Full Name for the Contact. The Full Name contains the text you entered in the Prefix, First Name, Middle Name, Last Name, Suffix, and Company Name fields, in that order.

hasFileSystemAddressFlag
boolean (Flag)

Specify whether the Contact can have File System Addresses.

holdDeliveryFlag
boolean (Flag)

Specify whether to hold Deliveries for this Contact.

id
string (ID) [ 1 .. 60 ] characters unique

Specify the unique system ID for the Contact.

lastName
string <= 60 characters

Specify the last name for the Contact.

middleName
string <= 60 characters

Specify the middle name for the Contact.

namePrefix
string <= 20 characters

Specify the prefix for the Contact.

nameSuffix
string <= 15 characters

Specify the suffix for the Contact.

participantFlag
boolean (Flag)

Specify whether the Contact is a Participant. Only those Contacts that are specified as Participants are available for selection as a Participant for a Contract.

sortByName
string [ 1 .. 255 ] characters

Specify the Sort By Name for the Contact. The Sort By Name contains the text you entered in the Last Name, Prefix, First Name, Middle Name, Suffix, and Company Name fields, in that order.

ud_userDefinedStringField
string (ud_userDefinedStringField_Request)

Specify values for the single-value string UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''title'''', the UD Field property name in the collection is ud_title. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ud_userDefinedNumberField
number (ud_userDefinedNumberField_Request)

Specify values for the single-value numerical UD Fields for the Item, when applicable. These UD Fields use the name of the UD Field prefixed with ud_ (for example, when the UD Field name is ''''weighting'''', the UD Field property name in the collection is ud_weighting. The UD Fields associated with the Item depend on the configuration, including the Admin Class and the data populated for the Item.

ID (string) or description (string) or SID (number) or GUID (string) (ud_userDefinedReferenceRequest)

Single-value Reference UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with ud_ and suffixed with Reference (for example, when the UD Field name is ''''territory'''', the UD Field property name in the collection is ud_territoryReference. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item. Define the reference using an ID, Description, SID, or GUID value.

object (udLookup_LookupUDFieldRequest)

When you send a POST or PUT request for an Item that includes a Lookup UD Field and you want to modify the Lookup UD Field data, use the _action property to specify whether to add, update, or delete the corresponding Child Collection data. The properties shown below are examples of the properties that can be sent. The actual set of properties necessary varies based on the configuration on the Lookup UD Field and the data that you want to add, update, or delete. Lookup UD Fields for an Item are included in the collection with the Name of the UD Field prefixed with udLookup_. For example, when the Lookup UD Field name is tiers, the Lookup UD Field property name in the collection is udLookup_tiers. The UD Fields included depend on the configuration, including the Admin Class and the data populated for the Item.

Array of objects (Contact Recipient Groups Child Collection PUT Request)

Contact Recipient Groups

When you want to create a Contact with Recipient Groups, you must first submit a POST Request to create the Contact with the Recipient Groups, but without Recipient Group Details. You must then submit a PUT or PATCH Request to update the Recipient Groups with the necessary Recipient Group Details.

Array of objects (Adjustment Cross-reference Request Properties)

Contact Adjustments

When you want to create a Contact with a linked Adjustment, you must first submit a POST Request to create the Contact. You must then submit a PUT or PATCH Request to update the Contact with the Adjustment information. The required properties vary based on the _action that you are performing and the values that you specify.

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/contacts/{guid}
Request samples
application/json
{
  • "adminClassReference": {
    },
  • "comment": "Client Contact",
  • "companyName": "Rightsline",
  • "contactTypeReference": {
    },
  • "displayName": "John Holder",
  • "firstName": "John",
  • "formattedName": "John Holder",
  • "hasFileSystemAddressFlag": false,
  • "holdDeliveryFlag": false,
  • "id": "JHolder",
  • "isAlliantUserFlag": false,
  • "lastName": "Holder",
  • "middleName": "Anthony",
  • "namePrefix": "Mr.",
  • "participantFlag": true,
  • "sortByName": "Holder, John"
}
Response samples
application/json
{
  • "result": {
    },
  • "errors": [
    ],
  • "warnings": [
    ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Copy an existing Contact

Copy a specific Contact.

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 Unique Identity

query Parameters
downloadAttachments
boolean

Use the downloadAttachments parameter to include Attachment data in the response. You must include either the verbose parameter or the include={ItemType}Attachments parameter when you want to include Attachment data in the response. Attachment data is returned in the _data property in base64 encoded format. When you do not include the downloadAttachments parameter but you include the verbose parameter or the include={ItemType}Attachments parameter, you can use the value in the the _downloadUrl properties to download Attachments directly.

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.

Request Body schema: application/json
copyAdjustments
boolean (Flag)

Copy Attached Adjustments on Tab

copyNotes
boolean (Flag)

Copy All Notes, Attachments, and Links

Responses
200

Successful Operation

403

Forbidden

404

Not Found

405

Method Not Allowed

415

Unsupported Media Type

500

Internal Server Error

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

Use the In Use Tool on a Contact

Use the In Use Tool on a Contact.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact 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/contacts/inUse/{guid}
Response samples
application/json
{
  • "result": [
    ],
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Execute the Resolve Tool on an existing Contact

Execute the Resolve Tool on an existing Contact.

Note: You must enable at least one of the Resolve Types.

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact 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.

Request Body schema: application/json
verifyFlag
boolean (Flag)

Submits a Contact Verify request.

lookupSQLFlag
boolean (Flag)

Submits a Lookup resolution request.

dateReferenceFlag
boolean (Flag)

Submits a Date UD Field resolution request.

udfCopyFlag
boolean (Flag)

Submits a UD Field Copy resolution request.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

put/api/data/contacts/resolve/{guid}
Request samples
application/json
{
  • "verifyFlag": true,
  • "lookupSQLFlag": true,
  • "dateReferenceFlag": true,
  • "udfCopyFlag": true
}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Verify an existing Contact

Verify an existing Contact

SecurityHeaderToken
Request
path Parameters
guid
required
string

Contact 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.

Request Body schema: application/json
forceResolve
boolean (Flag)

Specify whether you want the system to process the Verify Requests and verify the Contacts regardless of whether the Contacts are already verified.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

put/api/data/contacts/verify/{guid}
Request samples
application/json
{
  • "forceResolve": true
}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}

Verify all Contacts

Verify all existing Contacts.

SecurityHeaderToken
Request
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.

Request Body schema: application/json
forceResolve
boolean (Flag)

Specify whether you want the system to process the Verify Requests and verify the Contacts regardless of whether the Contacts are already verified.

Responses
200

OK

400

Bad Request

403

Forbidden

404

Not Found

405

Method Not Allowed

500

Internal Server Error

put/api/data/contacts/verifyAll
Request samples
application/json
{
  • "forceResolve": true
}
Response samples
application/json
{
  • "result": null,
  • "errors": [ ],
  • "warnings": [ ],
  • "hasErrors": false,
  • "hasWarnings": false
}
➔ Next to Contact Lists