I'm working on getting a Salesforce API key currently so that I can develop a web-based application (probably php) to streamline a currently tedious process. My current workflow is as follows:
- Open list of cases
- Click a specific case
- Fill out a report regarding that case (editing fields such as checkboxes and text inputs)
- Mark the report complete or incomplete
- Move on to the next case
My goal is to redesign the whole process using a custom application while using the Salesforce API to update the information/cases in Salesforce. I don't want to have to log into Salesforce and use it, because it's tedious and slow.
- Does the Salesforce API allow me to send information back and actually update the data/reports/cases in Salesforce?
- Which API is best to use for this process? (There's about 75-200 cases a week as far as quantity is concerned)
- REST API - Access objects in your organization using REST.
- SOAP API - Integrate your organization’s data with other applications using SOAP.
- Tooling API - Build custom development tools for Force.com applications. Coming soon!
- Chatter REST API - Access Chatter feeds and social data such as users, groups, followers, and files using REST.
- Bulk API - Load or delete large numbers of records.
- Metadata API - Manage customizations in your org and build tools that manage the metadata model (not the data, itself).
- Streaming API - Provide a stream of data reflecting data changes in your organization.
- Apex REST API - Build your own REST API in Apex. This API exposes Apex classes as RESTful Web services.
- Apex SOAP API - Create custom SOAP Web services in Apex. This API exposes Apex classes as SOAP Web services.
- Data.com API - Data.com provides 100% complete, high quality data, updated in real-time in the cloud, and with comprehensive coverage worldwide.
I feel that the
REST API might be the most simple and practical. In anyone's experiences, would this allow me to do what I need?
Thanks for any/all help!