DEV Community

Cover image for Getting Started with the Gemini API: A Practical Guide
eleonorarocchi
eleonorarocchi

Posted on

Getting Started with the Gemini API: A Practical Guide

#gemini #ai #google #llm

Getting Started with the Gemini API: A Practical Guide for Students

TL;DR

  • Getting access to the Gemini API takes less than 15 minutes: a Google Cloud account, an API key, and a Python library are enough to produce your first working prompt.
  • The free tier is sufficient for educational projects, experiments, and portfolio work: you don’t need a credit card to start building real things.
  • The barrier to entry is lower than it seems: the difficult part is not the technical setup, but knowing what to build once the model starts responding.

The Context

Whenever a junior developer asks me how to approach AI in a practical way, my answer is always the same: stop watching YouTube tutorials and write a line of code that calls a real model.

The problem is that “getting started” seems more complicated than it actually is. Dense official documentation, terminology that isn’t always clear, and the feeling that you need months of theory before touching something that actually works. That’s not the case.

Google’s Gemini API is currently one of the most accessible tools for anyone who wants to take their first steps with applied artificial intelligence. It supports text, images, and code, has a real free tier, and integrates with Python in just a few minutes. It’s not the only option on the market, but for a student or someone starting from scratch it’s probably the entry point with the best balance between simplicity and power.

This guide has a single goal: to take you from zero to your first working prompt in the shortest time possible.

How It Works

Step 1 — Create an account and enable the API

The starting point is Google AI Studio. You don’t need to configure a full Vertex AI project to begin: AI Studio is the most direct interface for developers who want to prototype quickly.

  1. Sign in with your Google account.
  2. Go to AI Studio and click Get API Key.
  3. Create a new API key or associate it with an existing Google Cloud project.
  4. Copy the key and store it safely: you’ll need it in a moment.

Operational note: never put the API key directly in your source code, especially if you’re working with Git. Use an environment variable or a .env file excluded from the repository.

Step 2 — Install the Python library

Open your terminal and install the official package:

pip install google-generativeai
Enter fullscreen mode Exit fullscreen mode

If you work in a virtual environment (which I always recommend, even for small projects):

python -m venv gemini-env
source gemini-env/bin/activate  # on Windows: gemini-env\Scripts\activate
pip install google-generativeai
Enter fullscreen mode Exit fullscreen mode

Step 3 — Configure the API key

The cleanest way is to use an environment variable. On Linux/macOS:

export GOOGLE_API_KEY="your-key-here"
Enter fullscreen mode Exit fullscreen mode

On Windows (PowerShell):

$env:GOOGLE_API_KEY="your-key-here"
Enter fullscreen mode Exit fullscreen mode

Alternatively, you can use a .env file with the python-dotenv library:

pip install python-dotenv
Enter fullscreen mode Exit fullscreen mode

And in the .env file:

GOOGLE_API_KEY=your-key-here
Enter fullscreen mode Exit fullscreen mode

Step 4 — Write your first working prompt

This is the moment when you stop reading guides and actually see something happen. Create a file called first_prompt.py with the following content:

from dotenv import load_dotenv
from google import genai
import os

load_dotenv()

client = genai.Client(api_key=os.getenv("GOOGLE_API_KEY"))

response = client.models.generate_content(
    model="gemini-2.5-flash",
    contents="Explain what an API is in three simple sentences."
)

print(response.text)
Enter fullscreen mode Exit fullscreen mode

Run it with:

python first_prompt.py
Enter fullscreen mode Exit fullscreen mode

If everything is configured correctly, you’ll see a text response from the model in your terminal. This is the starting point: from here you can build anything.

Step 5 — Add a bit of structure

Once the model responds, the next step is to make the code interactive. Here is a minimal example of a terminal chatbot:

from dotenv import load_dotenv
from google import genai
import os

load_dotenv()

client = genai.Client(api_key=os.environ["GOOGLE_API_KEY"])

print("Chatbot active. Type 'exit' to quit.\n")

history = []

while True:
    user_input = input("You: ")

    if user_input.lower() == "exit":
        break

    history.append(user_input)

    response = client.models.generate_content(
        model="gemini-2.5-flash",
        contents=history
    )

    reply = response.text
    print(f"Gemini: {reply}\n")

    history.append(reply)
Enter fullscreen mode Exit fullscreen mode

Twenty lines of code, a working chatbot with conversation memory. The start_chat model automatically maintains message history.

Practical Observations

A few things worth knowing before moving forward, which the official documentation tends to mention only in passing.

About the free tier. It exists and it’s real, but it has rate limits (requests per minute and per day). For small projects and prototypes this is not a problem. It becomes one if you build something that must handle continuous load or many simultaneous users. Keep an eye on your quota in the Google Cloud Console.

About choosing the model. At the moment gemini-2.5-flash is the best balance for beginners: fast, inexpensive (in terms of quota), and capable enough for most educational projects. gemini-2.5-pro is more powerful but consumes more quota. For your first project, use Flash.

About error handling. API calls fail. Always, sooner or later. Quota exhausted, timeouts, unexpected responses. Get your code used to handling exceptions right away:

try:
    response = model.generate_content("Your prompt")
    print(response.text)
except Exception as e:
    print(f"Error during API call: {e}")
Enter fullscreen mode Exit fullscreen mode

It’s not elegant, but it’s the bare minimum to avoid scripts crashing silently.

About prompts. The quality of the output depends enormously on how you formulate the request. A vague prompt produces vague answers. If you’re building a specific tool — a text analyzer, a quiz generator, a code corrector — invest time in defining the system prompt well. The difference between a mediocre result and a useful one often lies there, not in the code.

About API key security. I repeat this because it matters: the API key is a credential. If it ends up in a public GitHub repository, someone will use it in your place and you’ll receive the bill. Use .gitignore to exclude .env files, and if you’ve already committed a key by mistake, revoke it immediately from Google.

Top comments (0)