create fact

The topic, template, or user could not be found in your workspace/organisation

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

The fact to create

Request body for creating a fact. Mirrors the fact representation: topic_id,
template_id (the template's uuid), and user_id are always required (the user must have an
active membership in the workspace's organisation), and the type-specific value goes in
the nested value object. justification, begins_at, and ends_at are accepted per
the template's configuration.

The value shape depends on response_type:

  • detail answers (number, currency, date, date_range, external, rich_text, unrestricted): { "response": "..." }
  • links (link_with_status): { "href": "...", "status": "approved" }
  • assessments: { "scale_value_id": 1 } (choice) or { "score": 3.2 } (multistep)
  • partnerships (stakeholder): { "stakeholder": "<uuid>", "role": "..." } or { "partner_user_id": 1, "role": "..." }

uuid
required

The UUID of the Fact Card to attach the fact to

string

Optional with a template uuid, which already implies it; when given it must match. Required with a legacy integer template_id.

uuid
required

The uuid of the template (scoped to your workspace). Deprecated: a legacy integer template id is still accepted together with response_type.

integer
required

The id of the user credited as the contributor (must be an active member of the organisation)

string | null
date | null

Start of the trust period (defaults to today)

date | null

End of the trust period (defaults to today + the template trust period)

value
object

The type-specific value; keys depend on response_type (see above).

Responses

Language
Credentials
Bearer
Token
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json