Use wide Google Slides API integration

With Ants & Apps platform you can connect Google Slides API with more than 30 available apps, 600+ functional formulas to boost your productivity

Reference

  • presentations

    • Get the latest version of the specified presentation

      This action gets the latest version of the specified presentation.

      GETSlidesPresentationsGet

      Request parameters

      • presentationId*string

        The ID of the presentation to retrieve.

    • Create a blank presentation using the title given in the request

      This action creates a blank presentation using the title given in the request. If a `presentationId` is provided, it is used as the ID of the new presentation. Otherwise, a new ID is generated. Other fields in the request, including any provided content, are ignored. Returns the created presentation.

      POSTSlidesPresentationsCreate

      Request body

      • presentationIdstring

        The ID of the presentation.

      • slidesarray

        The slides in the presentation. A slide inherits properties from a slide layout.

      • revisionIdstring

        The revision ID of the presentation. Can be used in update requests to assert that the presentation revision hasn't changed since the last read operation. Only populated if the user has edit access to the presentation. The format of the revision ID may change over time, so it should be treated opaquely. A returned revision ID is only guaranteed to be valid for 24 hours after it has been returned and cannot be shared across users. If the revision ID is unchanged between calls, then the presentation has not changed. Conversely, a changed ID (for the same presentation and user) usually means the presentation has been updated; however, a changed ID can also be due to internal factors such as ID format changes.

      • notesMasterobject

        The notes master in the presentation. It serves three purposes: - Placeholder shapes on a notes master contain the default text styles and shape properties of all placeholder shapes on notes pages. Specifically, a `SLIDE_IMAGE` placeholder shape contains the slide thumbnail, and a `BODY` placeholder shape contains the speaker notes. - The notes master page properties define the common page properties inherited by all notes pages. - Any other shapes on the notes master will appear on all notes pages. The notes master is read-only.

      • layoutsarray

        The layouts in the presentation. A layout is a template that determines how content is arranged and styled on the slides that inherit from that layout.

      • titlestring

        The title of the presentation.

      • localestring

        The locale of the presentation, as an IETF BCP 47 language tag.

      • mastersarray

        The slide masters in the presentation. A slide master contains all common page elements and the common properties for a set of layouts. They serve three purposes: - Placeholder shapes on a master contain the default text styles and shape properties of all placeholder shapes on pages that use that master. - The master page properties define the common page properties inherited by its layouts. - Any other shapes on the master slide will appear on all slides using that master, regardless of their layout.

      • pageSizeobject

        The size of pages in the presentation.

    • Apply one or more updates to the presentation

      This action applies one or more updates to the presentation. Each request is validated before being applied. If any request is not valid, then the entire request will fail and nothing will be applied. Some requests have replies to give you some information about how they are applied. Other requests do not need to return information; these each return an empty reply. The order of replies matches that of the requests. For example, suppose you call batchUpdate with four updates, and only the third one returns information. The response would have two empty replies: the reply to the third request, and another empty reply, in that order. Because other users may be editing the presentation, the presentation might not exactly reflect your changes: your changes may be altered with respect to collaborator changes. If there are no collaborators, the presentation should reflect your changes. In any case, the updates in your request are guaranteed to be applied together atomically.

      POSTSlidesPresentationsBatchUpdate

      Request parameters

      • presentationId*string

        The presentation to apply the updates to.

      Request body

      • writeControlobject

        Provides control over how write requests are executed.

      • requestsarray

        A list of updates to apply to the presentation.

  • presentations.pages

    • Get the latest version of the specified page in the presentation

      This action gets the latest version of the specified page in the presentation.

      GETSlidesPresentationsPagesGet

      Request parameters

      • presentationId*string

        The ID of the presentation to retrieve.

      • pageObjectId*string

        The object ID of the page to retrieve.

    • Generate a thumbnail of the latest version of the specified page in the presentation and returns a URL to the thumbnail image

      This action generates a thumbnail of the latest version of the specified page in the presentation and returns a URL to the thumbnail image. This request counts as an [expensive read request](/slides/limits) for quota purposes.

      GETSlidesPresentationsPagesGetThumbnail

      Request parameters

      • presentationId*string

        The ID of the presentation to retrieve.

      • pageObjectId*string

        The object ID of the page whose thumbnail to retrieve.

      • thumbnailProperties.mimeTypestring

        The optional mime type of the thumbnail image. If you don't specify the mime type, the default mime type will be PNG.

      • thumbnailProperties.thumbnailSizestring

        The optional thumbnail image size. If you don't specify the size, the server chooses a default size of the image.