Guide

This guide takes you through the REST resources and operations included with the Nintex Forms for Office 365 REST API, providing examples that you can use in Visual Studio 2013.

What is REST?

Representational State Transfer (REST) is a methodology for implementing scalable web services. REST emphasizes a stateless, cacheable implementation with a uniform interface, typically accessed using Hypertext Transfer Protocol (HTTP). The REST service decouples the client from the server, by providing access to REST resources, each of which is accessed by using a Universal Resource Identifier (URI) that identifies that particular REST resource.

A REST resource is typically accessed by using HTTP methods, such as GET and PUT, to send and receive self-descriptive messages between the client and the REST service. These messages are typically expressed using Hypertext Markup Language (HTML), Expressive Markup Language (XML), or JavaScript Object Notation (JSON). The messages are self-descriptive in that each message includes enough information to describe how to process the message, and contains representations of information with which the client or the REST resource can interact. For example, the Nintex Forms for Office 365 REST API does not connect a client directly to Nintex Forms for Office 365, but instead serves as an intermediary between the two, interacting with representations of information, such as forms and export files, exchanged in such messages.

The combination of a REST resource and an HTTP method typically identifies a specific operation that can be performed for the information represented by that REST resource. Multiple HTTP methods are often used with a particular REST resource to represent different operations that can be performed for the information represented by that REST resource.

For example, to export an existing form from Nintex Forms for Office 365to a client for a fictional customer named Crestan, the following REST resource is invoked, using the HTTP GET method:

https://crestan.nintexo365.com/api/v1/forms/fd4f1cd2-7ea7-4b62-9751-0ff83ab609f7

However, invoking the very same REST resource and using the HTTP POST method allows the client to import a form file, overwriting the form inNintex Forms for Office 365 for the list. HTTP methods allow REST to avoid ambiguity when interacting with REST resources.

What can I do with the REST API?

The REST API includes the following REST resources:

Related information

Nintex Forms O365 Quick Start

API Reference