# Sign in with a Google One Tap credential

No router-level gate; the handler spends a nonce from the nonce route and verifies the Google credential.

> **Note:**

**Not fully described yet.** The API description has no described successful answer for this operation yet. The method, path, sign-in, rate limits and request fields on this page are read from the server's code and are accurate; what a successful call returns is not written down here yet. Until it is, search engines and the agent index leave this page out.

`POST /api/v1/auth/social/google/orgId/methodId/one-tap`

- Sign-in: None at the router: the operation is public, or checks its own proof (a signature, a token in the body, a signed link).
- Rate limit: Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 20 requests a minute per IP address.

No router-level gate; the handler spends a nonce from the nonce route and verifies the Google credential. May create the account, then answers a single-use `handoff` code redeemed like any social sign-in. Answers 404 when One Tap is off for the method, 401 for an expired nonce, 400 for a credential Google does not confirm, and 403 when the sign-in is refused.

## Request

| Field      | Type   | Required | Constraints | Description |
| ---------- | ------ | -------- | ----------- | ----------- |
| `orgId`    | string | Yes      | -           | -           |
| `methodId` | string | Yes      | -           | -           |

Send the body as `application/json`.

| Field        | Type   | Required | Constraints                   | Description |
| ------------ | ------ | -------- | ----------------------------- | ----------- |
| `credential` | string | Yes      | 1 to 8192 characters          | -           |
| `nonce`      | string | Yes      | 1 to 128 characters           | -           |
| `challenge`  | string | Yes      | matches `^[A-Za-z0-9_-]{43}$` | -           |

## Example request

Replace each `YOUR_...` value with your own.

```bash title="cURL"
curl -X POST "https://api.console.buildbase.app/api/v1/auth/social/google/YOUR_ORG_ID/YOUR_METHOD_ID/one-tap" \
  -H "Content-Type: application/json" \
  -d '{
  "credential": "string",
  "nonce": "string",
  "challenge": "string"
}'
```

```ts title="TypeScript"
const response = await fetch(
  'https://api.console.buildbase.app/api/v1/auth/social/google/YOUR_ORG_ID/YOUR_METHOD_ID/one-tap',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      credential: 'string',
      nonce: 'string',
      challenge: 'string',
    }),
  }
);
if (!response.ok) {
  throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.text();
```

```python title="Python"
import requests

response = requests.post(
    "https://api.console.buildbase.app/api/v1/auth/social/google/YOUR_ORG_ID/YOUR_METHOD_ID/one-tap",
    json={
        "credential": "string",
        "nonce": "string",
        "challenge": "string",
    },
    timeout=30,
)
response.raise_for_status()
data = response.text
```

## Responses

A successful answer is not described yet. The server answers with the status and body its handler sends.

### Any other status

The handler's own answer. Not described yet: response bodies come from captured responses (server/openapi/captured) and overlays (server/openapi/overlays).

## Errors

Each refusal, what it means, and what to do. The request changed nothing.

### 400 Bad Request

**What it means:** The request failed a `validate()` schema, or an id in the path is not a valid id. `path` names the field.

**What to do:** Fix the field the body names in `path` (or read `message`) and send the request again. Nothing was changed.

```json title="Example"
{
  "error": true,
  "success": false,
  "path": "string",
  "message": "string"
}
```

### 404 Not Found

**What it means:** An id in the path names nothing in this org.

**What to do:** Check the ids in the path: one of them names nothing in this organization.

```json title="Example"
{
  "success": false,
  "message": "string"
}
```

### 429 Too Many Requests

**What it means:** A rate limit in `x-rateLimit` was reached. `retryAfter` and the `Retry-After` header say how many seconds until the window resets.

**What to do:** Wait the number of seconds in the `Retry-After` header (also `retryAfter` in the body), then retry. Slow down repeated calls.

```json title="Example"
{
  "success": false,
  "message": "string",
  "reason": "rate_limited",
  "retryAfter": 1
}
```

## Events

A successful call can send these [webhook events](/webhooks/overview) to the endpoints that subscribe to them:

- [`user.registered`](/webhooks/overview#when-each-event-fires)
- [`user.logged_in`](/webhooks/overview#when-each-event-fires)

## Related

- [Auth guide](/authentication/overview): how this part of BuildBase works
- [All Auth operations](/http-api/reference/auth)
- [API reference](/http-api/reference): every operation, by tag
- [Sign-in and credentials for the HTTP API](/http-api/authentication)
- [How the HTTP API reports errors](/http-api/errors)
- [Make your first call](/http-api/first-call)
- [Error codes](/reference/error-codes): every `code` the API returns
- OpenAPI: operation `auth.social.google.oneTap.create` in [public-v1.json](https://docs.buildbase.app/openapi/public-v1.json)
