API Reference

IP Whitelisting

IP Whitelisting for Spartera Data Connections

When connecting your data sources to Spartera, you may need to whitelist our
IP addresses to allow secure access through your firewall or database security
rules.

Spartera IP Addresses

Production Environment

IP Address: 34.70.197.249

Use this IP address for all production data connections and marketplace assets.

Staging Environment

IP Address: 34.57.29.87

Use this IP address when testing integrations in our staging environment.

How to Configure IP Whitelisting

For Google BigQuery

  1. Navigate to your BigQuery project in Google Cloud Console
  2. Go to IAM & Admin → Firewall Rules
  3. Add a new rule with Spartera's production IP: 34.70.197.249
  4. Set the action to Allow
  5. Apply the rule to your dataset

For AWS RDS/Aurora

  1. Open the Amazon RDS console
  2. Select your database instance
  3. Navigate to Connectivity & Security → Security Groups
  4. Edit inbound rules
  5. Add a new rule:
    • Type: MySQL/Aurora (or your database type)
    • Source: Custom → 34.70.197.249/32
  6. Save the rule

For Snowflake

  1. Log into your Snowflake account
  2. Navigate to Admin → Security → Network Policies
  3. Create or edit your network policy
  4. Add Spartera's IP to the Allowed IP Addresses list:
   34.70.197.249
  1. Apply the policy to your account

For MySQL/PostgreSQL (Self-Hosted)

Edit your firewall configuration to allow incoming connections:

For Ubuntu/Debian (UFW):

sudo ufw allow from 34.70.197.249 to any port 3306

For CentOS/RHEL (firewalld):

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="34.70.197.249" port protocol="tcp" port="3306" accept'
sudo firewall-cmd --reload

For Azure SQL Database

  1. Open the Azure Portal
  2. Navigate to your SQL Server
  3. Go to Security → Firewalls and virtual networks
  4. Add a new rule:
    • Rule name: Spartera-Production
    • Start IP: 34.70.197.249
    • End IP: 34.70.197.249
  5. Click Save

Testing Your Connection

After whitelisting our IP addresses:

  1. Go to app.spartera.com
  2. Navigate to Data Sources → Add Connection
  3. Enter your database credentials
  4. Click Test Connection
  5. You should see a success message

Security Best Practices

Use Read-Only Credentials

Always create a dedicated read-only database user for Spartera connections:

-- Example for MySQL
CREATE USER 'spartera_readonly'@'34.70.197.249' IDENTIFIED BY 'secure_password';
GRANT SELECT ON your_database.* TO 'spartera_readonly'@'34.70.197.249';
FLUSH PRIVILEGES;

Limit Access to Specific Schemas

Only grant access to the schemas/tables that contain data you want to
monetize:

-- Example for PostgreSQL
CREATE USER spartera_readonly WITH PASSWORD 'secure_password';
GRANT CONNECT ON DATABASE your_database TO spartera_readonly;
GRANT USAGE ON SCHEMA analytics TO spartera_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA analytics TO spartera_readonly;

Enable SSL/TLS Encryption

Always require encrypted connections:

  • BigQuery: Encryption is enabled by default
  • AWS RDS: Enable require_secure_transport
  • Snowflake: Use ssl=on in connection parameters
  • Azure SQL: Enable "Require secure connections"

Troubleshooting

Connection Timeout

If you're experiencing connection timeouts:

  1. Verify the IP address is correctly whitelisted: 34.70.197.249
  2. Check that the database port is open (3306 for MySQL, 5432 for PostgreSQL)
  3. Ensure no VPC/subnet routing issues exist
  4. Verify DNS resolution if using hostnames

Access Denied Errors

If you see "Access Denied" errors:

  1. Confirm the database user has proper SELECT permissions
  2. Verify credentials are correct
  3. Check that the user is allowed to connect from Spartera's IP
  4. Review database audit logs for specific error messages

Staging Environment Testing

If you need to test in our staging environment first:

  1. Create a separate staging database connection
  2. Whitelist the staging IP: 34.57.29.87
  3. Test thoroughly before moving to production
  4. Update to production IP: 34.70.197.249 when ready

Support

Need help with IP whitelisting or connection issues?