Explore the API Reference

Once you know what a Nyckel function is and you’ve built one end-to-end, the API reference becomes a quick lookup rather than a manual to read front to back.

The full reference

API Reference — complete REST API: every endpoint, parameter, request shape, response shape, error code, and example.

What to look for first

If you’re integrating Nyckel into a real application, the endpoints you’ll touch most are:

• Invoke — make predictions. The single endpoint your application code calls in the hot path.
• Annotations — send corrections and confirmations back to Nyckel from your application or downstream tools.
• Samples — list, add, or update training samples programmatically (useful for bulk operations and back-office tooling).
• Functions — create, list, or update functions themselves (useful for provisioning environments or running the same function shape in dev and prod).

SDKs and code snippets

Every function in the Nyckel console has an Integrate tab that generates ready-to-copy code for the language you’re using. Start there for the exact request shape — it’s less ambiguous than reading the generic reference and translating it.

Next

• Developer Platform — architecture and patterns for production use.
• Build Production Workflows — opinionated guidance on how to integrate.