Signa1's API setup

Complete Configuration Guide

Google Cloud API Setup Guide

Step-by-step instructions for configuring APIs in Google Cloud Console

Project Name

Signa1

Application

Signa1 Internet

Domain

Signa1.online

1

Access Google Cloud Console

Navigate to the Google Cloud Console and ensure you're logged in with the account that has access to your Signa1 project.

Open Google Cloud Console

📍 Direct URL

https://console.cloud.google.com/

2

Select Your Project

Click on the project dropdown at the top of the page (next to "Google Cloud") and select Signa1 from your list of projects.

💡 Tip: If you don't see Signa1, use the search box or verify you're logged into the correct Google account that owns this project.

3

Navigate to APIs & Services

From the main dashboard, open the navigation menu (☰ hamburger icon) on the left side and find "APIs & Services" → "Library".

Go to API Library

🔗 Navigation Path

☰ Menu → APIs & Services → Library

4

Search for Required APIs

In the API Library, use the search bar to find the APIs you need for your Signa1 Internet GPS tracking application. Essential APIs for GPS tracking, drop pin markers, and network frequency detection:

📍 Maps JavaScript API

Required for GPS tracking, drop pin markers, and map display

Enable API

🌐 Geolocation API

For detecting network connection locations and GPS coordinates

Enable API

📡 Places API

For identifying network frequency spots and location details

Enable API

☁️ Cloud Storage API

For storing GPS tracking data and network frequency logs

Enable API

🔐 Cloud Firestore API

Real-time database for network connection data and marker sync

Enable API

🛰️ Directions API

For route tracking and navigation between GPS markers

Enable API

📶 Distance Matrix API

Calculate distances between network frequency spots

Enable API

���️ Geocoding API

Convert GPS coordinates to addresses for marker labels

Enable API

�� Maps Static API

Generate static map images with custom drop pin markers

Enable API

⏱️ Time Zone API

Timestamp tracking data with accurate location time zones

Enable API

5

Create API Credentials

After enabling your APIs, you'll need to create credentials to authenticate your Signa1 Internet application.

Go to Credentials Page

Click "+ CREATE CREDENTIALS" and choose:

• API Key - For simple, public API calls (less secure)
• OAuth 2.0 Client ID - For user authentication and authorization
• Service Account - For server-to-server interactions (recommended for production)

6

Configure OAuth Consent Screen (If Using OAuth)

If you're creating OAuth credentials, you must configure the OAuth consent screen first:

Configure OAuth Consent

Fill in the required information:

• App name: Signa1 Internet
• User support email: Your email address
• App domain: Signa1.online
• Authorized domains: Add Signa1.online
• Developer contact: Your email address

7

Restrict and Secure Your API Keys

For any API keys you create, it's crucial to add restrictions:

1. Click on the API key name in the credentials list
2. Under "Application restrictions", select "HTTP referrers (web sites)"
3. Add your domain: Signa1.online/*
4. Under "API restrictions", select "Restrict key" and choose only the APIs you need
5. Click "SAVE"

🔒 Security Warning: Never commit API keys to public repositories or expose them in client-side code. Always use environment variables and server-side authentication when possible.

8

Set Up Billing (If Required)

Some APIs require billing to be enabled on your project, even if you're within the free tier limits.

Go to Billing Settings

Steps to link billing:

1. Select your Signa1 project
2. Click "Link a billing account"
3. Create a new billing account or select an existing one
4. Enter payment information (credit card required)

💡 Free Tier: Google Cloud offers generous free tier limits. Set up billing alerts to avoid unexpected charges.

9

Verify API Status

Confirm all your APIs are enabled and functioning correctly:

View API Dashboard

On the dashboard, you'll see:

• List of all enabled APIs for your Signa1 project
• Traffic statistics and usage metrics
• Any quota limits or errors
• Request counts and latency information

10

Configure WWW Subdomain for Signa1.online

Set up your domain to work with both signa1.online and www.signa1.online by configuring DNS records at your domain registrar.

📋 Overview

To make your website accessible via both signa1.online and www.signa1.online, you need to add DNS records at your domain registrar and optionally set up URL redirection.

🎯 Step-by-Step Configuration

1️⃣ Access Your Domain Registrar's DNS Settings

Log in to the website where you purchased your domain (e.g., GoDaddy, Namecheap, Google Domains, Cloudflare).

• Navigate to: My Domains or Domain Management
• Select: signa1.online
• Find: DNS Settings, DNS Management, or Manage DNS

2️⃣ Find Your Server IP Address

Before you can configure DNS, you need to know where your website is hosted. Here's how to find your IP address:

🎯 Choose Your Hosting Scenario:

Option A: Using a Web Hosting Provider

If you're using a hosting service (GoDaddy Hosting, Bluehost, HostGator, SiteGround, etc.):

• Log in to your hosting provider's control panel (cPanel, Plesk, or custom dashboard)
• Look for "Server Information", "Account Details", or "Server IP"
• The IP address will be in format: XXX.XXX.XXX.XXX
• For GoDaddy Hosting: Go to "My Products" → "Web Hosting" → Click "Manage" → Find IP address in hosting details

Option B: Using Google Cloud (App Engine, Compute Engine, Cloud Run)

For Google Cloud services:

• Compute Engine VM: Go to VM Instances → Find "External IP" column
• App Engine: Use Google's nameservers instead (see Option C below)
• Cloud Run: Cloud Run provides a URL, not an IP. Map custom domain through Cloud Run console directly
• Load Balancer: Go to Load Balancers → Find frontend IP address

Option C: Using Google Cloud Nameservers (Advanced)

For full Google Cloud DNS management:

• Create a Cloud DNS zone: Cloud DNS Console
• Add your domain "signa1.online" as a new zone
• Google will provide nameservers like: ns-cloud-XX.googledomains.com
• Update nameservers at GoDaddy to point to Google's nameservers
• Manage all DNS records through Google Cloud DNS

Option D: Check Current Configuration (If Site Already Works)

If signa1.online already loads a website:

• Use an online DNS lookup tool: dnschecker.org
• Enter "signa1.online" and select "A" record type
• The current IP address will be displayed
• Or use command line: nslookup signa1.online

Configure A Record for Root Domain

Once you have your IP address, add or edit the A record:

Type	Name/Host	Value/Points To	TTL
A	@ (or blank/root)	Your IP from above	3600

💡 Example: If your hosting provider shows IP 203.0.113.45, enter that exact number in the "Value" field.

3️⃣ Add CNAME Record for WWW Subdomain

Create a CNAME record to make www.signa1.online point to your root domain:

Type	Name/Host	Value/Points To	TTL
CNAME	www	signa1.online	3600

💡 Alternative: Some registrars allow you to use an A record instead of CNAME for the www subdomain. In that case, use the same IP address as your root domain.

4️⃣ Save DNS Changes

After adding both records:

• Click Save or Save Changes
• DNS changes can take 15 minutes to 48 hours to fully propagate worldwide
• Most changes appear within 1-2 hours

5��⃣ Configure Server-Side Redirect (Optional but Recommended)

To automatically redirect visitors from one version to the other (e.g., www → non-www or vice versa), configure your web server:

For Apache (.htaccess file):

# Redirect www to non-www RewriteEngine On RewriteCond %{HTTP_HOST} ^www\.signa1\.online$ [NC] RewriteRule ^(.*)$ https://signa1.online/$1 [R=301,L] # OR redirect non-www to www RewriteEngine On RewriteCond %{HTTP_HOST} ^signa1\.online$ [NC] RewriteRule ^(.*)$ https://www.signa1.online/$1 [R=301,L]

For Nginx (server block):

# Redirect www to non-www server { server_name www.signa1.online; return 301 https://signa1.online$request_uri; } # OR redirect non-www to www server { server_name signa1.online; return 301 https://www.signa1.online$request_uri; }

6️⃣ Verify Your Configuration

After DNS propagation, test both URLs in your browser:

• Visit https://signa1.online (should load your website)
• Visit https://www.signa1.online (should also load your website)
• Check that any redirect (if configured) works correctly

🔍 DNS Propagation Checker: Use online tools like dnschecker.org or whatsmydns.net to verify DNS propagation globally.

🔀 Optional: Set Up Forwarding

If you want one version to automatically redirect to the other (e.g., www → non-www):

• Go to your GoDaddy domain settings
• Find Forwarding section
• Set up domain forwarding as needed
• Ensure your SSL certificate covers both versions

📋 Quick Reference Links

API Dashboard

Monitor API usage and status

API Library

Browse and enable APIs

Credentials

Manage API keys and OAuth

Billing

Configure billing and alerts

Configuration guide for Signa1 Internet project

Google Cloud Console • API Management • Signa1.online