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

# Start an attachment (member token)

> The member-token twin of [Start a card attachment](/companies/api/reference/attach-start): same rows, same hosted page, authenticated as the member instead of naming them with `user_id`. In sandbox this seeds an instantly-active test enrollment so the full flow is rehearsable without a browser.

The member-token twin of
[Start a card attachment](/companies/api/reference/attach-start): same
attachment rows, same hosted page, authenticated as the member instead of
naming them with `user_id`.

In sandbox this seeds an instantly-active test enrollment, so an agent can
rehearse the whole add-then-create flow with no browser step.


## OpenAPI

````yaml openapi.json POST /api/v2/attach
openapi: 3.1.0
info:
  title: Agentcard API
  version: 2.0.0
  description: >-
    The Agentcard v2 API — connect your users and verify their identity from
    your own backend. Every call is authenticated with a platform access token
    minted from your `client_id` + `client_secret`.
servers:
  - url: https://api.agentcard.sh
    description: >-
      There is one base URL. Sandbox vs production is decided by the client
      credential you use, never by the host.
security:
  - platformToken: []
tags:
  - name: Authentication
    description: >-
      Exchange your client credentials for a platform access token, and
      introspect what a token acts as.
  - name: Connect
    description: >-
      Connect a user to your platform: send a one-time code, verify it, record
      consent, and keep the connection alive.
  - name: Identity verification
    description: >-
      Verify a connected user's identity: upload their ID, submit any extra
      fields we ask for, then show a short face scan.
  - name: Wallet funding
    description: >-
      Fund a connected user's wallet from your own UI — request a payment link,
      relay the phone verification code, and poll until the funds land.
  - name: Withdrawals
    description: >-
      Move money out of a connected user's wallet — to a saved bank account or a
      crypto address on Base. Transfers are processed manually by the Agentcard
      team, usually within 1-3 business days.
paths:
  /api/v2/attach:
    post:
      tags:
        - Member cards
      summary: Start an attachment (member token)
      description: >-
        The member-token twin of [Start a card
        attachment](/companies/api/reference/attach-start): same rows, same
        hosted page, authenticated as the member instead of naming them with
        `user_id`. In sandbox this seeds an instantly-active test enrollment so
        the full flow is rehearsable without a browser.
      operationId: memberAttachStart
      responses:
        '200':
          description: A card is already attached.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CardAttachment'
        '201':
          description: >-
            The attachment. `pending` carries `attach_url` for the member to
            finish; `active` means an existing enrollment was adopted with no
            ceremony.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CardAttachment'
              example:
                object: card_attachment
                id: ca_123
                status: pending
                attach_url: https://app.agentcard.sh/attach/TOKEN
                expires_at: '2026-08-25T00:00:00.000Z'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          description: >-
            `attach_unavailable`: adding cards is not available for this
            organization.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            `user_info_required`: record consent first (POST
            /api/v2/connect/consent).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - userAccessToken: []
components:
  schemas:
    CardAttachment:
      type: object
      properties:
        object:
          type: string
          enum:
            - card_attachment
        id:
          type: string
          description: The attachment id.
        user_id:
          type: string
        status:
          type: string
          enum:
            - pending
            - active
            - ineligible
          description: >-
            `pending` — the user has not finished the attach link. `active` —
            attached; `create_card` now mints against this card. `ineligible` —
            this card cannot be attached; fall back to wallet funding +
            `create_card`.
        attach_url:
          type: string
          description: >-
            The hosted link the user opens to add their card. Present only on
            the start response.
        expires_at:
          type: string
          format: date-time
          description: >-
            When the attach link expires (48 hours). Present only on the start
            response.
        card:
          type: object
          description: >-
            Display details of the attached card. Present when status is
            `active`.
          properties:
            network:
              type: string
              nullable: true
            brand:
              type: string
              nullable: true
            last4:
              type: string
              nullable: true
            art_url:
              type: string
              nullable: true
        reason:
          type: string
          description: >-
            Why the card cannot be attached (e.g. `issuer_excluded`,
            `commercial_card`). Present when status is `ineligible`.
        message:
          type: string
          description: Human-readable guidance. Present when status is `ineligible`.
      required:
        - object
        - id
        - user_id
        - status
    Error:
      type: object
      description: Every v2 error uses the same envelope.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              description: A stable, machine-readable string (snake_case). Branch on this.
            message:
              type: string
              description: A human-readable explanation, safe to log.
            docs:
              type: string
              description: A link back to the reference.
            field_errors:
              type: object
              additionalProperties:
                type: string
              description: Only on `invalid_fields` — names each field to fix.
            warnings:
              type: array
              items:
                type: string
              description: >-
                Only on document upload errors — actionable feedback safe to
                show the user.
  responses:
    Unauthorized:
      description: >-
        `unauthorized` — the platform access token is missing or expired.
        Exchange your client credentials for a fresh one.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    platformToken:
      type: http
      scheme: bearer
      description: >-
        A platform access token. Get one on the **Create an access token**
        endpoint by exchanging your `client_id` + `client_secret`, then send it
        as `Authorization: Bearer <token>`. Tokens live one hour.
    userAccessToken:
      type: http
      scheme: bearer
      description: >-
        The user's connection access_token (user authentication), or an
        org-minted buy_token for org-owned accounts.

````