SDKs
Minimal SDK implementations that wrap the essentials — JWT signing, request dispatch, and back-off after a 429. Copy one into your project as a starting point, or use it as a reference while building your own.
Full SDKs are being built in the open at mymindcorp/api. They're not ready yet — until they are, the snippets on this page are the canonical reference. Contributions welcome.
Before you start
You need an access key. Create one on your Extensions page and keep the kid and base64 secret on hand — the secret is shown only once. See Authentication for the full key format and lifecycle.
What each SDK demonstrates
- Identification — every request sets the required
User-Agentheader naming the integration. Requests without one are rejected. - Signing — generates a fresh JWT bound to the request's method and path. See Authentication for the full token format.
- Two sample calls —
createObjectandgetObject. Every other resource method follows the same shape. - Back-off — after a
429, the SDK records when the slowest exhausted window will reset and delays the next outbound request until that point. See Rate Limits for the header format.
Example JavaScript SDK
Use the language picker in the sidebar to switch.
Where to next
With your SDK wired up, head to Objects for the full set of resource methods, then Spaces, Tags, and Search to extend it. For the gritty details on what to do when something goes wrong, see Error Handling.