> ## Documentation Index
> Fetch the complete documentation index at: https://docs.radium.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Radium

> Explore the Google Developer Platform — a REST API for user management, project orchestration, and webhooks, with OAuth 2.0 auth and official SDKs.

The Google Developer Platform is a unified REST API that gives developers, teams, and enterprises programmatic access to core infrastructure services — including user management, project orchestration, and real-time event streaming via webhooks. Whether you're building a server-side automation, a customer-facing SaaS product, or a multi-tenant application, the platform provides a consistent, well-documented API surface backed by OAuth 2.0 authentication, official JavaScript and Python SDKs, and a robust webhook system.

## What You Can Build

The Google Developer Platform is designed to power a wide range of integration patterns. Here are some of the most common use cases developers build on top of it.

<CardGroup cols={2}>
  <Card title="Automated Workflows" icon="gears">
    Trigger actions automatically when platform events occur. Combine webhook subscriptions with project and user APIs to build event-driven workflows without polling.
  </Card>

  <Card title="User Management" icon="users">
    Create, update, and deactivate users programmatically. Sync user identities between your application and the Google Developer Platform to keep access permissions always up to date.
  </Card>

  <Card title="Project Orchestration" icon="diagram-project">
    Manage projects, assign members, configure settings, and track resource usage — all through a single, consistent API without touching the Google Cloud Console UI.
  </Card>

  <Card title="Real-Time Events via Webhooks" icon="bolt">
    Subscribe to platform events and receive instant HTTP callbacks when something changes — a new user is created, a project is updated, or a quota threshold is crossed.
  </Card>
</CardGroup>

## How It Works

The Google Developer Platform exposes a standard **REST API** over HTTPS. All requests and responses use **JSON**, making the API easy to consume from any programming language or HTTP client.

**Base URL**

Every API endpoint is rooted at:

```
https://api.google.com/v1
```

**Request Format**

Append the resource path to the base URL and provide the appropriate HTTP method (`GET`, `POST`, `PATCH`, `DELETE`). Include your credentials in the `Authorization` header on every request.

**Authentication**

The platform supports two authentication methods:

* **API Keys** — Ideal for server-to-server integrations where you control both ends of the connection. Pass your key as a `Bearer` token in the `Authorization` header.
* **OAuth 2.0** — Required when acting on behalf of an end user. The platform implements the standard Authorization Code flow, issuing scoped access tokens that expire and can be refreshed.

See the [Authentication guide](/authentication) for full setup instructions and code examples for both methods.

**Responses**

All responses return standard HTTP status codes. Successful requests return `2xx` codes with a JSON body. Errors return `4xx` or `5xx` codes alongside a structured error object containing a `code`, `message`, and optional `details` field to help you debug quickly.

## Key Concepts

Familiarize yourself with these core terms before diving into the API reference — you'll encounter them throughout the documentation.

**Resources**
The primary objects the API exposes, such as users, projects, and webhooks. Each resource has a unique identifier and a standard set of CRUD endpoints.

**Projects**
The top-level organizational unit on the platform. All resources — users, webhooks, API keys — belong to a project. Your API key is always scoped to a specific project.

**Users**
Individuals who have been granted access to a project. Users have roles and permissions that determine which API scopes their tokens can include.

**Scopes**
Fine-grained permission strings attached to OAuth 2.0 tokens (e.g., `read:users`, `write:projects`). A token can only perform actions covered by the scopes it was granted at authorization time.

**Webhooks**
Outbound HTTP callbacks that the platform fires when specific events occur inside your project. You register a target URL and an event type; the platform delivers a signed JSON payload to that URL in real time.

## Next Steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Follow a step-by-step walkthrough to make your first live API call in under 5 minutes.
  </Card>

  <Card title="Authentication" icon="lock" href="/authentication">
    Learn how to create API keys and implement OAuth 2.0 to secure every request your application makes.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.