Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> in airbyte open version  0.44 isthere a an api to descriobe cron expressions, the expression is available in 1.4 version but not in 0.4

The knowledge sources only document a **cron describe API for Airbyte Embedded / ai-agents**, not for the Airbyte Open Source 0.44 platform.  - The documented endpoint is:    ```http   POST <https://api.airbyte.ai/api/v1/integrations/templates/connections/cron/describe>   ```    which validates and returns a human‑readable description of a Quartz cron expression, but this is part of the **Embedded connection templates API**, not the OSS core API.[[Connection templates](<https://docs.airbyte.com/ai-agents/embedded/api/connection-templates#configuration-options>); [Describe cron](<https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-templates-connections-cron-describe>)]  - For OSS / platform sync schedules, the docs only describe how to *use* cron expressions (Quartz format) in connection schedules; they do **not** mention any “describe cron” or validation endpoint in the OSS API for versions 0.4x or 1.x.[[Sync schedules](<https://docs.airbyte.com/platform/using-airbyte/core-concepts/sync-schedules>)]  Given this, I’m not seeing any evidence in the provided sources that **Airbyte Open Source v0.44** exposes an API to describe cron expressions. The “describe cron” endpoint you’re referring to appears to be specific to the Embedded API, not to OSS 0.44.  If you need cron help on OSS 0.44, based on these docs you would have to validate/describe the cron expression externally (e.g., Quartz docs or a generator) rather than via an OSS API.

You’re right: the **cron describe** endpoint that *is* documented does require authentication.  For Airbyte Embedded / AI Agents, the endpoint is:  ```http POST <https://api.airbyte.ai/api/v1/integrations/templates/connections/cron/describe> ```  and it **“requires an Access Token as the bearer token”** in the `Authorization` header.[[Describe cron](<https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-templates-connections-cron-describe>)]  Example (from the connection templates docs):  ```bash curl -X POST <https://api.airbyte.ai/api/v1/integrations/templates/connections/cron/describe> \   -H 'Authorization: Bearer &lt;token&gt;' \   -H 'Content-Type: application/json' \   -d '{     "cron_expression": "0 0 12 * * ?"   }' ```  This is the only cron-describe API mentioned in the provided sources, and it’s part of the **Embedded** API, not the OSS 0.44 core API.[[Connection templates](<https://docs.airbyte.com/ai-agents/embedded/api/connection-templates#configuration-options>)]