You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/appstore/creating-content/connector-guide-build/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Connectors can be used in your app to simplify connecting to existing third-part
35
35
36
36
### Connecting to Other Systems
37
37
38
-
Connectors are implemented as Mendix modules with a focus on connecting to other systems. Connectors can make use of any of the platform-supported protocols like [SOAP](/refguide/consumed-web-services/#soap), [REST](/refguide/consumed-rest-services/#rest), [OData](/refguide/consumed-odata-services/#external-entities), or [Catalog](/catalog/).
38
+
Connectors are implemented as Mendix modules with a focus on connecting to other systems. Connectors can make use of any of the platform-supported protocols like [SOAP](/refguide/consumed-web-services/#soap), [REST](/refguide/integration/rest-services/), [OData](/refguide/consumed-odata-services/#external-entities), or [Catalog](/catalog/).
39
39
40
40
They can also be used to package a Java library provided by the other system to make the connection. These Java library functions can be exposed via Java actions as custom microflow activities (see [How to Build Microflow Actions with Java](/howto/extensibility/howto-connector-kit/)). This makes it simpler for Mendix developers without in-depth knowledge about third-party integrations to use these connectors in their business logic.
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/integration/rest-services/_index.md
+34-3Lines changed: 34 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,38 @@ Representational state transfer (REST) is an approach to consuming or exposing r
11
11
12
12
* HTTP URLs to locate resources
13
13
* HTTP headers to authenticate and specify content types (such as XML or JSON)
14
-
* HTTP methods to identify operations on resources, such as GET (retrieve data) or POST (send data)
14
+
* HTTP methods to identify operations on resources, such as `GET` (retrieve data) or `POST` (send data)
15
+
16
+
Lack of contracts and schemas give you an easy start to using REST. However, many REST endpoints return complex data.
17
+
18
+
The [JSON Structure](/refguide/json-structures/) document helps to give structure to JSON data. From an example JSON snippet, a lightweight schema is extracted that is used in [Mapping Documents](/refguide/mapping-documents/).
19
+
The [Import Mapping](/refguide/import-mappings/) document converts JSON (or XML) to Mendix objects, and the [Export Mapping](/refguide/export-mappings/) document serializes Mendix objects to JSON (or XML).
20
+
21
+
## Content Types {#content-types}
22
+
23
+
Content types are included in [custom HTTP headers](/refguide/call-rest-action/#custom-http-headers) to specify the output of the call, including media type or data format. For more information on content types, see [Content Negotiation in REST](https://restfulapi.net/content-negotiation/).
24
+
25
+
## JSON
26
+
27
+
JavaScript object notation (JSON) is a lightweight representation of data.
28
+
29
+
```js
30
+
{
31
+
"name":"John Smith",
32
+
"age":23,
33
+
"address":
34
+
{
35
+
"street":"Dopeylane 14",
36
+
"city":"Worchestire"
37
+
}
38
+
}
39
+
```
40
+
41
+
Above, the object `person` is described with the corresponding values for the attributes `name`, `age`, and the referred object `address`.
42
+
43
+
REST calls that output JSON need to declare the [content type](#content-types) as `application/JSON`.
44
+
45
+
## Documents in This Category
15
46
16
47
To publish REST services, see:
17
48
@@ -21,7 +52,7 @@ To publish REST services, see:
21
52
22
53
To consume REST services, see:
23
54
24
-
*[Consumed REST Services](/refguide/consumed-rest-services/), an overview in the Studio Pro guide
55
+
*[Consumed REST Services (Beta)](/refguide/consumed-rest-services-beta/), an overview on how to Consume a REST Service
25
56
*[Call REST Service](/refguide/call-rest-action/), a description of the microflow action
26
-
*[Consume a REST Service](/howto/integration/consume-a-rest-service/) for step-by-step instructions
57
+
*[Use Call REST Service Action in a Microflow](/refguide/integration/use-call-rest-action-in-microflow/), instructions on how to use the Call REST Service action in a microflow
27
58
*[HttpRequest and HttpResponse System Entities](/refguide/http-request-and-response-entities/), an overview of these system entities in your domain model
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/_index.md
+7-32Lines changed: 7 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,38 +6,13 @@ weight: 15
6
6
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
7
7
---
8
8
9
-
## REST {#rest}
9
+
## Consumed REST Services
10
10
11
-
Representational state transfer (REST) is an approach to consuming or exposing resources. It has gained popularity because of its simplicity, because no extensive schemas or contracts are needed to transfer data between endpoints. It uses the following:
11
+
The Consumed REST Service document allows you to interact with any REST API. You can build, test, and create data structures to store your REST requests.
12
12
13
-
* HTTP URLs to locate resources
14
-
* HTTP headers to authenticate and specify [content types](#content-types) (such as XML or JSON)
15
-
* HTTP methods to identify operations on resources, such as `GET` (retrieve data) or `POST` (send data)
13
+
## Documents in This Category
16
14
17
-
Lack of contracts and schemas give you an easy start to using REST. However, many REST endpoints return complex data.
18
-
19
-
The [JSON Structure](/refguide/json-structures/) document helps to give structure to JSON data. From an example JSON snippet, a lightweight schema is extracted that is used in [Mapping Documents](/refguide/mapping-documents/). The [Import Mapping](/refguide/import-mappings/) document converts JSON (or XML) to Mendix objects, and the [Export Mapping](/refguide/export-mappings/) document serializes Mendix objects to JSON (or XML).
20
-
21
-
### Content Types {#content-types}
22
-
23
-
Content types are included in [custom HTTP headers](/refguide/call-rest-action/#custom-http-headers) to specify the output of the call, including media type or data format. For more information on content types, see [Content Negotiation in REST](https://restfulapi.net/content-negotiation/).
24
-
25
-
## JSON
26
-
27
-
JavaScript object notation (JSON) is a lightweight representation of data.
28
-
29
-
```js
30
-
{
31
-
"name":"John Smith",
32
-
"age":23,
33
-
"address":
34
-
{
35
-
"street":"Dopeylane 14",
36
-
"city":"Worchestire"
37
-
}
38
-
}
39
-
```
40
-
41
-
Above, the object `person` is described with the corresponding values for the attributes `name`, `age`, and the referred object `address`.
42
-
43
-
REST calls that output JSON need to declare the [content type](#content-types) as `application/JSON`.
15
+
*[Consumed REST Services (Beta)](/refguide/consumed-rest-services-beta/), an overview on how to Consume a REST Service
16
+
*[Call REST Service](/refguide/call-rest-action/), a description of the microflow action
17
+
*[Use Call REST Service Action in a Microflow](/refguide/integration/use-call-rest-action-in-microflow/), instructions on how to use the Call REST Service action in a microflow
18
+
*[HttpRequest and HttpResponse System Entities](/refguide/http-request-and-response-entities/), an overview of these system entities in your domain model
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/use-call-rest-action-in-microflow.md
0 commit comments