Resync common objects across a vertical
Response
Example response
{
"vertical": "ticketing",
"provider": "gitlab",
"status": "success"
}Changes
Changed in 6 of the 18 revisions of this API.3106
- ○
removed the
atsenum value from theverticalresponse property for the response status201response-property-enum-value-removed
- ○
removed the
hrisenum value from theverticalresponse property for the response status201response-property-enum-value-removed
This revision also has 42 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ●
added the new
accountingenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
atsenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
crmenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
ecommerceenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
failenum value to thestatusresponse property for the response status201response-property-enum-value-added
- ●
added the new
filestorageenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
hrisenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
marketingautomationenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
added the new
successenum value to thestatusresponse property for the response status201response-property-enum-value-added
- ●
added the new
ticketingenum value to theverticalresponse property for the response status201response-property-enum-value-added
- ●
- ▲
removed the success response with the status
200response-success-status-removed
- ○
added the success response with the status
201response-success-status-added
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
removed the success response with the status
201response-success-status-removed
- ○
added the success response with the status
200response-success-status-added
This revision also has 8 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
removed the success response with the status
200response-success-status-removed
- ○
added the media type
application/jsonfor the response with the status201response-media-type-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
added the success response with the status
201response-success-status-added
- ○