# FAQs (/docs/docklee/faqs)
## Getting started [#getting-started]

<Accordions type="single">
<Accordion title="Which languages does the SDK support?">
Python 3.9 and later, and TypeScript on Node.js 18 and later. The TypeScript SDK also works from plain JavaScript. Both install as `docklee`, from PyPI and npm. Any other language can call the REST API directly with an API key.
</Accordion>

<Accordion title="Can one API key use both knowledge and memory?">
Yes. A key can reach Knowledge Engines, DUM, or both, and you choose its capability: `read`, `write`, or `both`. See [API keys](/docs/docklee/api-keys).
</Accordion>

<Accordion title="Can I call Docklee from a browser or mobile app?">
No. An API key must stay on your server. Call Docklee from your backend and send the results to your client.
</Accordion>

<Accordion title="Should I use query or retrieve?">
Use `lynk.query` when you want Docklee to write the answer, with citations. Use `lynk.retrieve` when you run your own model and only need the ranked chunks to put in its prompt.
</Accordion>
</Accordions>

## Writing data [#writing-data]

<Accordions type="single">
<Accordion title="Do I need to name an engine when I write knowledge?">
No. A write declares a container, `vector` or `okf`, never an engine. You then link the container's API/SDK Feed source to the engines that should read it. See [Containers](/docs/docklee/containers).
</Accordion>

<Accordion title="Why can my engine not find data I just wrote?">
Check that the container's **API/SDK Feed** source is linked to the engine in its **Sources** tab. An engine reads only the sources linked to it. Also check that `Dock` was flushed or closed, so the buffered events were sent.
</Accordion>

<Accordion title="When does Dock send my data?">
`Dock` buffers captures and sends a batch when the buffer reaches 10 events, or when you call `flush`. In TypeScript it also sends every 5 seconds. Call `flush_sync()` or `await dock.close()` in Python, or `await dock.close()` in TypeScript, before your process exits.
</Accordion>

<Accordion title="What happens if a batch fails to send?">
With `flush_sync()` in Python and `flush()` in TypeScript, the events go back into the buffer and are sent with the next flush. Both return the batch result when the request succeeds and `None` or `null` when it fails, so you can check it in code.
</Accordion>

<Accordion title="Why was an event rejected as a duplicate?">
Identical content sent again within 60 seconds is skipped. Pass a `dedup_key` (Python) or `dedupKey` (TypeScript) to decide yourself what counts as the same event.
</Accordion>
</Accordions>

## Reading data [#reading-data]

<Accordions type="single">
<Accordion title="Why does recall return nothing?">
The most common cause is a multi-user space recalled without an `end_user`. Once a space holds any end user memory, a recall must name the end user. Also check the memory space ID and that your key's scope includes the space. See [End users](/docs/docklee/end-users).
</Accordion>

<Accordion title="Can one recall search several memory spaces?">
`lynk.recall` reads one memory space per call. To search several at once, call `POST /v1/dum/federated-search` with up to 10 `memory_space_ids`. Spaces your key can't reach are skipped, and the results are merged and ranked together.
</Accordion>

<Accordion title="Does the SDK retry failed requests?">
Yes. It retries timeouts, connection errors, and the statuses `408`, `409`, `429`, `500`, `502`, `503`, and `504`, up to 3 times by default, waiting longer before each retry. Set `max_retries` (Python) or `maxRetries` (TypeScript) to change the limit. Requests time out after 30 seconds unless you set `timeout`.
</Accordion>
</Accordions>

## Next steps [#next-steps]

<Cards>
  <Card title="Quickstart" href="/docs/docklee/quickstart" description="Store a memory and query your knowledge." />
  <Card title="How Docklee works" href="/docs/docklee/how-docklee-works" description="Where each write goes and how it is read." />
  <Card title="API keys" href="/docs/docklee/api-keys" description="Capability, runtimes, scope, and rotation." />
</Cards>
