Source: Shawn Collins, Flikr

Google wants to give developers an easier time when creating apps and services. The company has announced a new Google Docs API which helps automations. Developers can leverage the API to preform tasks that they would otherwise have to handle manually.

The idea is for developers to automate laborious tasks and manually focus on more important ones. Called REST API, the solutions is now available for Google Docs. Using the API, dev’s can create automated tasks within the document creating/editing app.

Google has been developing REST API for some time, and it has been available in preview since last April. Rolling out to all developers this week, the API is focused on three areas: bulk document creation, workflow management, and building content management services.

“Many of the features that make Google Docs so successful are available through the API. This API lets you read and write documents programmatically so that you can integrate data from various sources leveraging the power of Google Docs.”

Among the capabilities for developers is the ability to set up automatic processes that update documents. For example, invoices that are created every month can be automated. REST API will automatically update the invoices to reflect dates and details.

Microsoft REST API Guidelines

Back in 2016, Microsoft published guidelines for REST API integrations. Creating the guidelines means all developers can have an easy way of using REST APIs with simple HTTP support. Microsoft says making the REST APIs follow “consistent design guidelines” is essential for having the most workable environment for developers. The guidelines help users understand how to make RESTful interfaces easily.

The guidelines were created to:

  • Define consistent practices and patterns for all REST endpoints across Microsoft.
  • Adhere as closely as possible to accepted REST/HTTP best practices in the industry at-large.
  • Make accessing Microsoft Services via REST interfaces easy for all application developers.
  • Allow service developers to leverage the prior work of other services to implement, test and document REST endpoints defined consistently.
  • Allow for partners (e.g., non-Microsoft entities) to use these guidelines for their own REST endpoint design.”