Writing Styles

POST /public/v1/writing-styles

Create a new writing style (status: PENDING). Populate dos and donts now or later via PATCH /public/v1/writing-styles/:id. A writing style needs rules before it can be linked to a campaign.

Required: workspaceId, name

Optional: dos, donts, connectInstructions, inmailInstructions, qna, templateName, templateFollowUpConfig, accessScope

accessScope:

  • OWNER (default) — private to the authenticated user
  • WORKSPACE — shared across the workspace; only ADMIN or OWNER members can set this
POST /public/v1/writing-styles

POST /public/v1/writing-styles

curl --request POST \
  --url 'https://api.joinvalley.co/public/v1/writing-styles' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "key": "value"
}'
{
  "statusCode": 1,
  "status": true,
  "message": "<string>",
  "data": {
    "writing_style": {
      "id": "<string>",
      "name": "<string>",
      "status": "<string>",
      "access_scope": "<string>",
      "created_at": "<string>"
    }
  }
}

Default Response

Authorizations

  • x-api-key string required header

    Your Valley API key.

Request Body

application/json
  • workspaceId string required

    ID of the workspace to create the writing style in.

  • name string required

    Display name for the writing style.

  • dos[] string array

    List of things the AI should do when writing in this style.

  • donts[] string array

    List of things the AI should avoid when writing in this style.

  • connectInstructions string

    Type any custom instructions here — tone preferences, message length guidelines, personalization rules, or any other direction for how your connect sequences should be written.

  • inmailInstructions string

    Type any custom instructions here — tone preferences, message length guidelines, personalization rules, or any other direction for how your InMail sequences should be written.

  • qna[] object array

    Optional Q&A pairs that give the AI additional context about your tone and preferences.

    + Show Child Attributes
    • question string required
    • answer string required
  • templateName string

    Optional template label (e.g. "Executive", "Startup") used to categorise the style.

  • templateFollowUpConfig object

    Follow-up timing config (days between touches). Keys are f_1 through f_10; use 0 to skip a step.

    + Show Child Attributes
    • f_1 integer default

      Default: 0.

    • f_2 integer default

      Default: 0.

    • f_3 integer default

      Default: 0.

    • f_4 integer default

      Default: 0.

    • f_5 integer default

      Default: 0.

    • f_6 integer default

      Default: 0.

    • f_7 integer default

      Default: 0.

    • f_8 integer default

      Default: 0.

    • f_9 integer default

      Default: 0.

    • f_10 integer default

      Default: 0.

  • accessScope string enum enum

    Who can use this writing style. OWNER = private to you; WORKSPACE = shared across the workspace (ADMIN/OWNER only). Allowed values: OWNER, WORKSPACE.

Response

application/json
  • statusCode number
  • status boolean
  • message string
  • data object
    + Show Child Attributes
    • writing_style object
      + Show Child Attributes
      • id string
      • name string
      • status string
      • access_scope string
      • created_at string