Certify Your Ring Application

Ring App Store - Certify Phase

This document covers the certification process for Ring App Store applications through the Amazon Developer Portal.

Table of Contents

1. Overview
2. Prerequisites
3. Certification Process
4. Review Status
5. Version Control
6. Best Practices
7. Troubleshooting

Overview

The Certify phase is the third stage in the Ring App Store lifecycle (Configure → Develop → Certify → Publish). During this phase, your app configuration details are submitted for technical, security, and policy review by the Ring Team to ensure they meet quality standards before publishing.

What Gets Reviewed

The certification process reviews the app configuration details you provided during registration, including:

• App Information: App name, description, tags, features
• OAuth Configuration: Authentication type, partner endpoints (partnerConfigUrl, partnerLinkUrl, redirectUrl, webhookUrl)
• App Logo: Visual branding asset
• App Video: Promotional video demonstrating app functionality
• Endpoint Accessibility: Verification that configured URLs are reachable and functional

Important: You are not submitting application code. The review validates your app's configuration metadata and tests that your configured endpoints respond correctly.

Review Timeline

• Estimated Duration: 1-2 business days
• Pre-checks: Automated validation of configuration and endpoint accessibility
• Manual Review: Ring Team confirms end-to-end quality of configuration and endpoint responses

Prerequisites

Before submitting your app configuration for certification, ensure you have completed:

1. Configure Phase - App Registration Details
   • App name and description finalized
   • App tags selected appropriately
   • Features list configured (e.g., Liveview)
   • OAuth scopes defined (e.g., ava.devices)
   • App logo uploaded (PNG format, 512x512px recommended)
2. Configure Phase - OAuth Endpoints
   • authType set (typically "ring_driven")
   • partnerConfigUrl configured and accessible
   • partnerLinkUrl configured and accessible
   • redirectUrl configured and matches your OAuth implementation
   • webhookUrl configured and ready to receive POST requests
3. Develop Phase - Endpoint Implementation
   • All configured endpoints are deployed and accessible via HTTPS
   • OAuth endpoints respond correctly to Ring's requests
   • Webhook endpoint accepts POST requests and returns HTTP 200
   • Partner config endpoint returns valid JSON configuration
4. Testing
   • All configured endpoints tested and verified working
   • OAuth flow tested end-to-end
   • Webhook endpoint tested with sample payloads
   • Endpoints are stable and production-ready

Certification Process

Step 1: Review Readiness

Navigate to the Review and Certification section in the Amazon Developer Portal, Ring section.

The portal will display:

• Current certification status
• Previous review history (if any)
• Documentation links
• Version control options

Step 2: Start Review Process

When your app configuration is ready for review, click the Start review process button.

Important: Before starting, ensure:

• All configuration details are accurate and finalized
• All configured endpoints are deployed and accessible
• Endpoints have been tested and are production-ready
• You can withdraw within 1 minute after submission if needed

Step 3: Review Configuration Summary

Before submission, you'll see a confirmation screen displaying the complete configuration that will be submitted for review:

Configuration JSON:

{
  "appInformation": {
    "appName": "Your App Name",
    "description": "Detailed description of your app's functionality",
    "featureDescription": null,
    "features": null,
    "shortDescription": "Brief description for app listing",
    "tags": [
      "AI & Analytics Integrations"
    ],
    "title": null
  },
  "features": [
    "Liveview"
  ],
  "oauthScopes": [
    "ava.devices"
  ],
  "productionOauthConfig": {
    "authType": "ring_driven",
    "partnerConfigUrl": "https://yourapp.ai/partner-config",
    "partnerLinkUrl": "https://yourapp.ai/partner-link/",
    "redirectUrl": "https://yourapp.ai/redirect-url",
    "webhookUrl": "https://yourapp.ai/webhook-url"
  }
}

This JSON represents all the configuration details you provided during the Configure phase. The Ring Team will review this configuration and test that your endpoints respond correctly.

App Logo: Verify your uploaded logo appears correctly (PNG format, recommended size: 512x512px)

What to Verify:

• App name and descriptions are accurate and professional
• Tags and features correctly represent your app
• All URLs are correct and use HTTPS
• OAuth configuration matches your implementation
• Logo displays properly

Step 4: Confirm Submission

Review the configuration JSON carefully, then click Confirm submission.

Note: You can toggle between "Show unchanged" and "Split view" to review configuration changes if this is a resubmission. This is helpful to see what changed between versions.

Step 5: Pre-checks in Progress

After submission, automated pre-checks begin immediately to validate your configuration:

Status: "Certification in Progress" Message: "Ring Team to confirm end-to-end quality"

What Happens During Pre-checks:

• Configuration JSON is validated for completeness
• The wording in the description is verified in compliance with privacy and terms and conditions; this is done automtically

Submission Details:

• Version: Your configuration version (e.g., v2, v3, v5)
• Submitted on: Timestamp of submission (e.g., 12:38 02/13/2026)
• Estimated to complete: 1-2 business days

Withdrawal Option: You can withdraw from review 1 minute after submission if you need to make changes to your configuration.

Review Status

Certification States

Your app configuration can be in one of several states during the certification process:

1. Ready for Review

• All configuration details completed
• Endpoints configured and accessible
• Ready to submit configuration for certification

2. Pre-checks in Progress

• Automated validation of configuration JSON
• Endpoint accessibility checks
• Initial technical validation
• Withdrawal available after 1 minute from submission

3. Certification in Progress

• Ring Team manual review of configuration
• Testing of configured endpoints
• End-to-end quality verification
• Estimated completion: 1-2 business days

4. Certification Passed

• Configuration approved
• Endpoints verified working correctly
• Ready to move to Publish phase
• Can proceed with app launch

5. Certification Failed

• Issues identified in configuration or endpoints
• Detailed feedback provided
• Must update configuration/endpoints and resubmit

6. Withdrawn

• Configuration review withdrawn by developer
• Can update configuration and resubmit when ready
• Previous submission details retained for reference

Checking Status

To check your certification status:

1. Navigate to Review and Certification in the Amazon Developer Portal
2. View the current status banner
3. Check Review version history for past configuration submissions
4. Click View submitted diff to see the exact configuration JSON that was submitted

Version Control

Review Version History

The portal maintains a complete history of all configuration submissions:

Access: Click "Review version history" in the Version control section

Information Tracked:

• Version number (v1, v2, v3, etc.)
• Submission timestamp
• Review status (Withdrawn, In Progress, Passed, Failed)
• Configuration changes between versions
• Reviewer feedback (if applicable)

Version Management

1. Increment Versions: Each configuration submission creates a new version (v1, v2, v3)
2. Track Changes: Document what configuration details changed between versions
3. Learn from History: Review past feedback before updating and resubmitting
4. Test Endpoints: Ensure all endpoint changes are tested before resubmission

Viewing Submitted Configuration

Use the View submitted diff option to:

• See the exact configuration JSON that was submitted
• Compare configuration changes with previous versions
• Verify all endpoint URLs are correct
• Confirm app metadata and OAuth settings are accurate

Best Practices

Before Submission

1. Verify Configuration Details
   • App name is accurate and professional
   • Description clearly explains app functionality
   • Tags accurately represent your app's category
   • Features list is correct (e.g., Liveview)
   • OAuth scopes match your requirements (e.g., ava.devices)
   • App logo is high quality (PNG, 512x512px recommended)
2. Test All Configured Endpoints
   • partnerConfigUrl is accessible and returns valid JSON
   • partnerLinkUrl handles account linking requests
   • redirectUrl matches your OAuth implementation exactly
   • webhookUrl accepts POST requests and returns HTTP 200
   • All URLs use HTTPS (required for production)
   • Endpoints are deployed to production environment
3. Validate OAuth Implementation
   • OAuth flow works end-to-end with configured endpoints
   • Authorization requests are handled correctly
   • Token exchange works properly
   • Redirect URL matches configuration exactly (including trailing slash)
4. Test Webhook Endpoint
   • Endpoint accepts POST requests with JSON payload
   • Returns HTTP 200 within 5 seconds
   • Handles Ring's webhook payload format
   • Signature verification implemented (if required)

During Review

1. Monitor Status: Check the portal regularly for certification updates
2. Keep Endpoints Stable: Don't modify or take down configured endpoints during review
3. Monitor Endpoint Logs: Watch for Ring Team testing your endpoints
4. Respond Quickly: Address any questions or feedback from Ring Team promptly
5. Be Available: Ensure your team can respond to configuration issues

After Submission

1. Don't Change Configuration: Avoid modifying endpoint URLs during active review
2. Maintain Endpoint Availability: Keep all configured endpoints operational and responsive
3. Monitor for Test Traffic: Ring Team will test your endpoints - ensure they respond correctly
4. Prepare for Feedback: Be ready to update configuration if issues are found
5. Plan Next Steps: Prepare for the Publish phase once certification passes

Troubleshooting

Common Issues and Solutions

Issue: "Configuration Incomplete"

Symptoms: Cannot start review process, missing required fields

Solutions:

• Verify all required fields in Configure phase are filled:
  • App name and description
  • Tags and features
  • OAuth scopes
  • All OAuth endpoint URLs (partnerConfigUrl, partnerLinkUrl, redirectUrl, webhookUrl)
• Upload app logo if missing
• Ensure all URLs use HTTPS protocol

Issue: "Endpoint Not Accessible"

Issue: "Webhook Endpoint Not Responding"

Symptoms: Webhook validation fails during pre-checks

Solutions:

• Verify webhookUrl is accessible and accepts POST requests
• Ensure endpoint returns HTTP 200 within 5 seconds
• Test endpoint with sample Ring webhook payload
• Check that endpoint accepts application/json content type
• Review server logs for errors

Issue: "OAuth Configuration Mismatch"

Symptoms: OAuth flow fails during Ring Team testing

Solutions:

• Verify redirectUrl in configuration matches your OAuth implementation exactly
• Check for trailing slashes - they must match exactly
• Ensure partnerLinkUrl handles account linking correctly
• Test partnerConfigUrl returns valid JSON configuration
• Validate authType is set correctly (typically "ring_driven")

Issue: "Invalid Configuration JSON"

Symptoms: Pre-checks fail, configuration validation error

Solutions:

• Review the configuration JSON shown in submission screen
• Ensure all required fields are present
• Check that URLs are properly formatted
• Verify OAuth scopes are valid (e.g., "ava.devices")
• Confirm features list contains valid values

Issue: "Review Withdrawn Accidentally"

Symptoms: Need to resubmit configuration after withdrawal

Solutions:

• Click "Review version history" to see withdrawn submission
• Review the configuration that was submitted
• Make any necessary updates to configuration
• Version number will auto-increment on resubmission
• Click "Start review process" when ready

Getting Help

If you encounter issues during certification:

1. Check Version History: Review feedback from previous configuration submissions
2. View Submitted Diff: Use this feature to see exactly what configuration was submitted
3. Contact Support: Reach out to Ring Appstore Support use
   • Support case - https://developer.amazon.com/support/cases or Email: ring-appstore-support@amazon.com
   • Include: App name, configuration version, submission timestamp, specific issue
   • Attach: Configuration JSON if relevant

What Happens After Certification

Certification Passed

Once your app configuration passes certification:

1. Status Update: Portal shows "Certification Passed"
2. Configuration Approved: Your app details and endpoints are verified
3. Publish Phase: You can proceed to the Publish phase
4. Go Live: Complete publishing requirements to make app available in Ring App Store

Certification Failed

If certification fails:

1. Review Feedback: Detailed feedback provided by Ring Team about configuration or endpoint issues
2. Update Configuration: Fix identified problems in app details or endpoint URLs
3. Fix Endpoints: Address any endpoint accessibility or response issues
4. Retest: Thoroughly test all endpoint changes
5. Resubmit: Submit updated configuration (new version will be created automatically)

Timeline

• Passed: Proceed to Publish phase immediately
• Failed: Fix issues and resubmit (new 1-2 day review cycle)
• Withdrawn: Resubmit when ready (new review cycle)

Certification Checklist

Use this checklist before submitting your configuration for certification:

App Information Configuration

• App name is accurate and professional
• Description clearly explains app functionality and value
• Short description is concise and compelling
• Tags accurately represent app category (e.g., "AI & Analytics Integrations")
• Features list is accurate (e.g., "Liveview")
• App logo uploaded (PNG format, 512x512px recommended)

OAuth Configuration

• authType set correctly (typically "ring_driven")
• oauthScopes defined correctly (e.g., ["ava.devices"])
• All endpoint URLs use HTTPS protocol
• No typos in any URL configurations

Endpoint Configuration - partnerConfigUrl

• URL is accessible from the internet
• Returns valid JSON configuration
• Responds within reasonable time (< 5 seconds)
• HTTPS certificate is valid

Endpoint Configuration - partnerLinkUrl

• URL is accessible from the internet
• Handles account linking requests correctly
• Returns appropriate responses
• HTTPS certificate is valid

Endpoint Configuration - redirectUrl

• URL matches OAuth implementation exactly
• Includes or excludes trailing slash consistently
• Handles OAuth callback correctly
• HTTPS certificate is valid

Endpoint Configuration - webhookUrl

• URL is accessible from the internet
• Accepts POST requests with JSON payload
• Returns HTTP 200 status code
• Responds within 5 seconds
• HTTPS certificate is valid

Pre-Submission Testing

• All configured endpoints tested manually (curl/Postman)
• OAuth flow tested end-to-end with configured URLs
• Webhook endpoint tested with sample Ring payloads
• All endpoints deployed to production environment
• Endpoints are stable and won't be modified during review

Configuration Review

• Reviewed complete configuration JSON in submission screen
• Verified all URLs are correct
• Confirmed app metadata is accurate
• Checked that logo displays properly
• Ready to click "Confirm submission"

Last Updated: February 2026
Documentation Version: 1.0.0
Lifecycle Phase: Certify (Phase 3 of 4)