SugarCRM REST API Activities
- Creating and editing a SugarCRM REST API endpoint
SugarCRM Rest API endpoints contain the connection information that studio and the Integration Appliance use to connect to the SugarCRM Server via Rest API. You can create multiple endpoints that refer to separate instances. - Using the SugarCRM REST API Get UserInfo activity
Use the SugarCRM REST API Get UserInfo activity to retrieve user information such as userId, userTeamId, and so on from the SugarCRM server. - Using the SugarCRM REST API Get ServerInfo activity
Use the SugarCRM REST API Get ServerInfo activity to retrieve server information such as flavor, version, and GMT time from the SugarCRM server. - Using the SugarCRM REST API Get Reports activity
Use the SugarCRM REST API Get Reports activity to retrieve specific reports from the SugarCRM server. - Using the SugarCRM REST API Create Object activity
Use the SugarCRM REST API Create Object activity to create objects in the SugarCRM REST API instance. - Using the SugarCRM REST API Get Objects activity
Use the SugarCRM REST API Get Objects activity to get objects from the SugarCRM server. - Using the SugarCRM REST API Delete Object activity
Use the SugarCRM REST API Delete Object activity to delete objects from the SugarCRM REST API server. - Using the SugarCRM REST API Update Object activity
Use the SugarCRM REST API Update Object activity to update objects in the SugarCRM instance. - Using the SugarCRM REST API Search activity
Use the SugarCRM REST API Search activity to search for objects from specified records. This activity searches for details based on a query. - Specifying the Retry options for SugarCRM REST API activities
Specifying the Retry parameters is one of the tasks to configure a SugarCRM REST API activity. The SugarCRM REST API connector uses a single login session for all connections to an SugarCRM REST API endpoint. If a session expires, the connector automatically establishes a new session. The connector does not count the initial attempt to reacquiring the session as a retry attempt. The connector assumes the typical connector retry behavior after the initial attempt to reacquire a session fails.