---
title: "Dippr Handoff Token"
method: POST
path: "/auth/dippr/handoff-token"
tags: ["AUTH"]
---

# Dippr Handoff Token

`POST /auth/dippr/handoff-token`

## Request

- Base URL: `https://api.myaltimate.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.myaltimate.com/auth/dippr/handoff-token`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
- TypeScript: <https://skmtc.dev/myaltimate/apis/myaltimate-api/docs/auth/dippr/handoff-token/post.ts> (a function with typed inputs; its response is checked against the schema)

Mint the short-lived ticket /connect hands to Dippr for a current Owner.

It proves who the user is to the Altimate IdP and nothing more: only
/auth/dippr/redeem accepts it, for identity claims. Unlike connect-token it
leaves ``pending_social_jti`` alone, so it never cancels a CLI or social
sign-in in flight; the IdP enforces single use.

## Headers

- `x-tenant` string

## Response `200`

Successful Response

- object

## Other responses

- `401`: Not authenticated, or the instance is deactivated.
- `403`: This account cannot sign in to Dippr.
- `422`: Validation Error

## Changes

- **2026-11-03** `868dfab8c7fe`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/myaltimate/apis/myaltimate-api/changes/auth/dippr/handoff-token/post.md)

---

[API](https://skmtc.dev/myaltimate/apis/myaltimate-api.md) - [All operations](https://skmtc.dev/myaltimate/apis/myaltimate-api/llms.txt) - [OpenAPI document](https://skmtc.dev/myaltimate/apis/myaltimate-api/revisions/01c038028180?raw)