Submit a funding application draft to AWS

POST https://api.suger.cloud/org/{orgId}/fundingApplication/{fundingApplicationId}/submit

Send a draft saved by CreateFundingApplicationDraft to AWS Partner Central. Call it only after a person has approved the draft: it records the approval (approval status Approved), moves the application to PENDING_CREATE and starts the submission, whose outcome later shows in the application's status (PENDING_ACCEPTANCE once AWS has it, CREATE_FAILED with errorMessages if AWS refused it). The draft is validated again first; while fields are missing it answers 400 with the field `errors` and the draft stays as it was. An application that is not an unsent draft, is already on AWS Partner Central, or was declined by an approver answers 409, as does a second submit of the same draft.

Parameters

NameInTypeRequiredDescription
orgId path string yes Organization ID
fundingApplicationId path string yes Funding Application ID

Responses

200 — Success

Content-Type: application/json · Schema: OperationExecutionDetails

OperationExecutionDetails fields:

FieldTypeRequiredDescription
newWorkflowStarted boolean no
referralId string no ReferralID is the created referral's id, set by the SUGER co-sell create so the caller can chain follow-up calls (e.g. InviteCosellPartners) onto the new engagement without re-querying. Empty elsewhere.
runID string no
slackMirrorWarning string no SlackMirrorWarning is a non-blocking advisory set when a SUGER co-sell console message was saved but could not be mirrored to the partner's Slack channel (no workspace connected, no channel mapped, bot not in the channel, or a transient post failure). Empty when the message mirrored or Slack is not involved. The console surfaces it as a warning toast; the message is always persisted regardless (best-effort mirror).
status string no
workflowID string no

400 — The draft still has field errors

Content-Type: application/json · Schema: ValidateFundingApplicationResponse

ValidateFundingApplicationResponse fields:

FieldTypeRequiredDescription
errors array<FundingApplicationFieldMappingIssue> no

FundingApplicationFieldMappingIssue fields:

FieldTypeRequiredDescription
field string no
message string no

404 — Not found

Content-Type: application/json

409 — Not an unsent draft

Content-Type: application/json

500 — Internal server error

Content-Type: application/json

Example

Generated from this operation's schema. Values are placeholders — substitute your own ids, and set SUGER_TOKEN to a bearer token from the OAuth client-credentials exchange.

Request

curl -X POST 'https://api.suger.cloud/org/{orgId}/fundingApplication/{fundingApplicationId}/submit' \
  -H "Authorization: Bearer $SUGER_TOKEN"

Response — 200

{
  "newWorkflowStarted": true,
  "referralId": "01H0000000000000000000",
  "runID": "01H0000000000000000000",
  "slackMirrorWarning": "string",
  "status": "string",
  "workflowID": "01H0000000000000000000"
}

Error — 400

{
  "errors": [
    {
      "field": "string",
      "message": "string"
    }
  ]
}

View as Markdown · API reference overview

Spotted something wrong or out of date on this page? Tell us and we'll correct it.