Download the PHP package omniphx/forrest without Composer

Salesforce REST API Client for Laravel

Forrest is a Salesforce/Force.com REST API client for Laravel and Lumen.

Interested in Eloquent Salesforce Models? Check out @roblesterjr04's EloquentSalesForce project that utilizes Forrest as it's API layer.

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:

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

Laravel Installation

The package will automatically register the service provider and Forrest alias for Laravel >=5.5. For earlier versions, add the service provider and alias to your config/app.php file:

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

Lumen Installation

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:

This will publish a config/forrest.php file that can switch between authentication types as well as other settings.

After adding the config file, update your .env to include the following values (details for getting a consumer key and secret are outlined below):

For Lumen, 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. For Laravel 4, run php artisan config:publish omniphx/forrest which create 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. Search App in quick find box, and select App Manager
4. Click New Connected App.
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 amended to your password unless your IP address is whitelisted.

Client Credentials authentication flow

With the Client Credentials flow, you can directly authenticate with the Forrest::authenticate() method.

Using this authentication method only requires your consumer secret and key. Your Salesforce Connected app must also have the "Client Credentials Flow" Enabled in its settings.

SOAP authentication flow

(When you cannot create a connected App in Salesforce)

1. Salesforce allows individual logins via a SOAP Login
2. The Bearer access token returned from the SOAP login can be used similar to Oauth key
3. Update your config file and set the authentication value to UserPasswordSoap
4. Update your config file with values for loginURL, username, and password. With the Username Password SOAP flow, you can directly authenticate with the Forrest::authenticate() method.

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

If your application requires logging in to salesforce as different users, you can alternatively pass in the login url, username, and password to the Forrest::authenticateUser() method.

Security token might need to be amended to your password unless your IP address is whitelisted.

JWT authentication flow

Initial setup

1. Set authentication to OAuthJWT in config/forrest.php
2. Generate a key and cert: openssl req -newkey rsa:2048 -nodes -keyout server.key -x509 -days 365 -out server.crt
3. Configure private key in config/forrest.php (e.g., file_get_contents('./../server.key'),)

Setting up a Connected App

1. App Manager > Create Connected App
2. Enable Oauth Settings
3. Check "Use digital signatures"
4. Add server.crt or whatever you choose to name it
5. Scope must includes "refresh_token, offline_access"
6. Click Save

Next you need to pre-authorize a profile (As of now, can only do this step in Classic but it's important)

1. Manage Apps > Connected Apps
2. Click 'Edit' next to your application
3. Set 'Permitted Users' = 'Admin approved users are pre-authorized'
4. Save
5. Go to Settings > Manage Users > Profiles and edit the profile of the associated user (i.e., Salesforce Administrator)
6. Under 'Connected App Access' check the corresponding app name

The implementation is exactly the same as UserPassword (e.g., will need to explicitly specify a username and password)

For connecting to Lightning orgs you will need to configure an instanceUrl inside your forrest.php config:

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

Sample result:

If you are querying more than 2000 records, your 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.

Setting headers

Sometimes you need the ability to set custom headers (e.g., creating a Lead with an assignment rule)

To disable assignment rules, use 'Sforce-Auto-Assign' => 'false'

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.

You can determine which resources you have access to by calling with the resource method

This sample output shows the resourses available to call via the API:

From the list above, I can call resources by referring to the specified key.

Or...

Additional resource url parameters can also be passed in

As well as new formatting options, headers or other configurations

Upsert multiple records (Bulk API 2.0)

Bulk API requests are especially handy when you need to quickly load large amounts of data into your Salesforce org. The key differences is that it requires at least three separate requests (Create, Add, Close), and the data being loaded is sent in a CSV format.

To illustrate, following are three requests to upsert a CSV of Contacts records.

Create

Create a bulk upload job with the POST method, the body contains the following job properties:

• object is the type of objects you're loading (they must all be the same type per job)
• externalIdFieldName is the external ID, if this exists it'll update and if it doesn't a new record will be inserted. Only needed for upsert operations.
• contentType is CSV, this is currently the only valid value.
• operation is set to upsert to both add and update records.

We're storing the response in $bulkJob in order to reference the unique Job ID in the Add and Close requests below.

See Create a Job for the full list of options available here.

Add Data

Using the Job ID from the Create POST request, you then send the CSV data to be processed using a PUT request. This assumes you've loaded your CSV contents to $csv

See Prepare CSV Files for details on how it should be formatted.

Close

You must close the job before the records can be processed, to do so you send an UploadComplete state using a PATCH request to the Job ID.

See Close or Abort a Job for more options and details on how to abort a job.

Bulk API 2.0 is available in API version 41.0 and later. For more information on Salesforce Bulk API, check out the official documentation and this tutorial on how to perform a successful Bulk Upload.

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.

Base URL

Returns the URL of the Salesforce instance with api info.

Instance URL

Returns the URL of the Salesforce instance.

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.

Get file body from ContentVersion and Attachment

You can use the Forrest::getContentVersionBody() and Forrest::getAttachmentBody() to retrieve the content of the uploaded files. They return a streamed response, so it may be a bit cumbersome to use if now used to streams. Bellow you can find an example to retrieve the content of a uploaded content version.

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 the format of 'none' and the code will return the entire response body as a string.

Event Listener

This package makes use of Guzzle's event listers

Creating multiple instances of Forrest

There might be situations where you need to make calls to multiple Salesforce orgs. This can only be achieved only with the UserPassword flows.

1. Set storage = object in the config file. This will store the token inside the object instance:

2. Create a multiple instance with the laravel app()->make() helper function:

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

Creating a custom store

If you'd prefer to use storage other than session, cache or object, you can implement a custom implementation by configuring a custom class instance in storage.type:

You class can be named anything but it must implement Omniphx\Forrest\Interfaces\StorageInterface: