Documentation
Documentation

Overview

Spore docs

Start here

Getting startedInstall the CLIAuthentication and keys

Build

Search and filtersSegments and the loopEnrichment lifecycle

Recipes

Recipe: search to a live SegmentRecipe: enrich without a segmentRecipe: land your own research

Connect

Events

Account

Credits and billing

Reference

Conventions
API reference
Export the organization's Operation calls POSTPage the organization's Operation calls GETExport the organization's recorded acts POSTPage the organization's recorded acts GETCancel an enrichment launch POSTRead a vocabulary: tools, filters, knowledge, or NACE GETPublish a staged Commons Generation POSTRestore the retained previous Commons Generation POSTPage the organization's Companies GETCorrect a Company's Core under Spore-If-Match PATCHDelete a Company DELETERead everything you know about one Company GETRead Legal entity data for Companies you hold POSTFind Legal entities in the Commons POSTFold one Company into another POSTMint Companies from your own data, or attach rows to Companies you hold POSTPromote a declared current Fact into Company Core POSTRead one Company GETMeasure requested fields over a set of Companies POSTRun a native enrichment POSTPoll an enrichment GETFollow the organization's durable events stream GETPage a Job's frozen target list GETCreate an API key and reveal its secret once POSTRevoke an organization API key POSTList per-item enrichment outcomes GETDeclare a namespace and its fields before recording into them POSTDelete a declaration while nothing stands on it DELETERead your Catalog GETRecord what you observed about a Company or concluded about a Segment POSTUnlock every Legal entity a search matched POSTSearch the Commons: count, analytics, and a minted sample POSTPage a Segment's members, with the exact count GETName a live filter over your Companies POSTDelete a Segment DELETERead what you have concluded about one Segment GETRename a Segment, or change what it means, under Spore-If-Match PATCHRead a Segment's name and filter GETPage the organization's Segments GETPage the organization's credit ledger GETRead the balance and this key's spend bounds GET
API reference

Delete a Segment

Hard, and refused without `confirm=true`, reporting how much reduce knowledge it would remove. Echo that count as `reduceFacts` when confirming to refuse deletion if it changed. Company Facts are never touched: they belong to the Companies, not to the set that named them. Free.

DELETE
/api/v1/segments/{segmentId}

Hard, and refused without confirm=true, reporting how much reduce knowledge it would remove. Echo that count as reduceFacts when confirming to refuse deletion if it changed. Company Facts are never touched: they belong to the Companies, not to the set that named them.

Free.

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

segmentId*string

The Segment.

Formatuuid

Query Parameters

confirm?string

Set to true to delete; deletion is permanent and is refused without it.

Default"false"

Value in

  • "true"
  • "false"
reduceFacts?integer

The reduce-Fact count quoted by an earlier unconfirmed delete. When supplied, deletion is refused if the count changed.

Range0 <= value

Header Parameters

Idempotency-Key*string

Required for writes. Reusing this key with the same input replays the original response.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/api/v1/segments/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "Idempotency-Key: string"
{  "id": "7f9c2a14-3b6e-4d51-9a2f-1c8e5b0d47a3",  "reduceFacts": 0}

Name a live filter over your Companies POST

Stores a name and a filter, and nothing else. Members are whichever Companies match when you ask, so there is no count here, no snapshot, and no refresh: editing the filter changes membership immediately. Every field the filter names is validated against your own vocabulary — Core, your Catalog, and the registry field map — and an undeclared name is refused. Creating a Segment evaluates nothing. Free.

Read what you have concluded about one Segment GET

Returns the current value of every field this organization has recorded about the Segment itself — reduce knowledge, the conclusions that are about the set rather than about any one member — each with who recorded it, when, the evidence behind it including the Jobs it was reduced from, whether its declaration's freshness has lapsed, and the full history underneath. Members' own Facts are read per Company; `POST /coverage` is the door that asks what a set is missing. Free.