Step 1 — Create an API key
- Sign in to Recallio and open API Keys.
- Generate a key with the Contributor role (or Manager if you also plan to run delete operations).
- Copy the value now—keys are only shown once. You will use it as the bearer token for every Graph Memory request.
Step 2 — (Optional) Set up projects
Create projects in Settings → Projects if you support multiple environments (for example, different homes). You will pass theproject_id with every graph payload to keep relationships scoped correctly.
Step 3 — Prepare a graph payload
Graph Memory accepts free-form JSON or text in thedata field. The service extracts entities and relationships automatically.
Tip: Include descriptive field names so Recallio can infer meaningful relationships (for example, resident, technician, property).
Step 4 — Add entities and relationships
InvokePOST /api/GraphMemory/addv2 to ingest the payload.
201 Created response containing the entities and relationships that were added.
Step 5 — Search the graph
UsePOST /api/GraphMemory/searchv2 to retrieve connected context for assistant prompts.
source, relationship, destination, and a similarity score.
Step 6 — Inspect relationships (optional)
Confirm the graph by listing all edges for the same scope.Step 7 — Reset data (optional)
When you need a clean slate, call the delete endpoint with a Manager key.Next steps
- Review the Graph Memory Overview for a feature summary.
- Dive into the Graph Memory Deep Dive to learn schema details, ranking controls, and governance patterns.
- Explore every field in the Recallio Swagger reference.

