Get all calendars

get

/fscmRestApi/resources/11.13.18.05/calendars

Request

Query Parameters
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds a calendar that matches the primary key.
      Finder Variables
      • CalendarCode; string; Code for the calendar primary key finder.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • Calendar; string; Name of the workday calendar.
    • CalendarCode; string; Unique identifier for the calendar in the source system.
    • CalendarCodeName; string; Name of the unique identifier for the calendar in the source system.
    • CalendarDaysOff; integer; Number of consecutive nonworking days.
    • CalendarDaysOn; integer; Number of consecutive working days.
    • Description; string; Description of the calendar.
    • EndDate; string; End date for the calendar.
    • ExceptionEndDate; string; Last date till which any exception in the calendar is valid. The last date must be within the calendar start date and end date, both inclusive.
    • ExceptionStartDate; string; Start date from which any exception in the calendar is valid. The start date must be within the calendar start date and end date, both inclusive.
    • ExceptionType; integer; Code for the exception type. Valid values are 1 for On and 2 for Off.
    • ExceptionTypeName; string; Status of the exception type. Valid values are Available and Not Available.
    • QuarterlyCalTypeName; string; Name of the quarterly calendar type.
    • QuarterlyCalendarType; integer; Quarterly calendar type code. Valid values are 1 for 445 week pattern, 2 for 544 week pattern, 3 for 13 periods for the calendar year, 4 for regular months of the calendar year, and 5 for 454 week pattern.
    • Sequence; integer; Sequence number for working days in the calendar.
    • SourceSystem; string; Alphanumeric code used to identify the source system.
    • StartDate; string; Beginning date for the calendar.
    • WeekStartDay; integer; The day from which the calendar pattern string begins. Valid values are 1 for pattern string starts on a Monday, 2 for pattern string starts on the same day of the week on which the calendar start date falls.
    • WeekStartDayName; string; Name of the week start day.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : calendars
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : calendars-item-response
Type: object
Show Source
  • Title: Calendar
    Read Only: true
    Maximum Length: 255
    Name of the workday calendar.
  • Title: ID
    Read Only: true
    Maximum Length: 32
    Unique identifier for the calendar in the source system.
  • Title: Calendar Code
    Read Only: true
    Maximum Length: 32
    Name of the unique identifier for the calendar in the source system.
  • Title: Days Off
    Read Only: true
    Number of consecutive nonworking days.
  • Title: Days On
    Read Only: true
    Number of consecutive working days.
  • Title: Description
    Read Only: true
    Maximum Length: 250
    Description of the calendar.
  • Title: End Date
    Read Only: true
    End date for the calendar.
  • Title: Exception End Date
    Read Only: true
    Last date till which any exception in the calendar is valid. The last date must be within the calendar start date and end date, both inclusive.
  • Title: Exception Start Date
    Read Only: true
    Start date from which any exception in the calendar is valid. The start date must be within the calendar start date and end date, both inclusive.
  • Title: Exception Type Code
    Read Only: true
    Code for the exception type. Valid values are 1 for On and 2 for Off.
  • Title: Exception Type
    Read Only: true
    Maximum Length: 250
    Status of the exception type. Valid values are Available and Not Available.
  • Links
  • Title: Quarterly Type Code
    Read Only: true
    Quarterly calendar type code. Valid values are 1 for 445 week pattern, 2 for 544 week pattern, 3 for 13 periods for the calendar year, 4 for regular months of the calendar year, and 5 for 454 week pattern.
  • Title: Quarterly Type
    Read Only: true
    Maximum Length: 4000
    Name of the quarterly calendar type.
  • Title: Sequence
    Read Only: true
    Sequence number for working days in the calendar.
  • Title: Source System
    Read Only: true
    Maximum Length: 30
    Alphanumeric code used to identify the source system.
  • Title: Start Date
    Read Only: true
    Beginning date for the calendar.
  • Title: Weekly Start Day Code
    Read Only: true
    The day from which the calendar pattern string begins. Valid values are 1 for pattern string starts on a Monday, 2 for pattern string starts on the same day of the week on which the calendar start date falls.
  • Title: Week Start Day
    Read Only: true
    Maximum Length: 250
    Name of the week start day.
Back to Top