Skip to main content
Two endpoints let your app add knowledge to a workspace without waiting for someone to paste a link: Both take the install token, like the rest of the API. The SDK client has no methods for them yet, so call them with fetch; declare the scope on any piece so the app asks for it. A self-hosted app passes the delivery’s installToken or one minted with its client credentials. On Reintersect hosting, the gateway sets the token on calls made during a delivery, so leave out authorization there.

Search objects

A search object is one of your objects, such as a task or an incident, made findable in Cmd+K. It belongs to one of your reference kinds that has a search function, so picking a result opens or references the same URL your patterns match.
The response is the stored object plus applied: false when Reintersect kept a newer copy. Delete an object with DELETE /v0/search/objects/:kind/:externalId (204). How results appear:
  • Results show in Cmd+K for members who may see them, with your app’s name, and open the object’s URL.
  • Objects from a development install are visible only to its developer.
  • When the app is uninstalled or suspended, its results disappear at once; Reintersect also reindexes live installs every night.
  • The Reintersect agent’s search doesn’t include app objects.

Memories

A memory is a short fact the Reintersect agent can recall later, such as “The Website project ships on Thursdays”. Your app can write one when something worth remembering happens in your system:
The endpoint answers 202 Accepted and Reintersect saves the memory in the background, credited to your app as its source. A development install stores every memory for its developer only. Each install can write 60 memories a minute; more fail with 429. Memories are only saved in workspaces that have agent memory on.

Errors

See the API reference for search objects and memories.