Using SOAP API to Deploy Apex

These are SOAP API calls, objects, and headers that are available by default for Apex. For information on all other SOAP API calls, including those that can be used to extend or implement any existing Apex IDEs, contact your Salesforce representative.

Apex class methods can be exposed as custom SOAP Web service calls. This allows an external application to invoke an Apex Web service to perform an action in Salesforce. Use the webservice keyword to define these methods. For more information, see Considerations for Using the webservice Keyword.

Note

Any Apex code saved using SOAP API calls uses the same version of SOAP API as the endpoint of the request. For example, if you want to use SOAP API version 52.0, use endpoint 52.0:

1https://yourInstance.salesforce.com/services/Soap/s/52.0

The following API objects are available for Apex. For more information, see the SOAP API Developer Guide.

Use these SOAP API calls to deploy your Apex. For more information, see the SOAP API Developer Guide.

All these calls take Apex code that contains the class or trigger, as well as the values for any fields that need to be set.

These SOAP headers are available in SOAP API calls for Apex. For more information, see the SOAP API Developer Guide.

Also see the Metadata API Developer Guide for two additional calls:

Apex Developer Guide

Using SOAP API to Deploy Apex