Skip to content

by Startups.Studio

Holder.create

POST /{namespace}/holders

Creates a Holder.

Noun: Holder
Mode: do
Event: Holder.created

You, to your agent

Add a holder to TutorLoop with a party.

curl -X POST https://api.sb/tutorloop.com/holders \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"party":"party_1"}'

import { $ } from 'startup-builder'

const holder = await $.Holder.create({ party: 'party_1' })

npx startup-builder do Holder.create --json '{"party":"party_1"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Holder.create({ party: 'party_1' })"
  }
}

Create makes a new Holder from the inputs below. It is inherited: every Noun has get, list, create, update and delete.

Inputs

Input	Type	Required	Description
`party`	Party	required	The person or entity behind the holding.

Outputs

Output	Type	Required	Description
`holder`	Holder	required	The Holder.

Effects

Emits Holder.created.
Two-way: try, send, do.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Holder.create

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Holder

Previous Page

Holder.get

Next Page