Google Firebase Auth REST API

Name: Firebase Auth REST API
Brand: Firebase Auth REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey9 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Firebase Auth REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Firebase Auth REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Firebase Auth REST API.

Authenticate existing users with email/password through /accounts:signInWithPassword

GET STARTED

Start building with Firebase Auth REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Firebase Auth REST API for, with concrete tasks.

★ Server-Side Email/Password Auth

Implement email/password signup and sign-in from a backend or agent runtime that cannot use the client SDK. POST /accounts:signUp creates the user, /accounts:signInWithPassword authenticates returning users, and /accounts:sendOobCode triggers verification and reset emails. A simple auth service is live in a few hours.

POST /accounts:signUp with email='alice@acme.com' and a generated password, then POST /accounts:sendOobCode to send a verification email to that address

Federated Identity (Google, Apple, etc.)

Accept sign-in from federated identity providers by sending the IdP token to /accounts:signInWithIdp. Firebase verifies the IdP credential and returns its own idToken/refreshToken pair. Useful when an agent needs to act on behalf of a user authenticated via Google or Apple. Typically integrated in under a day per provider.

POST /accounts:signInWithIdp with postBody='id_token=GOOGLE_ID_TOKEN&providerId=google.com' and store the returned refreshToken for later session refresh

Custom Token Exchange

Use the Firebase Admin SDK to mint a custom token for a user authenticated by your own backend, then exchange it for a real Firebase idToken via /accounts:signInWithCustomToken. This bridges legacy auth systems into Firebase-secured services. Setup is roughly half a day including Admin SDK key handling.

Mint a custom token for userId 'u_42' with the Admin SDK, then POST /accounts:signInWithCustomToken with the token to get a usable idToken

AI Agent Identity Operations

Use Firebase Auth through Jentic so an agent can sign up users, send password-reset emails, or look up account state without managing the Identity Toolkit shape. Jentic exposes the nine endpoints as discoverable tools while keeping the API key in the vault, suitable for support-desk agents and onboarding bots. Get started with Jentic One, the self-hosted execution layer

Through Jentic, search 'send a password reset email', load the /accounts:sendOobCode schema, and execute with requestType=PASSWORD_RESET and email='user@example.com'

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for firebase auth rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/accounts:signUp

POST

/accounts:signInWithPassword

POST

/accounts:signInWithIdp

POST

/accounts:signInWithCustomToken

Exchange a custom token for an idToken

POST

/accounts:lookup

Look up user account data

POST

/accounts:update

Update account profile or password

POST

/accounts:delete

Delete an account

POST

/accounts:sendOobCode

Send verification or password-reset email

POST

/accounts:signUp

POST

/accounts:signInWithPassword

POST

/accounts:signInWithIdp

POST

/accounts:signInWithCustomToken

Exchange a custom token for an idToken

POST

/accounts:lookup

Look up user account data

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Firebase Web API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a password reset email' or 'sign in with email and password', and Jentic returns the matching Identity Toolkit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Firebase Auth REST API through Jentic.

Why is there no official OpenAPI spec for Firebase Auth REST API?

Google does not publish an OpenAPI specification for the Firebase Auth REST surface. Jentic generates and maintains this spec so that AI agents and developers can call Firebase Auth REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Firebase Auth REST API use?

The API uses an apiKey passed as the `key` query parameter on every call (the Web API key from the Firebase console). Through Jentic, the key sits in the encrypted vault and is appended at execution time. End-user credentials are still managed via the request body fields like email, password, or idToken.

Can I sign users up with email and password using the Firebase Auth REST API?

Yes. POST /accounts:signUp accepts email and password and returns idToken, refreshToken, and localId. Pair with POST /accounts:sendOobCode (requestType=VERIFY_EMAIL) to trigger the email verification flow.

What are the rate limits for the Firebase Auth REST API?

Identity Toolkit applies per-project quotas - typical defaults allow hundreds of requests per second per project, with per-IP throttling on signup and sign-in. The API returns standard 429 responses; check the Firebase console for project-specific limits.

How do I send a password reset email through Jentic?

Search Jentic for 'send a password reset email', load the /accounts:sendOobCode schema, and execute with requestType=PASSWORD_RESET and the user's email. Firebase delivers the reset email using your project's email template.

Can I use the Firebase Auth REST API server-side?

Yes - that is its primary use case. Mobile and web SDKs use it under the hood; calling it directly from a server or agent works well when an SDK is not available.

Can I limit what my agent is allowed to do with the Firebase Auth REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Firebase Auth operations and credentials the agent may use, and you can grant only the endpoints it needs, such as /accounts:signInWithPassword and /accounts:sendOobCode, while leaving /accounts:delete or /accounts:update out of the allowed set. Firebase Auth names its target in the request body through fields like email or idToken rather than in the URL path, so scoping is done per operation. Your Firebase Web API key is held by your own instance and injected only when a permitted call runs, never entering the agent's prompt or logs.

Google Firebase Auth REST API

Connect the Firebase Auth REST API to your agent

Capabilities

Start building with Firebase Auth REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs