ISVforce Guide
jNewer Version Available
API Access in Group and Professional Editions
API access is not normally supported in GE and PE orgs. However, after your app passes
the security review, you’re eligible to use some APIs for building composite
applications.
- Currently, the standard Data SOAP and REST APIs are supported for GE and PE apps, and Metadata API is supported in PE apps. To request API access, see How do I get an API token for my app? You can also contact Salesforce to request that a connected app be whitelisted to use the REST API in GE or PE orgs.
- Other APIs, such as the Bulk API and Apex methods exposed as SOAP Web services, remain unavailable.
- You can enable REST-based Web services using connected app consumer whitelisting.
- You can enable SOAP-based Web services, including Metadata API, using an API token called a Client ID, which is appended to your SOAP headers in integration calls. This special key enables your app to make calls to GE and PE orgs for Data API and PE orgs for Metadata API, even if the customer does not have API access.
The Client ID has these properties.
- You can't use the Client ID with the AJAX Toolkit in custom JavaScript, S-controls, or anywhere in your app where its value would be exposed to the end customer.
- For development purposes, GE and PE orgs created via the Environment Hub already have the Metadata API and SOAP API (Data API) enabled. You can then develop and test your app before the security review. After your app passes the security review and you obtain an API token, test your app again to ensure that it’s working correctly.
- The Client ID grants GE and PE access to the SOAP API, and PE access to the Metadata API. With the Metadata API, you can dynamically create various components that you typically create in Setup. For instance, you can create a custom field dynamically in a PE organization with the API token.
This table shows which APIs are accessible when using GE and PE and the method of access.
| API | Access to GE and PE |
|---|---|
| Web Services (SOAP) | Yes, with token |
| Apex methods exposed as Web services (SOAP) | No |
| Web services (REST) | Yes, with connected app consumer whitelisting |
| Apex methods exposed as Web services (REST) | Yes, with connected app consumer whitelisting |
| Chatter REST API | Yes |
| Metadata API | Yes, with token |
| Bulk API | No |
| Data Loader tool (uses SOAP Web services) |
No, can’t set the token |