Nintex Xtensions Glossary

This topic lists terms frequently referenced in the Nintex Xtensions Development Guide.

    A
  • A task that can be performed or triggered within a workflow, such as moving a file, sending an email, or using third-party API functionality.
  • A programming interface that defines how software can be interacted with by other software.
  • An authorization code passed in an API request, either inside the header or as a parameter, to identify the requester.
  • An authorization code passed in an API request, either inside the header or as a parameter, to identify the requester.
  • Identifying the requestor of the API using techniques such as a username and password, an API key, or OAuth2.0.
  • Identifying the requestor of the API using techniques such as a username and password, an API key, or OAuth2.0.
  • A service that allows you to run code without provisioning and managing a web serve to host it. Examples include Amazon Web Services and Microsoft Azure.
  • A service that allows you to run code without provisioning and managing a web serve to host it. Examples include Amazon Web Services and Microsoft Azure.
  • B
  • Identifying the API requestor using a username and password passed in the HTTP header.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • C
  • The software that sends an API request. Many clients can contact the same API.
  • A field representing the parameter or response of the endpoint when it is configured as a workflow action in the Workflow Designer.
  • The stored authorization credentials for a connector.
  • A set of instructions for Nintex Automation Cloud to use third-party API functionality with Nintex workflows. An Xtension may include workflow actions, start events, forms or file control.
  • A task that can be performed or triggered within a workflow, such as moving a file, sending an email, or using third-party API functionality.
  • A set of instructions for Nintex Automation Cloud to use third-party API functionality with Nintex workflows. An Xtension may include workflow actions, start events, forms or file control.
  • E
  • The address of a specific resource provided by the third-party API.
  • A task or occurrence that can trigger the start of a workflow, such as a form submission or third-party API event.
  • H
  • The section of the HTTP request that defines the operation of the request, including authorization.
  • The domain name of the third-party API's URL.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • The section of the HTTP request that defines the operation of the request, including authorization.
  • Hypertext Transfer Protocol: the protocol by which websites and APIs communicate over the internet.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • The section of the HTTP request that defines the operation of the request, including authorization.
  • The HTTP action to perform on the endpoint, such as GET, POST, DELETE, PUT. In defined inside the operation's path object in the OpenAPI specification.
  • Hypertext Transfer Protocol Secure: the protocol by which websites and APIs communicate securely over the internet.
  • J
  • JavaScript Object Notation: a data format based on JavaScript that is commonly used for API request parameters and responses.
  • L
  • A service that allows you to run code without provisioning and managing a web serve to host it. Examples include Amazon Web Services and Microsoft Azure.
  • O
  • A standard, language-agnostic description of RESTful APIs that can be read by both humans and machines. Formerly known as Swagger.
  • A two-step authorization protocol that both identifies the requestor, and allows a user to grant access to a third-party account without revealing their credentials to the requesting software.
  • A two-step authorization protocol that both identifies the requestor, and allows a user to grant access to a third-party account without revealing their credentials to the requesting software.
  • A two-step authorization protocol that both identifies the requestor, and allows a user to grant access to a third-party account without revealing their credentials to the requesting software.
  • A standard, language-agnostic description of RESTful APIs that can be read by both humans and machines. Formerly known as Swagger.
  • A standard, language-agnostic description of RESTful APIs that can be read by both humans and machines. Formerly known as Swagger.
  • A single request to a third-party API. Operations often become actions in the workflow designer.
  • P
  • A piece of information passed to a third-party API during a request.
  • The part of the URL after the hostname that directs the request to a specific resources within the host. For example, the section after "example.com" in http://example.com/this/is/a/path.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • Q
  • Part of the URL that does not fit into the path structure, and provides additional information or parameters for the request. The query is prefaced by a question mark (?) in the URL, for example: http://example.com?color=blue.
  • R
  • A seqence of symbols used to identify a particular pattern or piece of text within a larger body of text. Often used to validate input, such as valid URLs or email addresses.
  • A seqence of symbols used to identify a particular pattern or piece of text within a larger body of text. Often used to validate input, such as valid URLs or email addresses.
  • An attempt to use a feature or operation of a third-party API.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • The section of the HTTP request that defines the operation of the request, including authorization.
  • The return from a third-party API after a request has been made by the client.
  • The part of an HTTP request or response that can contain an arbitrary amount of data, such as the content of a form or web page.
  • The section of the HTTP request that defines the operation of the request, including authorization.
  • Representational State Transfer: a style of software architecture that separates state and functionality into distributed resources, with each resource uniquely addressable, typically using HTTP commands. RESTful applications are usually stateless and support caching.
  • Representational State Transfer: a style of software architecture that separates state and functionality into distributed resources, with each resource uniquely addressable, typically using HTTP commands. RESTful applications are usually stateless and support caching.
  • S
  • A service that allows you to run code without provisioning and managing a web serve to host it. Examples include Amazon Web Services and Microsoft Azure.
  • A Nintex-specific OpenAPI Specification key that allows special functionality within Nintex Xtensions.
  • A task or occurrence that can trigger the start of a workflow, such as a form submission or third-party API event.
  • A standard, language-agnostic description of RESTful APIs that can be read by both humans and machines. Formerly known as Swagger.
  • T
  • A task or occurrence that can trigger the start of a workflow, such as a form submission or third-party API event.
  • V
  • A Nintex-specific OpenAPI Specification key that allows special functionality within Nintex Xtensions.
  • W
  • An endpoint of an API that can be configured to call a user-defined URL when something occurs within the API's platform. Also known as a user-defined callback or reverse API.
  • X
  • A set of instructions for Nintex Automation Cloud to use third-party API functionality with Nintex workflows. An Xtension may include workflow actions, start events, forms or file control.
  • Y
  • A subset of the human-readable JSON format that uses indentations instead of braces and brackets. YAML can be readily converted into JSON. Nintex Xtensions supports JSON only.