When you create, update or submit ACE opportunities through the AWS Partner Central Selling API, directly or through a connector, AWS refuses a bad request with an exception. This guide explains what the errors look like, the rules behind them, and how to fix the common ones. Rules are as AWS documents them as of November 2026. Where a rule comes from what the CoSell team saw in production or Sandbox calls instead, the guide says so. If AWS accepted the opportunity but its review came back as Action Required, see what Action Required means and how to fix it.
What an error looks like
The Selling API returns these exceptions on its opportunity actions:
ValidationException: the input breaks a format constraint or a business rule. It carries aReasonand anErrorList.ConflictException: the request conflicts with the record's current state. Fetch it again and retry.ResourceNotFoundException: the record does not exist, or your credentials cannot see it.AccessDeniedException: your identity lacks permission. It carries aReason.ThrottlingException: you sent too many requests.ServiceQuotaExceededException: the request would exceed a quota.StartEngagementFromOpportunityTaskcan return it.InternalServerException: usually transient. Retry after a short delay.
AWS's action pages list HTTP 400 for every one of these except InternalServerException, which is 500. Branch on the exception name, not the status code.
Inside a ValidationException
Reason says which kind of check failed:
REQUEST_VALIDATION_FAILED: the request itself is malformed, with missing required fields, wrong data types or bad string formats.BUSINESS_VALIDATION_FAILED: the request is well formed but breaks a Partner Central business rule.
ErrorList holds one entry per problem. Each has a Message and a Code, and usually a FieldName. The codes are:
REQUIRED_FIELD_MISSING: a required field is absent.INVALID_ENUM_VALUE: the value is not one AWS accepts for that field.INVALID_STRING_FORMAT: the string does not match the expected format, such as an email address or a date.INVALID_VALUE: the value is outside the allowed range or set.TOO_MANY_VALUESandNOT_ENOUGH_VALUES: a list has more or fewer entries than allowed.ACTION_NOT_PERMITTED: the change is not allowed in the record's current state, or with your permissions.DUPLICATE_KEY_VALUE: a value that must be unique already exists.
AWS also lists INVALID_RESOURCE_STATE and VALUE_OUT_OF_RANGE as valid codes, without a description. In CoSell's calls, field names in messages came back in lower camel case, such as customer.account.address.stateOrRegion, while request fields are written Customer.Account.Address.StateOrRegion. Compare them without regard to case.
Submission errors can arrive as a failed task
StartEngagementFromOpportunityTask is asynchronous. It runs several steps, including SubmitOpportunity. A refusal can come back as TaskStatus FAILED with a ReasonCode, such as OpportunityValidationFailed, OpportunitySubmissionFailed or RequestThrottled, and a Message explaining the failure, rather than as an exception. Read the task result, or look it up with ListEngagementFromOpportunityTasks.
The errors people hit most
| Error or message | What it means | How to fix |
|---|---|---|
REQUIRED_FIELD_MISSING on fields you did not change | UpdateOpportunity replaces the whole record. Any field you leave out becomes null. | Call GetOpportunity, change only what you mean to, and send the full record. |
REQUIRED_FIELD_MISSING on customer.account.address.stateOrRegion | The customer is in the US and has no state. CoSell saw this at submission. | Send a state name from AWS's list, such as California. |
| Submission refused for a missing delivery model, sales activities or use case | The API marks these optional, but CoSell has seen AWS refuse submission without them. | Fill Project.DeliveryModels, Project.SalesActivities and Project.CustomerUseCase before you submit. |
INVALID_ENUM_VALUE | A value is not on AWS's list, for example the industry, country, use case or delivery model. | Send the exact value AWS lists, with the same spelling, spacing and case. |
INVALID_STRING_FORMAT | A string breaks AWS's pattern, for example an email address or a date. | Use lower-case email of at most 80 characters, phone as + and digits, and dates as YYYY-MM-DD. |
ACTION_NOT_PERMITTED on country, postal code or website | The opportunity is approved and AWS has locked these fields. CoSell has seen this. | Leave locked fields unchanged and keep AWS's values in the payload. |
lifeCycle.stage is not editable post launch | The opportunity is Launched, so its stage can no longer change. CoSell also saw this for the city. | Stop sending stage changes for launched opportunities. |
You can not update the stage when Opportunity status is Pending Submission | AWS refused a stage change before submission. CoSell saw this in the Sandbox. | Set the stage when you create the opportunity. |
Update refused while Submitted or In review | AWS blocks all updates during its review. | Wait for the review result, then update. |
ConflictException on UpdateOpportunity | Your LastModifiedDate does not match AWS's copy. | Fetch the record again, reapply your change, and retry. |
Conflicting client token submitted for a new request body. | You reused a ClientToken with a different CreateOpportunity request. | Use a new token for a new request. Reuse a token only to retry the same request. |
ResourceNotFoundException | The record does not exist, or these credentials cannot see it. | Check the O-prefixed ID, the Catalog value and the credentials. |
AccessDeniedException | The IAM identity lacks the partnercentral: action, or a condition such as the catalog blocks it. | Add the action to the identity's policy. |
ThrottlingException | You are over the request rate or the daily quota. | Back off exponentially and retry. |
Rules that make a field required or refuse a value
Required at submission, not at creation
CreateOpportunity marks most fields optional, but AWS checks more at submission. Before StartEngagementFromOpportunityTask, AWS requires one to ten Partner Solutions, AWS Marketplace solutions or AWS Marketplace products on the opportunity. Each must be in Public or Limited status; AWS rejects draft or inactive entities. You attach them only with AssociateOpportunity. CreateOpportunity and UpdateOpportunity cannot set RelatedEntityIdentifiers.
Since 1 July 2026, moving an opportunity to Committed or Launched also requires an associated AWS Marketplace solution, AWS Marketplace product or Partner Solution. The console's Other option, described in Project.OtherSolutionDescription, is none of these, so on its own it does not meet the rule as AWS words it.
Values that need a companion field
- Industry
OtherneedsCustomer.Account.OtherIndustry, up to 255 characters. Project.OtherCompetitorNamesis allowed only whenProject.CompetitorNameis*Other.Project.OtherSolutionDescriptiondescribes your offer when the solution is Other.NationalSecurityapplies only when the industry isGovernment. The Partner Central form asks for it in that case.- When you choose co-sell, the Partner Central form asks for at least one value in
PrimaryNeedsFromAws.
Address and contact rules
CountryCodeis a two-letter code from AWS's list, such asUSorIN.StateOrRegiontakes names from AWS's list, which holds US states and territories. A US customer needs one.PostalCodeis up to 20 characters. The Partner Central form requires it.WebsiteUrlis 4 to 255 characters, and required except for national security opportunities.Duns, if you send it, is nine digits.- A contact
Emailmust be lower case throughout and at most 80 characters. Lower-case addresses before sending. - A contact
Phoneis+followed by up to 15 digits.
Expected spend
FrequencyisMonthly.TargetCompanyisAWS.Selfis accepted only whenProject.ExpectedContractDurationis present.- AWS's description says
CurrencyCodeacceptsUSDandEUR, although the list of values is longer. The AWS European Sovereign Cloud partition (aws-eusc) requiresEUR. Amountis digits with up to two decimals. No thousands separators and no currency symbols.EstimationUrl, if present, must be an AWS Pricing Calculator estimate link.ExpectedCustomerSpendtakes at most 10 entries.
Text fields and picklists
Project.CustomerBusinessProblemis 20 to 2,000 characters.LifeCycle.NextStepsis up to 255 characters, andPartnerOpportunityIdentifierup to 64.LifeCycle.TargetCloseDatemust not be in the past.- In the
AWScatalog,Originmust bePartner Referral. - Copy use case values from AWS's current list. AWS's API reference writes some without spaces around the slash, such as
Migration/Database Migration. CoSell found that ACE takes the spaced form,Migration / Database Migration, as Partner Central's own list writes it (Sandbox, 1 November 2026).
Locked fields and stage rules
SubmittedandIn review: nothing can change.Action Required: only the customer address, website, target close date, expected spend, business problem andPartnerOpportunityIdentifier.Approved: everything except country, postal code, industry, website, business problem,PartnerOpportunityIdentifierand title, plus any business rule AWS applies. CoSell has also seen AWS refuse a company name change.- Launched: AWS publishes no list. CoSell has seen AWS refuse changes to the stage and the city.
- Stage: AWS takes submissions from
Qualifiedonwards, and not for an opportunity already closed as lost.
UpdateOpportunity needs the full record. If you build it from a GetOpportunity response, AWS's Sandbox guide says to rename Id to Identifier and remove CreatedDate, OpportunityTeam and RelatedEntityIdentifiers. Keep LifeCycle.ReviewStatus as AWS returned it. In CoSell's Sandbox tests, leaving it out blanked the status, and the opportunity could no longer be submitted.
Catalogs, identifiers and idempotency
CatalogisAWSfor real opportunities andSandboxfor testing without touching live data. In the Sandbox, you simulate AWS's review by settingLifeCycle.ReviewStatustoApprovedorAction Requiredyourself.- The Selling API endpoint is in US East (N. Virginia):
partnercentral-selling.us-east-1.api.aws. - Opportunity IDs are
Ofollowed by digits. Engagement IDs starteng-and engagement invitation IDsengi-. ClientTokenis required onCreateOpportunityand onStartEngagementFromOpportunityTask. AWS recommends a UUID, unique to the request and unchanged across its retries.- CoSell found that a submission reusing the token of an earlier, refused attempt can repeat that refusal even after you fix the data. Derive the token from the opportunity's current version.
PartnerOpportunityIdentifierholds your CRM's record ID. AWS locks it after approval.
Throttling and retries
AWS's quotas apply per partner account:
- write actions such as
CreateOpportunity,UpdateOpportunity,AssociateOpportunityandStartEngagementFromOpportunityTask: 1 request a second and 10,000 in a rolling 24 hours; - read actions such as
GetOpportunity,ListOpportunitiesandGetAwsOpportunitySummary: 10 a second and 100,000 in 24 hours.
Over a limit, AWS returns ThrottlingException, and the AWS SDKs retry it automatically. AWS recommends exponential backoff; add random jitter so parallel workers do not retry in step. Retry InternalServerException after a short delay. Never retry ValidationException or AccessDeniedException unchanged, and fetch the record again before retrying a ConflictException. To save read quota, react to Amazon EventBridge events, or poll ListOpportunities with the AfterLastModifiedDate filter. Request higher limits in Service Quotas.
Where CoSell fits
CoSell connects Salesforce, HubSpot, Microsoft Dynamics 365, Zoho CRM or LeadSquared, or CoSell's built-in CRM, to Partner Central through the Selling API. It checks each deal against AWS's rules inside your CRM workflow before submission and names the field to fix; AWS's own Partner Central agent can also check drafts in the console. After submission, CoSell shows AWS's review status and comments on the deal, keeps an error inbox with retry, and leaves out fields AWS has locked instead of failing the whole update. It runs hosted by HabileLabs or in your own AWS account, from USD 10 a month on AWS Marketplace; the offer is currently for AWS accounts in India. See features and pricing.
Sources
- Selling API actions: CreateOpportunity (opens in a new tab), UpdateOpportunity (opens in a new tab), SubmitOpportunity (opens in a new tab), StartEngagementFromOpportunityTask (opens in a new tab) and AssociateOpportunity (opens in a new tab) (checked 13 November 2026)
- Selling API errors: ValidationExceptionError (opens in a new tab) and Common error types (opens in a new tab) (checked 13 November 2026)
- Selling API types: LifeCycle (opens in a new tab), Account (opens in a new tab), Address (opens in a new tab), Contact (opens in a new tab), Project (opens in a new tab) and ExpectedCustomerSpend (opens in a new tab) (checked 13 November 2026)
- Selling API developer guide: opportunity updates (opens in a new tab), associating opportunities (opens in a new tab), optimistic locking and data sync (opens in a new tab), quotas (opens in a new tab), testing in a sandbox (opens in a new tab) and supported Regions (opens in a new tab) (checked 13 November 2026)
- Creating an opportunity (opens in a new tab), Partner Central sales guide (checked 13 November 2026)
- AWS Partner Central now supports AWS Marketplace listings for co-selling (opens in a new tab), AWS What's New, 1 July 2026 (checked 13 November 2026)