---
title: "Create outcome series"
method: POST
path: "/api/v1/business/outcome-series/create"
tags: ["business"]
---

# Create outcome series

`POST /api/v1/business/outcome-series/create`

## Request

- Base URL: `https://point11.ai`
- URL: `https://point11.ai/api/v1/business/outcome-series/create`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://auth.point11.ai/oauth2/authorize`, token URL `https://auth.point11.ai/oauth2/token`)

Add an empty imported series to Outcomes, then send its days with business_outcome_series_values_import. Name it (unique in the organization) and say what a day's value is: kind "total" adds over days (sales, orders, leads), "level" is a reading at the day's end (active subscribers); unit "currency" (with its ISO 4217 code) or "count"; split "channel" when each day carries what AI assistants referred (ai) and the rest (other), else "none". Days are calendar days as the data dates them; every value is a day's total, never a person.

## Headers

- `Point11-Organization` string, uuid
- `Idempotency-Key` string, uuid, required

## Request body

- BusinessOutcomeSeriesCreateRequest
  - `origin` 'custom' | 'crm_import'
  - `name` string, required
  - `kind` 'total' | 'level', required
  - `unit` 'currency' | 'count' | 'percent', required
  - `currencyCode` string, nullable
  - `split` 'none' | 'channel'
  - `definition` string, nullable

## Response `200`

Success.

- BusinessOutcomeSeriesCreateResponse
  - `id` string, uuid, required
  - `origin` 'custom' | 'crm_import' | 'crm_sync', required
  - `name` string, required
  - `kind` 'total' | 'level', required
  - `unit` 'currency' | 'count' | 'percent', required
  - `currencyCode` string, nullable, required
  - `split` 'none' | 'channel', required
  - `definition` string, nullable, required
  - `createdAt` string, required
  - `valuesUpdatedAt` string, nullable, required
  - `firstDate` string, nullable, required
  - `lastDate` string, nullable, required
  - `days` integer, required
  - `crm` object, nullable, required
    - `syncId` string, uuid, required
    - `measure` 'deals' | 'revenue', required

## Other responses

- `400`: The input, query, or Idempotency-Key is invalid.
- `401`: The bearer is missing, expired, or not accepted.
- `402`: Billing refused the write: the code names the reason and `details.reason` carries it.
- `403`: The credential lacks the operation's scope or role, or the operation needs a different door.
- `404`: The resource or organization does not exist for this caller.
- `405`: This path takes another HTTP method, named in `Allow`.
- `409`: The request conflicts with current state or with prior use of its Idempotency-Key.
- `413`: The request, or the answer it asks for, is too large; narrow it.
- `429`: The credential's rate budget is spent; retry after `Retry-After` seconds.
- `500`: An unexpected server failure; retry later. Only `request_id` identifies it.
- `503`: A dependency is temporarily unavailable; retry after `Retry-After` seconds.
- `default`: Another status a product answers for its own refusal (for example `415` for an unsupported attachment); branch on `code`.

---

[API](https://skmtc.dev/point11/apis/point11-api.md) · [All operations](https://skmtc.dev/point11/apis/point11-api/llms.txt) · [OpenAPI document](https://skmtc.dev/point11/apis/point11-api/revisions/36a84c7aca11?raw)