Skip to main content

API Access Fails After Logout

Question​

> My developer calls the K3 API to retrieve configuration data. After logging out, the call no longer works. Apparently, a login token was used for API access.

Answer​

The login token (session token) is intended for internal editor access and expires after logging out or after a certain period of time. It is not suitable for programmatic API access in the frontend or in integrations.

Use the Correct Endpoint​

There is a dedicated, token-free API endpoint for publicly retrieving configuration data:

GET https://d2mb1ky72vpspf.cloudfront.net/assets/data/current/{APP-CODE}.de.json

This endpoint is publicly accessible and does not require a login token. It returns the app’s complete configuration data.

Where can I find the app code?​

Editor → Options → App Code.

Secure vs. Public Endpoint

K3 distinguishes between internal endpoints (login required, for the Editor) and the public app endpoint (no token required, for integrations and frontends). Always use the public endpoint for programmatic access.

Further Information​

  • API Authentication
  • Session Token Expired
  • Retrieving Configuration Data via the API