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

# Get Profile

> Manage the signed-in user's account settings

**CLI:**

```bash theme={null}
puffle account
```

## Overview

Returns the current user's account, billing summary, and safe stored profile context. The response includes:

* `account` - auth-owned identity fields such as `id`, `email`, and `fullName`.
* `profile` - `firstName`, `lastName`, company name/logo/website, company and personal LinkedIn URLs, and stored onboarding company/market/signals context when present.
* `billing` - the current plan and billing state available to the caller.
* `canManageAuth` - `true` only for a browser-session caller that is the signed-in user acting as themselves. Bearer API-key callers receive `false`.

## AI agent notes

Use this as the account-settings read before changing a user's profile name or when you need the stored company context returned with the account. Treat absent profile/context fields as unknown rather than inventing values. The public Bearer-token API can update `firstName` and `lastName`. Login email and password changes always require a signed-in human using a browser session; do not attempt them with an API key. If `canManageAuth` is `false`, direct the human to the dashboard rather than retrying.

This is not the company/ICP profile. Use [Get Company Profile](/api-reference/accounts/list-context) when you need GTM context for Feed and Lead Finder search preparation, reassessment, or outbound message generation.


## OpenAPI

````yaml get /api/account
openapi: 3.0.3
info:
  title: Puffle API
  version: 1.0.0
  description: >-
    HTTP API for the Puffle GTM platform - Feed and Lead Finder search
    preparation, campaign-backed Outbound execution, Puffle Agent runs, sender
    management, and Unibox reply workflows. Designed for operation by both
    humans and autonomous AI agents. Agents should start at the [Agent
    Playbook](/guides/agent-playbook) which prescribes a workspace-context check
    (`GET /api/context`) and core user journeys with exact call ordering.
  contact:
    name: Puffle Support
    url: https://puffle.ai
servers:
  - url: https://app.puffle.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Campaigns
    description: >-
      Campaign-backed Outbound execution. These endpoints manage draft,
      launching, active, paused, and completed Outbound runs with sequence
      nodes, contacts, and sender accounts.
  - name: Accounts
    description: Signed-in user account, settings, and workspace context endpoints.
  - name: Billing
    description: Billing customer portal and account billing endpoints.
  - name: Senders
    description: >-
      Connected sender accounts, email inboxes, sending domains, DNS
      verification, warmup, and sender capacity.
  - name: Socials
    description: >-
      Read connected LinkedIn and X accounts, review current and archived posts,
      and reconcile publication status. Creating, editing, scheduling,
      publishing, OAuth connection, analytics, and mentions remain
      dashboard-managed workflows and are not part of the public Bearer-token
      API.
paths:
  /api/account:
    get:
      tags:
        - Accounts
      summary: Get Profile
      description: >-
        Read the signed-in user's account settings, auth-management capability,
        current billing plan, and safe stored user profile/company context.
      operationId: getAccount
      parameters: []
      responses:
        '200':
          description: Successful response.
        '401':
          description: Unauthorized.
        '500':
          description: Internal server error.
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: pk_live_...

````