# How to Submit an Application to Production This guide explains how to submit a developer application for production review from inside the SPA Developer Portal. ## Prerequisites Before submitting to production, make sure you have: - Tested the application's scopes, webhooks, and benefits end to end in the sandbox. - Confirmed the application behaves as expected for real customer scenarios. ## Step 1 — Open the Production tab In the sidebar, switch to the **Production** tab. ## Step 2 — Go to Application Submissions Click **Application submissions** in the Production sidebar (CheckCircle icon). This page lists every application you have submitted, with its submission date and current review status. ![app_submissions.png](/assets/app_submissions.39a153ccfa1f9bf2095b07a1ad7ee0314a0e047c1e4d8b6977108e22805519e6.71a4f21c.png) If you haven't submitted anything yet, you'll see an empty state with a short walkthrough and an **ADD APPLICATION** button. ## Step 3 — Add your application Click **+ ADD APPLICATION**. A modal opens asking for: - **Application Type** (Application type cannot be changed later) - **Application Name** - **Activation Email** ![app_submissions_add.png](/assets/app_submissions_add.15977241929befd7f96488a6079c384ce490822a54bf7f6fde76764085da7548.71a4f21c.png) Submitting the modal creates the application in **Draft** status and takes you straight to its detail page. ## Step 4 — Fill in the application details On the detail page, work through the same tabs used for sandbox applications: - **Details** — name and activation email (editable any time via "Edit Details"). - **Scopes** — the permissions your application needs in production. - **Webhooks** — endpoints that should receive real-time events. - **Benefits** — services to auto-create when the integration is activated. - **Events** — event configuration relevant to your integration type. ![app_submissions_details.png](/assets/app_submissions_details.6396bf772569cfcec11c8f6e02d69db0246bac54914de55fa27e0c49011a4083.71a4f21c.png) Before submitting, prepare the following — production reviewers will check for this: - **Application Overview**: what the application does and how it integrates with the platform. - **Scope Justification**: why requested scope/permission is needed. ## Step 5 — Submit for review Once every tab is filled in and reviewed, submit the application for production review. Its status moves from **Draft** to **Submitted**. ## Step 6 — Track the review status Back on the **Application submissions** list, each application shows a status chip: | Status | Meaning | | --- | --- | | Draft | Created but not yet submitted for review | | Submitted | Sent to the review team, awaiting triage | | In Review | Actively being reviewed | | Accepted | Approved for production | | Completed | Fully live in production | | Rejected | Not approved — see notes and resubmit a new app if needed | The info banner at the top of the page is a reminder: this list is **read-only**. ## Getting help - Support and general onboarding: see the public [Getting Started guide](https://developer.sportalliance.com/products/developer-portal/getting-started). - For issues specific to this portal (submissions stuck, statuses not updating), contact the Sport Alliance support team.