|
249 | 249 | {"shape":"ThrottlingException"},
|
250 | 250 | {"shape":"InternalServerException"}
|
251 | 251 | ],
|
252 |
| - "documentation":"<p>This API is in preview release for Amazon Connect and subject to change.</p> <p>Before calling this API, use <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_CreateDomain.html\">CreateDomain</a> or <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_UpdateDomain.html\">UpdateDomain</a> to enable identity resolution: set <code>Matching</code> to true.</p> <p>GetMatches returns potentially matching profiles, based on the results of the latest run of a machine learning process. </p> <important> <p>The process of matching duplicate profiles. If <code>Matching</code> = <code>true</code>, Amazon Connect Customer Profiles starts a weekly batch process called Identity Resolution Job. If you do not specify a date and time for Identity Resolution Job to run, by default it runs every Saturday at 12AM UTC to detect duplicate profiles in your domains. </p> <p>After the Identity Resolution Job completes, use the <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_GetMatches.html\">GetMatches</a> API to return and review the results. Or, if you have configured <code>ExportingConfig</code> in the <code>MatchingRequest</code>, you can download the results from S3.</p> </important> <p>Amazon Connect uses the following profile attributes to identify matches:</p> <ul> <li> <p>PhoneNumber</p> </li> <li> <p>HomePhoneNumber</p> </li> <li> <p>BusinessPhoneNumber</p> </li> <li> <p>MobilePhoneNumber</p> </li> <li> <p>EmailAddress</p> </li> <li> <p>PersonalEmailAddress</p> </li> <li> <p>BusinessEmailAddress</p> </li> <li> <p>FullName</p> </li> <li> <p>BusinessName</p> </li> </ul> <p>For example, two or more profiles—with spelling mistakes such as <b>John Doe</b> and <b>Jhn Doe</b>, or different casing email addresses such as <b>JOHN_DOE@ANYCOMPANY.COM</b> and <b>johndoe@anycompany.com</b>, or different phone number formats such as <b>555-010-0000</b> and <b>+1-555-010-0000</b>—can be detected as belonging to the same customer <b>John Doe</b> and merged into a unified profile.</p>" |
| 252 | + "documentation":"<p>Before calling this API, use <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_CreateDomain.html\">CreateDomain</a> or <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_UpdateDomain.html\">UpdateDomain</a> to enable identity resolution: set <code>Matching</code> to true.</p> <p>GetMatches returns potentially matching profiles, based on the results of the latest run of a machine learning process. </p> <important> <p>The process of matching duplicate profiles. If <code>Matching</code> = <code>true</code>, Amazon Connect Customer Profiles starts a weekly batch process called Identity Resolution Job. If you do not specify a date and time for Identity Resolution Job to run, by default it runs every Saturday at 12AM UTC to detect duplicate profiles in your domains. </p> <p>After the Identity Resolution Job completes, use the <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_GetMatches.html\">GetMatches</a> API to return and review the results. Or, if you have configured <code>ExportingConfig</code> in the <code>MatchingRequest</code>, you can download the results from S3.</p> </important> <p>Amazon Connect uses the following profile attributes to identify matches:</p> <ul> <li> <p>PhoneNumber</p> </li> <li> <p>HomePhoneNumber</p> </li> <li> <p>BusinessPhoneNumber</p> </li> <li> <p>MobilePhoneNumber</p> </li> <li> <p>EmailAddress</p> </li> <li> <p>PersonalEmailAddress</p> </li> <li> <p>BusinessEmailAddress</p> </li> <li> <p>FullName</p> </li> <li> <p>BusinessName</p> </li> </ul> <p>For example, two or more profiles—with spelling mistakes such as <b>John Doe</b> and <b>Jhn Doe</b>, or different casing email addresses such as <b>JOHN_DOE@ANYCOMPANY.COM</b> and <b>johndoe@anycompany.com</b>, or different phone number formats such as <b>555-010-0000</b> and <b>+1-555-010-0000</b>—can be detected as belonging to the same customer <b>John Doe</b> and merged into a unified profile.</p>" |
253 | 253 | },
|
254 | 254 | "GetProfileObjectType":{
|
255 | 255 | "name":"GetProfileObjectType",
|
|
433 | 433 | {"shape":"ThrottlingException"},
|
434 | 434 | {"shape":"InternalServerException"}
|
435 | 435 | ],
|
436 |
| - "documentation":"<p>This API is in preview release for Amazon Connect and subject to change.</p> <p>Runs an AWS Lambda job that does the following:</p> <ol> <li> <p>All the profileKeys in the <code>ProfileToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>All the objects in the <code>ProfileToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>All the <code>ProfileToBeMerged</code> will be deleted at the end.</p> </li> <li> <p>All the profileKeys in the <code>ProfileIdsToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>Standard fields are merged as follows:</p> <ol> <li> <p>Fields are always \"union\"-ed if there are no conflicts in standard fields or attributeKeys.</p> </li> <li> <p>When there are conflicting fields:</p> <ol> <li> <p>If no <code>SourceProfileIds</code> entry is specified, the main Profile value is always taken. </p> </li> <li> <p>If a <code>SourceProfileIds</code> entry is specified, the specified profileId is always taken, even if it is a NULL value.</p> </li> </ol> </li> </ol> </li> </ol> <p>You can use MergeProfiles together with <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_GetMatches.html\">GetMatches</a>, which returns potentially matching profiles, or use it with the results of another matching system. After profiles have been merged, they cannot be separated (unmerged).</p>" |
| 436 | + "documentation":"<p>Runs an AWS Lambda job that does the following:</p> <ol> <li> <p>All the profileKeys in the <code>ProfileToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>All the objects in the <code>ProfileToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>All the <code>ProfileToBeMerged</code> will be deleted at the end.</p> </li> <li> <p>All the profileKeys in the <code>ProfileIdsToBeMerged</code> will be moved to the main profile.</p> </li> <li> <p>Standard fields are merged as follows:</p> <ol> <li> <p>Fields are always \"union\"-ed if there are no conflicts in standard fields or attributeKeys.</p> </li> <li> <p>When there are conflicting fields:</p> <ol> <li> <p>If no <code>SourceProfileIds</code> entry is specified, the main Profile value is always taken. </p> </li> <li> <p>If a <code>SourceProfileIds</code> entry is specified, the specified profileId is always taken, even if it is a NULL value.</p> </li> </ol> </li> </ol> </li> </ol> <p>You can use MergeProfiles together with <a href=\"https://docs.aws.amazon.com/customerprofiles/latest/APIReference/API_GetMatches.html\">GetMatches</a>, which returns potentially matching profiles, or use it with the results of another matching system. After profiles have been merged, they cannot be separated (unmerged).</p>" |
437 | 437 | },
|
438 | 438 | "PutIntegration":{
|
439 | 439 | "name":"PutIntegration",
|
|
1582 | 1582 | "required":[
|
1583 | 1583 | "DomainName",
|
1584 | 1584 | "Uri",
|
1585 |
| - "ObjectTypeName", |
1586 | 1585 | "CreatedAt",
|
1587 | 1586 | "LastUpdatedAt"
|
1588 | 1587 | ],
|
|
1610 | 1609 | "Tags":{
|
1611 | 1610 | "shape":"TagMap",
|
1612 | 1611 | "documentation":"<p>The tags used to organize, track, or control access for this resource.</p>"
|
| 1612 | + }, |
| 1613 | + "ObjectTypeNames":{ |
| 1614 | + "shape":"ObjectTypeNames", |
| 1615 | + "documentation":"<p>A map in which each key is an event type from an external application such as Segment or Shopify, and each value is an <code>ObjectTypeName</code> (template) used to ingest the event. It supports the following event types: <code>SegmentIdentify</code>, <code>ShopifyCreateCustomers</code>, <code>ShopifyUpdateCustomers</code>, <code>ShopifyCreateDraftOrders</code>, <code>ShopifyUpdateDraftOrders</code>, <code>ShopifyCreateOrders</code>, and <code>ShopifyUpdatedOrders</code>.</p>" |
1613 | 1616 | }
|
1614 | 1617 | }
|
1615 | 1618 | },
|
|
2058 | 2061 | "required":[
|
2059 | 2062 | "DomainName",
|
2060 | 2063 | "Uri",
|
2061 |
| - "ObjectTypeName", |
2062 | 2064 | "CreatedAt",
|
2063 | 2065 | "LastUpdatedAt"
|
2064 | 2066 | ],
|
|
2086 | 2088 | "Tags":{
|
2087 | 2089 | "shape":"TagMap",
|
2088 | 2090 | "documentation":"<p>The tags used to organize, track, or control access for this resource.</p>"
|
| 2091 | + }, |
| 2092 | + "ObjectTypeNames":{ |
| 2093 | + "shape":"ObjectTypeNames", |
| 2094 | + "documentation":"<p>A map in which each key is an event type from an external application such as Segment or Shopify, and each value is an <code>ObjectTypeName</code> (template) used to ingest the event. It supports the following event types: <code>SegmentIdentify</code>, <code>ShopifyCreateCustomers</code>, <code>ShopifyUpdateCustomers</code>, <code>ShopifyCreateDraftOrders</code>, <code>ShopifyUpdateDraftOrders</code>, <code>ShopifyCreateOrders</code>, and <code>ShopifyUpdatedOrders</code>.</p>" |
2089 | 2095 | }
|
2090 | 2096 | },
|
2091 | 2097 | "documentation":"<p>An integration in list of integrations.</p>"
|
|
2296 | 2302 | },
|
2297 | 2303 | "ObjectFilter":{
|
2298 | 2304 | "shape":"ObjectFilter",
|
2299 |
| - "documentation":"<p>Applies a filter to the response to include profile objects with the specified index values. This filter is only supported for ObjectTypeName _asset and _case.</p>" |
| 2305 | + "documentation":"<p>Applies a filter to the response to include profile objects with the specified index values. This filter is only supported for ObjectTypeName _asset, _case and _order.</p>" |
2300 | 2306 | }
|
2301 | 2307 | }
|
2302 | 2308 | },
|
|
2496 | 2502 | "members":{
|
2497 | 2503 | "KeyName":{
|
2498 | 2504 | "shape":"name",
|
2499 |
| - "documentation":"<p>A searchable identifier of a standard profile object. The predefined keys you can use to search for _asset include: _assetId, _assetName, _serialNumber. The predefined keys you can use to search for _case include: _caseId.</p>" |
| 2505 | + "documentation":"<p>A searchable identifier of a standard profile object. The predefined keys you can use to search for _asset include: _assetId, _assetName, _serialNumber. The predefined keys you can use to search for _case include: _caseId. The predefined keys you can use to search for _order include: _orderId.</p>" |
2500 | 2506 | },
|
2501 | 2507 | "Values":{
|
2502 | 2508 | "shape":"requestValueList",
|
2503 | 2509 | "documentation":"<p>A list of key values.</p>"
|
2504 | 2510 | }
|
2505 | 2511 | },
|
2506 |
| - "documentation":"<p>The filter applied to ListProfileObjects response to include profile objects with the specified index values. This filter is only supported for ObjectTypeName _asset and _case.</p>" |
| 2512 | + "documentation":"<p>The filter applied to ListProfileObjects response to include profile objects with the specified index values. This filter is only supported for ObjectTypeName _asset, _case and _order.</p>" |
2507 | 2513 | },
|
2508 | 2514 | "ObjectTypeField":{
|
2509 | 2515 | "type":"structure",
|
|
2528 | 2534 | "members":{
|
2529 | 2535 | "StandardIdentifiers":{
|
2530 | 2536 | "shape":"StandardIdentifierList",
|
2531 |
| - "documentation":"<p>The types of keys that a ProfileObject can have. Each ProfileObject can have only 1 UNIQUE key but multiple PROFILE keys. PROFILE, ASSET or CASE means that this key can be used to tie an object to a PROFILE, ASSET or CASE respectively. UNIQUE means that it can be used to uniquely identify an object. If a key a is marked as SECONDARY, it will be used to search for profiles after all other PROFILE keys have been searched. A LOOKUP_ONLY key is only used to match a profile but is not persisted to be used for searching of the profile. A NEW_ONLY key is only used if the profile does not already exist before the object is ingested, otherwise it is only used for matching objects to profiles.</p>" |
| 2537 | + "documentation":"<p>The types of keys that a ProfileObject can have. Each ProfileObject can have only 1 UNIQUE key but multiple PROFILE keys. PROFILE, ASSET, CASE, or ORDER means that this key can be used to tie an object to a PROFILE, ASSET, CASE, or ORDER respectively. UNIQUE means that it can be used to uniquely identify an object. If a key a is marked as SECONDARY, it will be used to search for profiles after all other PROFILE keys have been searched. A LOOKUP_ONLY key is only used to match a profile but is not persisted to be used for searching of the profile. A NEW_ONLY key is only used if the profile does not already exist before the object is ingested, otherwise it is only used for matching objects to profiles.</p>" |
2532 | 2538 | },
|
2533 | 2539 | "FieldNames":{
|
2534 | 2540 | "shape":"FieldNameList",
|
|
2541 | 2547 | "type":"list",
|
2542 | 2548 | "member":{"shape":"ObjectTypeKey"}
|
2543 | 2549 | },
|
| 2550 | + "ObjectTypeNames":{ |
| 2551 | + "type":"map", |
| 2552 | + "key":{"shape":"string1To255"}, |
| 2553 | + "value":{"shape":"typeName"} |
| 2554 | + }, |
2544 | 2555 | "OperatorPropertiesKeys":{
|
2545 | 2556 | "type":"string",
|
2546 | 2557 | "enum":[
|
|
2695 | 2706 | },
|
2696 | 2707 | "PutIntegrationRequest":{
|
2697 | 2708 | "type":"structure",
|
2698 |
| - "required":[ |
2699 |
| - "DomainName", |
2700 |
| - "ObjectTypeName" |
2701 |
| - ], |
| 2709 | + "required":["DomainName"], |
2702 | 2710 | "members":{
|
2703 | 2711 | "DomainName":{
|
2704 | 2712 | "shape":"name",
|
|
2721 | 2729 | "FlowDefinition":{
|
2722 | 2730 | "shape":"FlowDefinition",
|
2723 | 2731 | "documentation":"<p>The configuration that controls how Customer Profiles retrieves data from the source.</p>"
|
| 2732 | + }, |
| 2733 | + "ObjectTypeNames":{ |
| 2734 | + "shape":"ObjectTypeNames", |
| 2735 | + "documentation":"<p>A map in which each key is an event type from an external application such as Segment or Shopify, and each value is an <code>ObjectTypeName</code> (template) used to ingest the event. It supports the following event types: <code>SegmentIdentify</code>, <code>ShopifyCreateCustomers</code>, <code>ShopifyUpdateCustomers</code>, <code>ShopifyCreateDraftOrders</code>, <code>ShopifyUpdateDraftOrders</code>, <code>ShopifyCreateOrders</code>, and <code>ShopifyUpdatedOrders</code>.</p>" |
2724 | 2736 | }
|
2725 | 2737 | }
|
2726 | 2738 | },
|
|
2729 | 2741 | "required":[
|
2730 | 2742 | "DomainName",
|
2731 | 2743 | "Uri",
|
2732 |
| - "ObjectTypeName", |
2733 | 2744 | "CreatedAt",
|
2734 | 2745 | "LastUpdatedAt"
|
2735 | 2746 | ],
|
|
2757 | 2768 | "Tags":{
|
2758 | 2769 | "shape":"TagMap",
|
2759 | 2770 | "documentation":"<p>The tags used to organize, track, or control access for this resource.</p>"
|
| 2771 | + }, |
| 2772 | + "ObjectTypeNames":{ |
| 2773 | + "shape":"ObjectTypeNames", |
| 2774 | + "documentation":"<p>A map in which each key is an event type from an external application such as Segment or Shopify, and each value is an <code>ObjectTypeName</code> (template) used to ingest the event. It supports the following event types: <code>SegmentIdentify</code>, <code>ShopifyCreateCustomers</code>, <code>ShopifyUpdateCustomers</code>, <code>ShopifyCreateDraftOrders</code>, <code>ShopifyUpdateDraftOrders</code>, <code>ShopifyCreateOrders</code>, and <code>ShopifyUpdatedOrders</code>.</p>" |
2760 | 2775 | }
|
2761 | 2776 | }
|
2762 | 2777 | },
|
|
3105 | 3120 | },
|
3106 | 3121 | "KeyName":{
|
3107 | 3122 | "shape":"name",
|
3108 |
| - "documentation":"<p>A searchable identifier of a customer profile. The predefined keys you can use to search include: _account, _profileId, _fullName, _phone, _email, _ctrContactId, _marketoLeadId, _salesforceAccountId, _salesforceContactId, _zendeskUserId, _zendeskExternalId, _serviceNowSystemId.</p>" |
| 3123 | + "documentation":"<p>A searchable identifier of a customer profile. The predefined keys you can use to search include: _account, _profileId, _assetId, _caseId, _orderId, _fullName, _phone, _email, _ctrContactId, _marketoLeadId, _salesforceAccountId, _salesforceContactId, _salesforceAssetId, _zendeskUserId, _zendeskExternalId, _zendeskTicketId, _serviceNowSystemId, _serviceNowIncidentId, _segmentUserId, _shopifyCustomerId, _shopifyOrderId.</p>" |
3109 | 3124 | },
|
3110 | 3125 | "Values":{
|
3111 | 3126 | "shape":"requestValueList",
|
|
3238 | 3253 | "UNIQUE",
|
3239 | 3254 | "SECONDARY",
|
3240 | 3255 | "LOOKUP_ONLY",
|
3241 |
| - "NEW_ONLY" |
| 3256 | + "NEW_ONLY", |
| 3257 | + "ORDER" |
3242 | 3258 | ]
|
3243 | 3259 | },
|
3244 | 3260 | "StandardIdentifierList":{
|
|
0 commit comments