Queues a partial update against AWS Partner Central. The exact behavior depends on
the value of the tackle-operation-id header.
- Production cloud operations:
updateOpportunity(default),updateDraftOpportunity,
updateStartEngagementOpportunity,startEngagement,closeLostOpportunity,
launchOpportunity,updateOpportunityCRMID. - Test-environment-only:
acceptOpportunity,rejectOpportunity. These simulate
AWS-side responses to an incoming engagement invitation/opportunity and are routable
only for vendor accounts provisioned for use in a test environment. Production vendor
accounts that send one of these operation IDs receive400 Bad Requestwith the
messagethe requested operation is only supported in test or demo environments.
The success response is 202 Accepted with an empty body; poll getOpportunity or
listOpportunityEvents to observe the outcome of the queued request.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
202Accepted. The update request has been queued for asynchronous processing in AWS
Partner Central. The response body is empty; poll getOpportunity or
listOpportunityEvents to observe the result of the queued request.
401Unauthorized. The request did not include valid Tackle MTM bearer credentials, or the
authenticated principal could not be resolved.
500Internal Server Error. An unexpected error occurred while processing the request. Response
bodies for 5xx errors may be empty.
