Reeve.Memory

What it does

• Your app can use the memory feature if it was approved for it when it was first set up, or if it's later granted access by an administrator. To actually use it, each request still needs valid credentials, and access can be limited or blocked if your account or organization has been restricted.

Getting started

1. Get the memory capability for your host app, either approved at setup or granted later by an administrator. It is not on by default.
2. Authenticate with your Reeve host key (X-Reeve-Host-Key) to call the Reeve.Memory surface.
3. Make your first request and check the response, then wire it into your app.

Limits & notes

• Requests authorize on your organization; a valid host key scoped to this capability is required.

FAQ

What does Reeve.Memory do?

Your app can use the memory feature if it was approved for it when it was first set up, or if it's later granted access by an administrator. To actually use it, each request still needs valid credentials, and access can be limited or blocked if your account or organization has been restricted.

Sources

2 of 7 claims on this page are grounded in the Reeve.Knowledge product corpus. The rest are product/catalog reference copy with no Knowledge card behind them, listed as uncited below.

• does.0 — [source]
• faqs.0.a — [source]
• overview — uncited (reference copy)
• how_to.0 — uncited (reference copy)
• how_to.1 — uncited (reference copy)
• how_to.2 — uncited (reference copy)
• limits.0 — uncited (reference copy)