Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Running Apex
Debugging, Testing, and Deploying Apex
Debugging Apex
Testing Apex
Deploying Apex
Using Change Sets To Deploy Apex
Using the Salesforce Extensions for Visual Studio Code to Deploy Apex
Using the Ant Migration Tool to Deploy Changes
Using SOAP API to Deploy Apex
Distributing Apex Using Managed Packages
Apex Reference
Appendices
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Using SOAP API to Deploy Apex

These Salesforce Objects and SOAP API calls and headers 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.

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 61.0 , use endpoint 61.0: 
1https://MyDomain.salesforce.com/services/Soap/s/61.0
These Salesforce objects are available for Apex.
Use these SOAP API calls to deploy your Apex.

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.
Also see the Metadata API Developer Guide for two additional calls: