Nintex Xtensions Glossary
This topic lists terms frequently referenced in the Nintex Xtensions Development Guide.
-
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 a software platform can receive and respond to requests from other software platforms.
-
An predefined string passed in an API request, either inside the header or as a request parameter, to identify and/or authenticate the requester.
-
Confirming the identity of the person or service requesting access to a resource (Authorization) and confirming they have permission to complete that request (Authorization). These terms are often used interchangeably. Examples include username and passwords, API keys, and OAuth2.0 flows.
-
Identifying the API requestor using a username and password passed in the HTTP header.
-
The software that sends an API request, such as a web browser. Many clients can contact the same API.
-
A field in the action configuration panel that corresponds to a parameter or response property of the action's endpoint.
-
The stored authentication and authorization credentials for a connector.
-
A set of workflow actions defined for a specific third-party API such as Salesforce, Box, or another service provider. Nintex Automation Cloud provides many connectors out of the box, and you can create your own custom connectors using the Nintex Xtensions framework.
-
The URL of a specific resource provided by an API.
-
The domain name of the third-party API's URL.
-
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 or response that contains additional information such as authorization tokens or accepted content types.
-
The HTTP action to perform on the endpoint, such as GET, POST, DELETE, PUT. 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.
-
JavaScript Object Notation: a data format based on JavaScript that is commonly used for API request parameters and responses.
-
An authorization protocol that 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 single request to a third-party API. Operations often become actions in the workflow designer.
-
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.
-
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.
-
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 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.
-
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.
-
A cloud provider service that allows you to run code without provisioning and managing a web server 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.
-
A Nintex-specific OpenAPI Specification key that allows special functionality within Nintex Xtensions.
-
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.
-
A set of workflow actions defined for a specific third-party API such as Salesforce, Box, or another service provider. Nintex Automation Cloud provides many connectors out of the box, and you can create your own custom connectors using the Nintex Xtensions framework.
-
A human-readable file format similar to JSON that uses indentations instead of braces and brackets. OpenAPI Specifications provided by other service providers may sometimes be written in YAML instead of JSON. Nintex Xtensions supports JSON only.
A
B
C
E
H
J
O
P
Q
R
S
V
W
X
Y