Versions Compared

Old Version 3

changes.mady.by.user Brian Miller

Saved on

compared with

New Version Current

changes.mady.by.user Rose Yntema

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

Overview

Swagger is an interactive documentation system that also allows you to conveniently try out & make REST API calls from the documentation page itself.   

...

The Swagger REST API Documentation page should open as shown below. The REST endpoints are organized based on a system of repositories, containers, artifacts, and relations (see Conceptual Model for an overview).

...

To

...

Login

The sign-in request authenticates the user and returns a token if succesful. The token is then used for every REST API request to the Syndeia Cloud server. Follow the steps below to sign-in and register the token so that you do not have to specify it for each request. 

...

9.  Paste the copied token (previous step) in the Value field, and then click the Authorize button, followed by clicking the Done button.
   

To

...

Create a

...

New User



10.  Click on POST /signUp button, 

11.  Click the Try it out button.  The "User info for signUp" fields should show up.  
     ​

12.  Click the Edit button.  The field should now become editable.  

13.  Fill out the requested fields, ie: first name, last name, email, password.  

14.  Click the blue Execute button.  

15.  If successful, you should receive an HTTP 200 response back with JSON data.  If there was a form error, you should receive an HTTP 4XX response back with an appropriate error message.  

...

To

...

Reset a

...

Password

16.  Click on POST /resetpassword button, 

...


(info) Note, Reset Password is considered an admin-level operation that requires the USER_MODIFY permission.  This is distinct from the Change Password operation which does not require any permission and only applies to one's own password.  

To Update a User (Permissions)

1722.  Click on PUT GET /api/v1/users/email/{keyemail} button, 
18
23.  Click the Try it out button.  The "User info that needs to be updated" fields should show up.  
     Image Added
24.  Fill out the requested field, ie: email.    

25.  Click the blue Execute button.  

26.  If successful, you should receive an HTTP 200 response back with JSON data.  If there was a form error, you should receive an HTTP 4XX response back with an appropriate error message.

27.  Copy the key value
      Image Added
28.  Click on PUT /api/v1/users/{key} button, 

29.  Click the Try it out button.  The "Get user" fields should show up.  
     

1930.  Click the Edit button.  The field should now become editable.  

2031.  Fill out the requested fields, ie: key, firstName, lastName, permissions.    

       (info) Currently the following permissions are available:


USER_CREATE

Create user permission

USER_READ

User read permission

USER_MODIFY

User modification permission

USER_REMOVE

User remove permission

REPOSITORY_CREATE

Create repository permission

REPOSITORY_MODIFY

Repository modification permission

REPOSITORY_DELETE

Repository deletion permission

CONTAINER_CREATE

Create container permission

CONTAINER_MODIFY

Container modification permission

ARTIFACT_RELATION_WRITE

Artifact relation write permission

CONTAINER_DELETE

Container deletion permission

READ

General read permission


32.  Click the blue Execute button.  

33.  If successful, you should receive an HTTP 200 response back with JSON data.  If there was a form error, you should receive an HTTP 4XX response back with an appropriate error message.

To Delete a User

34.  Click on GET /api/v1/users/email/{email}
35.  Click the Try it out button.  The "User info that needs to be updated" fields should show up.  
     Image Added
36.  Fill out the requested field, ie: email.    

37.  Click the blue Execute button.  

38.  If successful, you should receive an HTTP 200 response back with JSON data.  If there was a form error, you should receive an HTTP 4XX response back with an appropriate error message.

39.  Copy the key value
      Image Added
40.  Click on DELETE /api/v1/users/{key} button, 

41.  Click the Try it out button.  The "Delete a user given the user key" field should show up.  
     Image Added

42.  Fill out the requested field, ie: key.   

43.  Click the blue Execute button.  

44.  If successful, you should receive an HTTP 200 response back with JSON data.  If there was a form error, you should receive an HTTP 4XX response back with an appropriate error message.