/skill-schedules

Foundational GET all handler for: skill-schedules
This is used to define any schedules that are set-up to run a Skill by a given user.

This is set to run the skill as if it is the user who initiated it.

The format for the skill schedule is a crontab format.
ID: NUMBER: This is the Primary Key (Numeric) of the Skill Schedule
AI_CONVERSATIONS_ID: NUMBER: This is the conversation that this Skill Scheduler runs as
SKILL_INPUT: JSON: This is used to track a JSON input to the Skill if applicable
ACTIVE: NUMBER: This indicates if this Skill Schedule is currently active or not
SCHEDULE: VARCHAR2(255): This is the interval that this skill runs asThis is stored in the format of crontab: https:wwwibmcomdocseniastopictask-unix-cron-format
DESCRIPTION: CLOB: This is used to describe this Skill Schedule for record-keeping
AI_SKILLS_ID: NUMBER: This is the Skill that is run according to the Crontab schedule
CEPHISSO_PLATFORM_ACCOUNTS_ID: NUMBER: This is the Sphere that this scheduler is stored in
CEPHISSO_PLATFORM_USERS_ID: NUMBER: This is the user that this skill will run asUnless impersonation enabled by an admin this is always the creating the admin
SYSTEM_GUID: VARCHAR2(36): This is used to track a unique identifier for a system specificaly a System GUID generated by SYSGUID()
UUID: VARCHAR2(36): This is the UUID for this record
METADATA: JSON: This is a JSON metadata field
DATA_LINEAGE: JSON: This field includes any specifications about where the source system is any external identifier time last updated etc
UDFS: JSON: This is used to track the UDFs (User Defined Fields) that might get added
CREATED_ON: DATE: The Date-time that this record was created
CREATED_BY: VARCHAR2(255): The User ID of the user account that created this record
LAST_UPDATED_ON: DATE: This is the Date-time when this record was Last Updated
LAST_UPDATED_BY: VARCHAR2(255): The User ID of the user account who last updated this record

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Request

Responses