Skip to main content
Every deployed function is protected by default. Requests without a valid credential receive 401 Unauthorized.

Quick start

1

Deploy your function

The deploy doesn’t generate any credential automatically. To call your function you need a platform API key (see the next step).
2

Call with your API key

Create an API key at apps.jelou.ai, in the app configuration section, and send it in the Authorization header:
Successful response:
Without an API key or with an invalid one:

How it works

  1. Create a platform API key at apps.jelou.ai, in the app configuration section
  2. Every request must include it in the Authorization: Bearer sk_... header
  3. The SDK validates the key against the Jelou gateway, confirms it belongs to the same organization that owns the function, and caches the result in memory
  4. If the key is valid, the request reaches your handler. Otherwise, it returns 401
Creating new runtime tokens (jelou functions tokens create) is deprecated and responds 410 Gone. Deploys don’t generate one automatically either — the supported mechanism for authenticating functions, new or existing, is a platform API key.
Runtime tokens (jfn_rt_...) created before this migration are still validated via X-Jelou-Token (backwards compatible) and can be listed or revoked with jelou functions tokens list / jelou functions tokens revoke, but new ones can no longer be created and none are generated on new deploys.

Routes without authentication

The /__health and /openapi.json routes never require a credential. Cron triggers don’t either — the platform authenticates them automatically.

Usage examples

The platform does not validate anything — your code is responsible.