PUT /v2-edge/vendors/{vendorId} only returning error 500

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PUT /v2-edge/vendors/{vendorId} only returning error 500

L1 Bithead

We are trying to update vendors start/enddate through the api but seem to be unable to perform any calls towards the modify vendor endpoint. No matter what we send in the body the api always return error 500.

According to Swagger UI (alero.eu) it should be possible to only send start and end date as no attribute is required.

 

Is anyone getting PUT /v2-edge/vendors/{vendorId} to work?

 

See below for example bodies.

 

{

"accessStartDate": 1714694400000,

"accessEndDate": 1724386777000

}

 

{

"accessStartDate": 1714694400000,

"accessEndDate": 1724386777000,

"canInvite": false,

"invitedVendorsInitialStatus" : "Activated",

"maxNumOfInvitedVendors": 0,

"provisioningType": "ProvisionedByAlero",

"username": "VendorUser123",

"groups": ["[group id]"],

"comments":"test",

"applications": [

   {

     "siteId": "[site id]",

     "applicationId": "[app id]"

   }

],

"pvwaApplications":false

}

 

1 accepted solution

Accepted Solutions

L6 Presenter

Hello,

 

You found the answer yourself, but the reason is because this is an HTTP PUT operation, which replaces an entire resource. If there were a PATCH endpoint, you could push only the updates required.

View solution in original post

3 REPLIES 3

L1 Bithead

Update:

The following seemed to work but why are all attributes mandatory?

 

{

 "accessStartDate": 1724198400000,

 "accessEndDate": 1724371199001,

 "canInvite": false,

 "invitedVendorsInitialStatus": "Activated",

 "maxNumInvitedVendors": 0,

 "provisioningType": "ProvisionedByAlero",

 "username": "",

 "groups": [

   ""

 ],

 "comments": "test",

 "applications": [

   {

     "siteId": "",

     "applicationId": ""

   }

 ],

 "pvwaApplications": true

}

L6 Presenter

Hello,

 

You found the answer yourself, but the reason is because this is an HTTP PUT operation, which replaces an entire resource. If there were a PATCH endpoint, you could push only the updates required.

L1 Bithead

Hi,

 

Makes sense. I may have overlooked that part during my troubleshoot.

 

Thanks

  • 1 accepted solution
  • 148 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!