This page is for developers and administrators. If you create and edit presentations in the browser, start from the main Troubleshooting guide.
Cloud integrations
- Confirm the request uses the documented Cloud v3 base URL, method, path, content type, and a valid bearer token.
- Do not send self-hosted v1 payloads or authentication keys to Cloud endpoints.
- Record the sanitized request shape, HTTP status, response body, request identifier, and time of the failure.
- Treat asynchronous intermediate states as non-final, preserve the task identifier, and poll until it reaches a documented final state.
- Make webhook processing idempotent, deduplicate repeated deliveries, and return a successful response promptly after accepting an event.
Self-hosted integrations
- Confirm the request uses the v1 endpoints exposed by the installed release rather than Cloud v3 paths.
- Confirm the request sends an active
sk-presenton-...API key as a bearer token without logging or exposing it. - Generate a replacement key after administrator credential recovery, rotation, or suspected exposure.
- Confirm the MCP client can reach the Presenton host from its network environment; MCP is unavailable in the desktop app.
- Check application logs for route, authentication, validation, provider, rendering, and background-task failures.
- Retry with a minimal payload, then add files, templates, webhooks, and optional fields one at a time.