Download the PHP package cmpas2/ayforrest without Composer

Salesforce REST API Client for Laravel 5

Salesforce/Force.com REST API client for Laravel. While it acts as more of a wrapper of the API methods, it should provide you with all the flexibility you will need to interact with the REST service.

While this package is built for Laravel, it has been decoupled so that it can be extended into any framework or vanilla PHP application. Currently the only support is for Larevel 4, 5 and Lumen.

Installation

If you are upgrading to Version 2.0, be sure to re-publish your config file.

Forrest can be installed through composer. Open your composer.json file and add the following to the require key:

"omniphx/forrest": "2.*"

Next run composer update from the command line to install the package.

If you are using Laravel, add the service provider and alias to your config/app.php file:

Omniphx\Forrest\Providers\Laravel\ForrestServiceProvider::class

'Forrest' => Omniphx\Forrest\Providers\Laravel\Facades\Forrest::class

For Laravel 4, add Omniphx\Forrest\Providers\Laravel4\ForrestServiceProvider in app/config/app.php. Alias will remain the same.

Lumen Installation

You should copy the config file from src/config/config.php and add it to a forrest.php configuration file under a config directory in the root of your application.

Then you'll utilize the Lumen service provider by registering it in the bootstrap/app.php file.

Configuration

You will need a configuration file to add your credentials. Publish a config file using the artisan command:

You can find the config file in: config/forrest.php

For Laravel 4, run php artisan config:publish omniphx/forrest. It will be found in app/config/omniphx/forrest/config.php

Getting Started

Setting up a Connected App

1. Log into to your Salesforce org
2. Click on Setup in the upper right-hand menu
3. Under Build click Create > Apps
4. Scroll to the bottom and click New under Connected Apps.
5. Enter the following details for the remote application:
   • Connected App Name
   • API Name
   • Contact Email
   • Enable OAuth Settings under the API dropdown
   • Callback URL
   • Select access scope (If you need a refresh token, specify it here)
6. Click Save

After saving, you will now be given a Consumer Key and Consumer Secret. Update your config file with values for consumerKey, consumerSecret, loginURL and callbackURI.

Setup

Creating authentication routes

Web Server authentication flow

Username-Password authentication flow

With the Username Password flow, you can directly authenticate with the Forrest::authenticate() method.

To use this authentication you must add your username, and password to the config file. Security token might need to be ammended to your password unless your IP address is whitelisted.

Custom login urls

Sometimes users will need to connect to a sandbox or custom url. To do this, simply pass the url as an argument for the authenticatation method:

Note: You can specify a default login URL in your config file.

Basic usage

After authentication, your app will store an encrypted authentication token which can be used to make API requests.

Query a record

Result:

If you are querying more than 2000 records, you response will include:

Simply, call Forrest::next($nextRecordsUrl) to return the next 2000 records.

Create a new record

Records can be created using the following format.

Update a record

Update a record with the PUT method.

Upsert a record

Update a record with the PATCH method and if the external Id doesn't exist, it will insert a new record.

Delete a record

Delete a record with the DELETE method.

XML format

Change the request/response format to XML with the format key or make it default in your config file.

API Requests

With the exception of the search and query resources, all resources are requested dynamically using method overloading.

First, determine which resources you have access to by calling:

Result:

Next, call resources by referring to the specified key. For instance:

or

Resource urls can be extended by passing additional parameters into the first argument:

You can also add optional parameters to requests:

Additional API Requests

Refresh

If a refresh token is set, the server can refresh the access token on the user's behalf. Refresh tokens are only for the Web Server flow.

If you need a refresh token, be sure to specify this under access scope in your Connected App. You can also specify this in your configuration file by adding 'scope' => 'full refresh_token'. Setting scope access in the config file is optional, the default scope access is determined by your Salesforce org.

Revoke

This will revoke the authorization token. The session will continue to store a token, but it will become invalid.

Versions

Returns all currently supported versions. Includes the verison, label and link to each version's root:

Resources

Returns list of available resources based on the logged in user's permission and API version.

Identity

Returns information about the logged-in user.

For a complete listing of API resources, refer to the Force.com REST API Developer's Guide

Custom Apex endpoints

If you create a custom API using Apex, you can use the custom() method for consuming them.

Additional options and parameters can be passed in like this:

Read Creating REST APIs using Apex REST for more information.

Raw Requests

If needed, you can make raw requests to an endpoint of your choice.

Raw response output

By default, this package will return the body of a response as either a deserialized JSON object or a SimpleXMLElement object.

There might be times, when you would rather handle this differently. To do this, simply use any format other than 'json' or 'xml' and the code will return a Guzzle response object.

Event Listener

This package makes use of Guzzle's event listers

For more information about Guzzle responses and event listeners, refer to their documentation.