@microsoft/msgraph-sdk-teams/teams/item/schedule/index.d.ts

Teams fluent API for Microsoft Graph

import { type Schedule } from '@microsoft/msgraph-sdk/models/index.js';
import { type DayNotesRequestBuilder } from './dayNotes/index.js';
import { type OfferShiftRequestsRequestBuilder } from './offerShiftRequests/index.js';
import { type OpenShiftChangeRequestsRequestBuilder } from './openShiftChangeRequests/index.js';
import { type OpenShiftsRequestBuilder } from './openShifts/index.js';
import { type SchedulingGroupsRequestBuilder } from './schedulingGroups/index.js';
import { type ShareRequestBuilder } from './share/index.js';
import { type ShiftsRequestBuilder } from './shifts/index.js';
import { type SwapShiftsChangeRequestsRequestBuilder } from './swapShiftsChangeRequests/index.js';
import { type TimeCardsRequestBuilder } from './timeCards/index.js';
import { type TimeOffReasonsRequestBuilder } from './timeOffReasons/index.js';
import { type TimeOffRequestsRequestBuilder } from './timeOffRequests/index.js';
import { type TimesOffRequestBuilder } from './timesOff/index.js';
import { type BaseRequestBuilder, type KeysToExcludeForNavigationMetadata, type NavigationMetadata, type RequestConfiguration, type RequestInformation, type RequestsMetadata } from '@microsoft/kiota-abstractions';
/**
 * Provides operations to manage the schedule property of the microsoft.graph.team entity.
 */
export interface ScheduleRequestBuilder extends BaseRequestBuilder<ScheduleRequestBuilder> {
    /**
     * Provides operations to manage the dayNotes property of the microsoft.graph.schedule entity.
     */
    get dayNotes(): DayNotesRequestBuilder;
    /**
     * Provides operations to manage the offerShiftRequests property of the microsoft.graph.schedule entity.
     */
    get offerShiftRequests(): OfferShiftRequestsRequestBuilder;
    /**
     * Provides operations to manage the openShiftChangeRequests property of the microsoft.graph.schedule entity.
     */
    get openShiftChangeRequests(): OpenShiftChangeRequestsRequestBuilder;
    /**
     * Provides operations to manage the openShifts property of the microsoft.graph.schedule entity.
     */
    get openShifts(): OpenShiftsRequestBuilder;
    /**
     * Provides operations to manage the schedulingGroups property of the microsoft.graph.schedule entity.
     */
    get schedulingGroups(): SchedulingGroupsRequestBuilder;
    /**
     * Provides operations to call the share method.
     */
    get share(): ShareRequestBuilder;
    /**
     * Provides operations to manage the shifts property of the microsoft.graph.schedule entity.
     */
    get shifts(): ShiftsRequestBuilder;
    /**
     * Provides operations to manage the swapShiftsChangeRequests property of the microsoft.graph.schedule entity.
     */
    get swapShiftsChangeRequests(): SwapShiftsChangeRequestsRequestBuilder;
    /**
     * Provides operations to manage the timeCards property of the microsoft.graph.schedule entity.
     */
    get timeCards(): TimeCardsRequestBuilder;
    /**
     * Provides operations to manage the timeOffReasons property of the microsoft.graph.schedule entity.
     */
    get timeOffReasons(): TimeOffReasonsRequestBuilder;
    /**
     * Provides operations to manage the timeOffRequests property of the microsoft.graph.schedule entity.
     */
    get timeOffRequests(): TimeOffRequestsRequestBuilder;
    /**
     * Provides operations to manage the timesOff property of the microsoft.graph.schedule entity.
     */
    get timesOff(): TimesOffRequestBuilder;
    /**
     * Delete navigation property schedule for teams
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @throws {ODataError} error when the service returns a 4XX or 5XX status code
     */
    delete(requestConfiguration?: RequestConfiguration<object> | undefined): Promise<void>;
    /**
     * Retrieve the properties and relationships of a schedule object. The schedule creation process conforms to the One API guideline for resource based long running operations (RELO).When clients use the PUT method, if the schedule is provisioned, the operation updates the schedule; otherwise, the operation starts the schedule provisioning process in the background. During schedule provisioning, clients can use the GET method to get the schedule and look at the provisionStatus property for the current state of the provisioning. If the provisioning failed, clients can get additional information from the provisionStatusCode property. Clients can also inspect the configuration of the schedule.
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @returns {Promise<Schedule>}
     * @throws {ODataError} error when the service returns a 4XX or 5XX status code
     * @see {@link https://learn.microsoft.com/graph/api/schedule-get?view=graph-rest-1.0|Find more info here}
     */
    get(requestConfiguration?: RequestConfiguration<ScheduleRequestBuilderGetQueryParameters> | undefined): Promise<Schedule | undefined>;
    /**
     * Create or replace a schedule object. The schedule creation process conforms to the One API guideline for resource based long running operations (RELO).When clients use the PUT method, if the schedule is provisioned, the operation replaces the schedule; otherwise, the operation starts the schedule provisioning process in the background. During schedule provisioning, clients can use the GET method to get the schedule and look at the provisionStatus property for the current state of the provisioning. If the provisioning failed, clients can get additional information from the provisionStatusCode property. Clients can also inspect the configuration of the schedule.
     * @param body The request body
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @returns {Promise<Schedule>}
     * @throws {ODataError} error when the service returns a 4XX or 5XX status code
     * @see {@link https://learn.microsoft.com/graph/api/team-put-schedule?view=graph-rest-1.0|Find more info here}
     */
    put(body: Schedule, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<Schedule | undefined>;
    /**
     * Delete navigation property schedule for teams
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @returns {RequestInformation}
     */
    toDeleteRequestInformation(requestConfiguration?: RequestConfiguration<object> | undefined): RequestInformation;
    /**
     * Retrieve the properties and relationships of a schedule object. The schedule creation process conforms to the One API guideline for resource based long running operations (RELO).When clients use the PUT method, if the schedule is provisioned, the operation updates the schedule; otherwise, the operation starts the schedule provisioning process in the background. During schedule provisioning, clients can use the GET method to get the schedule and look at the provisionStatus property for the current state of the provisioning. If the provisioning failed, clients can get additional information from the provisionStatusCode property. Clients can also inspect the configuration of the schedule.
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @returns {RequestInformation}
     */
    toGetRequestInformation(requestConfiguration?: RequestConfiguration<ScheduleRequestBuilderGetQueryParameters> | undefined): RequestInformation;
    /**
     * Create or replace a schedule object. The schedule creation process conforms to the One API guideline for resource based long running operations (RELO).When clients use the PUT method, if the schedule is provisioned, the operation replaces the schedule; otherwise, the operation starts the schedule provisioning process in the background. During schedule provisioning, clients can use the GET method to get the schedule and look at the provisionStatus property for the current state of the provisioning. If the provisioning failed, clients can get additional information from the provisionStatusCode property. Clients can also inspect the configuration of the schedule.
     * @param body The request body
     * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
     * @returns {RequestInformation}
     */
    toPutRequestInformation(body: Schedule, requestConfiguration?: RequestConfiguration<object> | undefined): RequestInformation;
}
/**
 * Retrieve the properties and relationships of a schedule object. The schedule creation process conforms to the One API guideline for resource based long running operations (RELO).When clients use the PUT method, if the schedule is provisioned, the operation updates the schedule; otherwise, the operation starts the schedule provisioning process in the background. During schedule provisioning, clients can use the GET method to get the schedule and look at the provisionStatus property for the current state of the provisioning. If the provisioning failed, clients can get additional information from the provisionStatusCode property. Clients can also inspect the configuration of the schedule.
 */
export interface ScheduleRequestBuilderGetQueryParameters {
    /**
     * Expand related entities
     */
    expand?: string[];
    /**
     * Select properties to be returned
     */
    select?: string[];
}
/**
 * Uri template for the request builder.
 */
export declare const ScheduleRequestBuilderUriTemplate = "{+baseurl}/teams/{team%2Did}/schedule{?%24expand,%24select}";
/**
 * Metadata for all the navigation properties in the request builder.
 */
export declare const ScheduleRequestBuilderNavigationMetadata: Record<Exclude<keyof ScheduleRequestBuilder, KeysToExcludeForNavigationMetadata>, NavigationMetadata>;
/**
 * Metadata for all the requests in the request builder.
 */
export declare const ScheduleRequestBuilderRequestsMetadata: RequestsMetadata;
//# sourceMappingURL=index.d.ts.map