Skip to main content

Overview

Your API key is essential for accessing Scoot Gateway API endpoints. This guide will walk you through the process of requesting, generating, and managing your API authentication tokens.
You must have a verified Scoot account before you can request API access. If you don’t have an account yet, follow our account creation guide first.

Prerequisites

Before requesting your API key, ensure you have:
  • ✅ A verified Scoot account
  • ✅ Completed email verification
  • ✅ Access to your Scoot Dashboard
  • ✅ Basic information about your intended API usage

Step-by-Step API Key Request Process

Step 1: Prepare Your Request Information

Before contacting support, gather the following information:
  • Account Details: Your registered email address and company name
  • Project Description: Clear explanation of your intended use case
  • Expected Usage: Estimated number of API calls per month
  • Environment: Development, staging, or production
  • Technical Contact: Primary developer contact information
  • Timeline: When you need API access

Step 2: Contact Scoot Support Team

Currently, API keys are managed by our support team. Send an email request with your information:
To: support@scoot.app
Subject: API Key Request - [Your Company Name]
Hello Scoot Support Team,

I would like to request API access for my Scoot account.

Account Information:
- Email: [your-account-email@domain.com]
- Company: [Your Company Name]

Technical Contact:
- Name: [Developer Name]
- Email: [developer@domain.com]
- Phone: [Optional contact number]

Additional Information:
[Any specific requirements or questions]

Thank you for your assistance.

Best regards,
[Your Name]
Make sure your email includes:
  • Valid account email (must match your Scoot account)
  • Clear use case description (helps with appropriate access levels)
  • Realistic usage estimates (for rate limiting setup)
  • Preferred environment (dev/staging/prod)
  • Timeline requirements (urgent vs standard processing)
  • Technical contact details (for key delivery and support)

Step 3: Wait for Support Response

After sending your request:
  • Initial Response: Within 24 hours (business days)
  • Processing Time: 1-3 business days for standard requests
  • Urgent Requests: Same day (if submitted before 12 PM EST)
  • Complex Cases: Up to 5 business days for custom requirements
The support team will:
  1. Verify your account and eligibility for API access
  2. Review your use case to determine appropriate access levels
  3. Generate your API key with proper permissions and limits
  4. Send you the key securely via email with usage instructions
  5. Provide additional resources and documentation links

Step 4: Receive Your API Key

When your request is approved, you’ll receive an email containing:
  1. Your API Key: A secure token for authentication
  2. Usage Instructions: How to implement the key in your requests
  3. Rate Limits: Your specific API usage limits
  4. Security Guidelines: Best practices for key management
  5. Support Contact: Direct contact for technical questions
Store your API key securely immediately upon receipt. The support team cannot retrieve lost keys - you’ll need to request a new one.

Step 5: Secure Your API Key

Immediately after generation:
  1. Copy the full API key - it will look like: sk_live_abc123def456...
  2. Store it securely in your password manager or secure notes
  3. Save it in your environment variables for development:
    SCOOT_API_KEY=your-actual-api-key-here
    
  4. Never commit the key to version control
To keep your API key secure:
  • ✅ Store in environment variables
  • ✅ Monitor usage for unusual activity
  • ❌ Never share keys via email or chat
  • ❌ Don’t hardcode keys in your application
  • ❌ Avoid storing keys in client-side code

Managing Your API Keys

API key management is currently handled through our support team. Self-service key management will be available in a future dashboard update.

Testing Your API Key

Once you have your API key, test it with a simple request:
curl -X GET "https://api.scoot.app/api/v1/transcription" \
  -H "X-API-Key: your-api-key-here" \
  -H "Content-Type: application/json"

Troubleshooting

Common Issues

If your API key isn’t working:
  1. Verify you copied the entire key (they’re usually 40+ characters)
  2. Check for extra spaces or characters
  3. Ensure you’re using the correct header: X-API-Key
  4. Contact support to verify the key is active
  5. Check your email for any key expiration notices
If you haven’t heard back from support:
  1. Check your spam/junk folder for replies
  2. Verify you sent to the correct email: support@scoot.app
  3. Resend your request with “FOLLOW-UP” in the subject
  4. Include your original email timestamp in the follow-up
  5. For urgent issues, mention “URGENT” in the subject line
If your API access request is delayed:
  1. Standard requests take 1-3 business days
  2. Check your spam folder for approval emails
  3. Verify you included all required information in your original request
  4. Send a polite follow-up email referencing your original request
  5. Include your account email and original request date
If you have questions about your request status:
  1. Reply to the support team’s email for clarification
  2. Provide additional information if requested
  3. Ask about alternative access levels if full access isn’t available
  4. Inquire about account tier upgrades if needed

Next Steps

After successfully obtaining your API key:

Support

Need help with API key requests? Our support team handles all API key operations:

Primary Support Channel

  • Email: support@scoot.app
  • Response Time: Within 24 hours (business days)
  • For Urgent Issues: Include “URGENT” in your subject line

Support Hours

  • Monday - Friday: 9:00 AM - 6:00 PM EST
  • Weekends: Limited support for urgent issues only
  • Holidays: Extended response times may apply

What to Include in Support Emails

For faster resolution, always include:
  • ✅ Your account email address
  • ✅ Specific error messages (if any)
  • ✅ What you’re trying to accomplish
  • ✅ Steps you’ve already tried
  • ✅ Timeline/urgency level

Additional Resources

  • Documentation: This help center for implementation guidance
  • Community: Developer discussions (coming soon)
Be specific about your use case when requesting API access. This helps our team provide the right level of access and better support.
I