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/apidocs-mxsdk/apidocs/marketplace/content-api.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,10 @@
1
1
---
2
-
title: "Content API"
3
-
linktitle: "Marketplace Content"
2
+
title: "Marketplace Content API"
4
3
url: /apidocs-mxsdk/apidocs/content-api/
5
4
type: swagger
6
5
description: "The Content API accesses both public and company-specific Marketplace content information."
7
6
restapi: true
8
-
weight: 45
7
+
weight: 10
9
8
---
10
9
11
10
## Introduction
@@ -22,7 +21,7 @@ If you have Marketplace content, this API can help you get the following informa
22
21
23
22
### Generating a PAT
24
23
25
-
For details on how to generate a PAT, see the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
24
+
For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
26
25
27
26
Select at least the following as the **Marketplace** scope:
28
27
@@ -39,7 +38,7 @@ GET /content HTTP/1.1
39
38
Authorization: MxToken 7LJE…vk
40
39
```
41
40
42
-
To authenticate calls when using the OpenAPI specification below, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
41
+
To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
description: "The Publish API accesses both public and company-specific Marketplace content information."
6
+
restapi: true
7
+
weight: 20
8
+
---
9
+
10
+
## Introduction
11
+
12
+
The Mendix Publish API allows you to publish components to Marketplace.
13
+
14
+
{{% alert color="warning" %}}
15
+
You can currently only publish new releases of existing components.
16
+
{{% /alert %}}
17
+
18
+
## Authentication {#authentication}
19
+
20
+
### Generating a PAT
21
+
22
+
For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
23
+
24
+
Select at least the following as the **Marketplace** scope:
25
+
26
+
*`mx:marketplace:write`
27
+
28
+
Store the generated value `{GENERATED_PAT}` somewhere safe so you can use it to authorize your Content API calls.
29
+
30
+
### Using the PAT
31
+
32
+
Each request must contain an `Authorization` header with the value `MxToken {GENERATED_PAT}`. Here is an example:
33
+
34
+
```http
35
+
GET /content HTTP/1.1
36
+
Authorization: MxToken 7LJE…vk
37
+
```
38
+
39
+
To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/overview/component-details.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
@@ -22,7 +22,7 @@ The header for a component includes the following details:
22
22
***Recommended**: If the header contains this label, it means that the component meets your company's policies and guidelines, and therefore is recommended by your Mendix Admins.
23
23
24
24
* The name of the component
25
-
***Save** – Click this to add the component to your [Saved Content](/appstore/home-page/#personal) list.
25
+
***Save** – Click this to add the component to your **Saved** list.
26
26
* Depending on the content type:
27
27
28
28
***Use in Studio Pro** for modules and widgets – Click this to copy the content ID so that you can [search for and use the component in Studio Pro](/appstore/use-content/#current-sp).
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/overview/marketplace-home-page.md
+15-10Lines changed: 15 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The search box at the top of the page allows you to explore the Mendix Marketpla
29
29
You can refine search results using the following filters:
30
30
31
31
***Support** – Select between the available support categories. For details, see the [Marketplace Content Support](/appstore/marketplace-content-support/).
32
-
***Visibility** – Choose whether you want to display [publicor private](/appstore/submit-content/#support-licensing) content.
32
+
***Visibility** – Choose whether you want to display public, private, or company components.
33
33
***Content Types** – Choose the type of content to display. For details, see the [Types of Marketplace Components](/appstore/#components-type) section in *Marketplace*.
34
34
***Category** – Select specific domains in which components or services share characteristics, functions, or purposes.
35
35
***Industry** – Select specific sectors or business domains in which components or services are used.
@@ -40,9 +40,13 @@ You can refine search results using the following filters:
40
40
For details on finding and installing Marketplace content in Studio Pro, see the [Finding and Downloading Content in Studio Pro](/appstore/use-content/#downloading) section of *Using Marketplace Content*.
41
41
{{% /alert %}}
42
42
43
-
## Personal {#personal}
43
+
## Manage Components
44
44
45
-
The **Personal** category contains the items described in the following sections.
45
+
The **Manage Components** category contains the items described in the following sections.
46
+
47
+
## Published
48
+
49
+
This page includes all your published components
46
50
47
51
### Drafts {#my-drafts}
48
52
@@ -142,13 +146,14 @@ You can configure content groups for various levels of access to your company co
142
146
143
147
This table breaks down the roles and permissions for content groups:
144
148
145
-
| Roles | Manage Groups (Create & Delete) | Manage Group Members | Assign Content to Group | Manage Content (Add New Release, Manage Versions) | View & Download Group Content | View Group List |
| Organization member (not part of any group) | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ |
151
-
| Guest | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
149
+
| Roles | Manage groups (create & delete) | Manage group members | Assign content to group | Manage content (Add new release, manage releases) | View & download group content | View group list | Manage drafts |
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/upload-content/_index.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,8 +218,7 @@ To update content that has already been published, follow these steps:
218
218
219
219
1. Find the component in one of the following sections:
220
220
221
-
***My Content**
222
-
***Company Content**
221
+
***Published**
223
222
***Content Group**
224
223
{{% alert color="info" %}}If an existing Marketplace component is assigned to a [content group](/appstore/home-page/#content-groups) as specific content group [content](/appstore/home-page/#group-content), you can only update the component if you are a member of that group.{{% /alert %}}
225
224
@@ -229,8 +228,6 @@ To update content that has already been published, follow these steps:
229
228
***Manage Versions** – This option gives you access to the **Edit** and **Unpublish** actions for each version of the component.
230
229
***Unpublish Component**
231
230
232
-
{{% alert color="info" %}}Only one draft version of a component can exist at a time, so when one draft version is in progress, another draft cannot be started. If there is a draft version in progress, click **Edit Draft** on the page where you manage the component in order to see the draft.{{% /alert %}}
233
-
234
231
3. You can edit all component details, as described in the [Adding New Marketplace Content](#adding) section above.
235
232
4. In the **Version** section of the **Package** page, update the **Major**, **Minor**, and **Patch** numbers so that the component is saved as a new version:
0 commit comments