> ## Documentation Index
> Fetch the complete documentation index at: https://help.scribe-mail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create the Scribe account of the person the connector signed in



## OpenAPI

````yaml /api-reference/openapi.json post /v1/account
openapi: 3.0.1
info:
  title: Scribe Public API
  version: v1
  description: >-
    REST API to manage email signatures, teammates, smart fields, and marketing
    campaigns in your Scribe workspace. Every request uses JSON and is
    authenticated with a workspace API key. Endpoints are versioned under `/v1`,
    for example `https://api.scribe-mail.com/v1/signatures`.
  contact:
    name: Scribe Support
    url: https://help.scribe-mail.com/en
servers:
  - url: https://api.scribe-mail.com
    description: Production
security: []
tags:
  - name: Signatures
    description: >-
      Create, update, publish, and install email signature templates, and
      control which teammates each signature is assigned to.
  - name: Teammates
    description: >-
      Manage the people whose signatures Scribe deploys, and set their smart
      field values.
  - name: Emails
    description: >-
      Manage teammate email addresses, including the aliases that receive a
      signature.
  - name: Smart fields
    description: >-
      Define the dynamic fields, such as job title, phone number, or calendar
      link, that populate signatures.
  - name: Folders
    description: Organize signature templates into folders.
  - name: Assets
    description: >-
      Upload and manage the images and files used across signatures and
      campaigns.
  - name: Marketing campaigns
    description: >-
      Schedule, pause, and resume the promotional banners shown in your team's
      signatures.
  - name: Integrations
    description: >-
      List the directory, HRIS, and email integrations connected to your
      workspace.
  - name: Integration entities
    description: >-
      List the org units and groups from your connected integrations, used to
      target signatures.
  - name: Financial documents
    description: List the invoices and financial documents for your workspace.
paths:
  /v1/account:
    post:
      tags:
        - Account
      summary: Create the Scribe account of the person the connector signed in
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                accept_terms:
                  type: boolean
                  description: >-
                    Must be true: the person accepted the Terms and Conditions
                    and the Privacy Policy.
                time_zone:
                  type: string
                  description: The person's IANA time zone, when the agent knows it.
              required:
                - accept_terms
      responses:
        '201':
          description: Account created; the same token now reaches it
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/account_response'
        '401':
          description: An API key cannot sign anyone up
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error_response'
        '403':
          description: The signed-in email is not verified
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error_response'
        '409':
          description: 'The email''s domain belongs to a workspace: ask for an invitation'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error_response'
        '422':
          description: 'A personal address needs a company email: nothing is created'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/validation_error_response'
      security:
        - ApiKey: []
components:
  schemas:
    account_response:
      type: object
      properties:
        data:
          $ref: '#/components/schemas/account'
      required:
        - data
      additionalProperties: false
    error_response:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
            code:
              type: string
            message:
              type: string
          required:
            - type
            - code
            - message
          additionalProperties: false
        remediation:
          type: object
          description: >-
            Optional dashboard hand-off: where to send the user to unblock the
            request (e.g. connect an integration). Present on some 403/409
            responses.
          properties:
            action:
              type: string
              enum:
                - connect_integration
                - manage_in_dashboard
                - upgrade_plan
                - sign_up
            dashboard_url:
              type: string
              format: uri
            message:
              type: string
          required:
            - action
            - dashboard_url
            - message
          additionalProperties: false
      required:
        - error
      additionalProperties: false
    validation_error_response:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
            code:
              type: string
            message:
              type: string
          required:
            - type
            - code
            - message
          additionalProperties: false
        details:
          type: array
          items:
            type: object
            properties:
              field:
                type: string
              code:
                type: string
              message:
                type: string
              allowed:
                type: array
                description: >-
                  For an enum/const violation: the permitted values for this
                  field. Present only when the list is small enough to inline;
                  for large enums (e.g. icon) see the content schema.
                items: {}
              missing:
                type: array
                description: 'For a missing-required violation: the absent property names.'
                items:
                  type: string
            required:
              - field
              - code
              - message
            additionalProperties: false
      required:
        - error
        - details
      additionalProperties: false
    account:
      type: object
      properties:
        workspace:
          type: object
          properties:
            id:
              type: string
            name:
              type: string
              nullable: true
          required:
            - id
            - name
          additionalProperties: false
        user:
          type: object
          properties:
            email:
              type: string
            first_name:
              type: string
              nullable: true
            last_name:
              type: string
              nullable: true
          required:
            - email
            - first_name
            - last_name
          additionalProperties: false
        trial_ends_at:
          type: string
          nullable: true
      required:
        - workspace
        - user
        - trial_ends_at
      additionalProperties: false
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.