Create a co-sell opportunity

post

https://aws.cosell.tackle.io/api/opportunities

Queues a create request against AWS Partner Central. The success response is 202 Accepted
with the Tackle identifier; poll getOpportunity to observe the cloud-side outcome.

If a crmId is supplied and your vendor account enforces a one-opportunity-per-CRM-ID
constraint, the request is rejected with 409 Conflict when an existing co-sell
opportunity already maps to the same CRM identifier. Whether this constraint is enforced
is configured per vendor; contact your Tackle account team if you need to change the
behavior.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

crmId

string

hubspotCrmId

string

HubSpot Deal ID to associate with this co-sell opportunity

awsSubmission

object

This information is required to start engagement with AWS.

opportunityTeam

array of objects

opportunityTeam

nationalSecurity

string

enum

Whether the opportunity is for a national-security or government
customer that AWS Partner Central treats as restricted. Submit Yes
for national-security workloads (which routes the opportunity through
AWS's restricted review path) and No otherwise.

Allowed:

customer

object

lifeCycle

object

marketing

object

opportunityType

string

enum

Allowed:

primaryNeedsFromAws

array of strings

primaryNeedsFromAws

project

object

softwareRevenue

object

solutions

array of strings

solutions

awsMarketplaceOffers

array of strings

Array of AWS Marketplace offer identifiers associated with the opportunity.

awsMarketplaceOffers

awsProducts

array of strings

Array of AWS product identifiers associated with the opportunity. These represent AWS services
or products that are part of the customer's solution (e.g., AmazonBedrock, AmazonS3, AmazonEC2Trn2).

awsProducts

dataMapper

object

Headers

tackle-operation-id

string

enum

Selects the create flow. createOpportunity (the default) creates the
opportunity and starts the AWS engagement; createDraftOpportunity creates
the opportunity in draft state without starting an engagement.

Header matching is lenient: only createDraftOpportunity is matched
explicitly, and any other value (including unknown values, an empty
string, or an omitted header) is routed through the default
createOpportunity flow rather than rejected with 400 Bad Request.
Clients should still send one of the documented values so future
server-side validation can be adopted without a breaking change.

Allowed:

Responses

401

Unauthorized. The request did not include valid Tackle MTM bearer credentials, or the
authenticated principal could not be resolved.

500

Internal Server Error. An unexpected error occurred while processing the request. Response
bodies for 5xx errors may be empty.

Language

Credentials

Bearer

MTM JWT

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

400Bad Request. The request was malformed or failed validation (for example, an invalid sortField/sortOrder value, an unsupported tackle-operation-id, or a request body that fails to parse as JSON).

409Conflict. The request cannot be applied to the resource in its current state (for example, attempting updateDraftOpportunity on an opportunity that is no longer in draft state, or createOpportunity with a crmId that already maps to an existing co-sell opportunity).