Callback Response

After processing an execution request, your service must send results back to Adobe through the callback URL.

Required Headers

X-Callback-Token: {tokenFromExecutionRequest} 
X-Api-Key: {customerApiKey} 
X-Request-Id: {requestId} 
Authorization: Bearer {accessToken} 
x-gw-ims-org-id: {imsOrgId} 
Content-Type: application/json 

To generate the accessToken for the Authorization header, set up OAuth Server-to-Server credentials in the Adobe Developer Console for your IMS Organization and Client.

Request Structure

{ 
  "objectData": [ 
    { 
      "activityData": {...}, 
      "leadData": {...}  // OR accountData, OR accountPersonData 
    } 
  ] 
} 

activityData

Every callback must include an activityData block that indicates success or failure:

{ 
  "activityData": { 
    "success": true, 
    "errorCode": null, 
    "reason": null 
  } 
} 

A success response looks like:

{ 
  "activityData": { 
    "success": true 
  } 
} 

and an error response contains the errorCode and reason:

{ 
  "activityData": { 
    "success": false, 
    "errorCode": "ENRICHMENT_FAILED", 
    "reason": "External API rate limit exceeded" 
  } 
} 

Callback Structure by Entity Type

Lead Callback

{ 
  "objectData": [ 
    { 
      "activityData": { 
        "success": true 
      }, 
      "leadData": { 
        "id": 12345, 
        "email": "john.doe@acme.com", 
        "firstName": "John", 
        "lastName": "Doe", 
        "mobilePhone": "+1-555-0101", 
        "linkedInUrl": "https://linkedin.com/in/johndoe", 
        "customField1": "enriched-value", 
        "accessorValues": { 
          "enrichmentScore": 92, 
          "dataQuality": "high", 
          "treatmentId": "premium" 
        } 
      } 
    } 
  ] 
} 

Required Fields

Optional Fields

Account Callback

{ 
  "objectData": [ 
    { 
      "activityData": { 
        "success": true 
      }, 
      "accountData": { 
        "id": 67890, 
        "accountName": "Acme Corporation", 
        "industry": "Technology", 
        "revenue": 2000000, 
        "employees": 5500, 
        "website": "https://acme.com", 
        "customAccountField1": "enriched", 
        "accessorValues": { 
          "accountScore": 95, 
          "tier": "enterprise", 
          "region": "EMEA" 
        } 
      } 
    } 
  ] 
} 

AccountPerson Callback

For an accountPerson entity type, the callback structure supports:

Structure mirrors the execution request for consistency.

{ 
  "objectData": [ 
    { 
      "activityData": { 
        "success": true, 
        "analysisModel": "enterprise-b2b-v2.5", 
        "leadsAnalyzed": 3, 
        "rolesIdentified": 3 
      }, 
      "accountData": { 
        "id": 54321, 
        "buyingGroupSize": 7, 
        "decisionTimeframe": "Q2 2024", 
        "committeeCompleteness": 0.85, 
        "accountEngagementScore": 88, 
        "opportunityStage": "evaluation" 
      }, 
      "accountPersonData": [ 
        { 
          "accountPersonRelId": 9001, 
          "accountId": 54321, 
          "personId": 12345, 
          "leadData": { 
            "email": "john.cto@acme.com", 
            "title": "Chief Technology Officer", 
            "mobilePhone": "+1-555-0101" 
          }, 
          "accessorValues": { 
            "buyingRole": "economic_buyer", 
            "influenceScore": 95, 
            "engagementLevel": "high" 
          } 
        }, 
        { 
          "accountPersonRelId": 9002, 
          "accountId": 54321, 
          "personId": 12346, 
          "leadData": { 
            "email": "jane.vp@acme.com", 
            "title": "VP of Operations" 
          }, 
          "accessorValues": { 
            "buyingRole": "champion", 
            "influenceScore": 88, 
            "engagementLevel": "high" 
          } 
        } 
      ] 
    } 
  ] 
} 

accountData Structure

accountPersonData Array Structure

Support Matrix

Split Path Accessors

When enableSplitPaths: true, include accessorValues in the entity payload (leadData, accountData, or accountPersonData[]) and keep keys/data types aligned with accessorsMetadata from the service definition.

See Path Condition Accessors for full accessor design and routing examples.

Callback Error Model

This page focuses on callback payload structure. Keep complete error taxonomy, response handling, and retry strategy in Error Handling.