Download the PHP package tectalic/openai without Composer

Tectalic OpenAI REST API Client

This package is no longer supported or maintained.

Introduction

The Tectalic OpenAI REST API Client is a package that provides a convenient and straightforward way to interact with the OpenAI API from your PHP application.

Supports ChatGPT, GPT-4, GPT-3.5, GPT-3, Codex, DALL·E, Whisper, Fine-Tuning, Embeddings and Moderation models, with fully typed Data Transfer Objects (DTOs) for all requests and responses and IDE autocomplete support.

More information is available from https://tectalic.com/apis/openai.

This is an unofficial package and has no affiliations with OpenAI.

Examples

Integrating OpenAI into your application is now as simple as a few lines of code.

Chat Completion using ChatGPT (GPT-3.5 & GPT-4)

Learn more about chat completion.

This handler supports both the GPT-3.5 and GPT-4 models:

GPT-3.5

Supported GPT-3.5 models include gpt-3.5-turbo and more.

GPT-4

Supported GPT-4 models include gpt-4 and more.

Note: GPT-4 is currently in a limited beta and is only accessible to those who have been granted access. Please see here for details and instructions on how to join the waitlist.

If you receive a 404 error when attempting to use GPT-4, then your OpenAI account has not been granted access.

Chat Completion Function Calling using ChatGPT (GPT-3.5 & GPT-4)

The following example uses the gpt-3.5-turbo-0613 model to demonstrate function calling.

It converts natural language into a function call, which can then be executed within your application.

Learn more about function calling.

Text Completion (GPT-3)

This handler supports all GPT-3 models, including text-davinci-003, text-davinci-002 and more.

Learn more about text completion.

Code Completion (Codex)

Supported Codex models include code-davinci-002 and code-cushman-001.

Learn more about code completion.

Image Generation (DALL·E)

Learn more about image generation.

Speech to Text Audio Transcription (Whisper)

Supported Whisper models include whisper-1.

Learn more about speech to text, including the 50+ supported languages.

Speech to Text Audio Translation (Whisper)

Supported Whisper models include whisper-1.

Learn more about speech to text, including the 50+ supported languages.

Installation

Need help getting started? See our guide: how to build an app using the OpenAI API.

System Requirements

• PHP version 7.2.5 or newer (including PHP 8.0 and 8.1)
• PHP JSON extension installed if using PHP 7.x. As of PHP 8.0, this extension became a core PHP extension so is always enabled.
• A PSR-18 compatible HTTP client such as 'Guzzle' or the 'Symfony HTTP Client'.

Composer Installation

Install the package into your project:

Usage

After installing the Tectalic OpenAI REST API Client package into your project, ensure you also have a compatible PSR-18 HTTP client such as 'Guzzle' or the Symfony 'HTTP Client'.

You can use the following code sample and customize it to suit your application.

Authentication

To authenticate your API requests, you will need to provide an Authentication ($auth) object when calling Manager::build().

Authentication to the OpenAI API is by HTTP Bearer authentication.

Please see the OpenAI API documentation for more details on obtaining your authentication credentials.

In the Usage code above, customize the Authentication constructor to your needs. For example, will likely need to add a OPENAI_API_KEY environment variable to your system.

Client Class

The primary class you will interact with is the Client class (Tectalic\OpenAi\Client).

This Client class also contains the helper methods that let you quickly access the 19 API Handlers.

Please see below for a complete list of supported handlers and methods.

Supported API Handlers and Methods

This package supports 28 API Methods, which are grouped into 19 API Handlers.

See the table below for a full list of API Handlers and Methods.

Deprecated method(s) are listed with strike-through formatting. Please do not use these methods, as they will be removed in a future release.

Making a Request

There are two ways to make a request to the nominated API Handler and API Method:

If you built the client to be accessible globally, you can use the relevant API Handler Class directly:

Alternatively, you can access all API Handlers from the client class using the Client class:

Retrieving the Response

Once you have made a request using one of the two methods outlined above, the next step is to access the response.

You can access the response in different ways. Please choose your preferred one.

Model Responses

Model responses are Data Transfer Object (DTO) style PHP classes, with public properties for each API property.

They offer a structured way of retrieving the response from an API request.

All Response Models are an instance of Tectalic\OpenAi\Models\AbstractModel or Tectalic\OpenAi\Models\AbstractModelCollection.

After performing the request, use the ->toModel() fluent method to the API Method:

Each API Method's toModel() call will return the appropriate Model class type for the API Method you have just called.

Associative Array Responses

After performing the request, use the ->toArray() fluent method to the API Method:

In the resulting associative array, the array keys will match the names of the public properties in the relevant Model class.

PSR 7 Response Objects

If you need to access the raw response or inspect the HTTP headers, use the ->getResponse() fluent method to the API Method. It will return a Psr\Http\Message\ResponseInterface:

Errors

When performing requests with Tectalic OpenAI REST API Client, specific scenarios will cause a Tectalic\OpenAi\Exception\ClientException to be thrown. Please see below for details.

Invalid Usage of the Manager Class

A \LogicException will be thrown if the Manager::build() function is called multiple times, or if Manager::access() is called before calling Manager::build().

Unsuccessful HTTP Response Codes

The Tectalic OpenAI REST API Client depends on a PSR-18 compatible HTTP client, and that HTTP client should not throw an exception for unsuccessful HTTP response codes.

An unsuccessful response code is classified as one that is not in the range 200-299 (inclusive). Examples of unsuccessful response codes include:

• Informational responses (100-199)
• Redirection responses (300-399)
• Client error responses (400-499)
• Server error responses (500-599)

If an unsuccessful response code does occur:

• your HTTP Client will not throw an Exception.
• the API Handler's toModel() method will throw a ClientException.
• the API Handler's toArray() method will return the response body and not throw a ClientException.
• The API Handler's getResponse() method will return the raw response and not throw a ClientException.

Below is an example of how you may wish to use a try/catch block when performing a request so that you can detect and handle unexpected errors.

HTTP Client Exceptions

If your HTTP client of choice throws an exception other than ClientException, the Tectalic OpenAI REST API Client Client and its API Handler classes will let these exceptions bubble up.

Consult your HTTP client's documentation for more details on exception handling.

Tests

The Tectalic OpenAI REST API Client package includes several types of automated PHPUnit tests to verify the correct operation:

• Unit Tests
• Integration Tests

To run these tests, you will need to have installed the Tectalic OpenAI REST API Client package with its dev dependencies (i.e. not using the --no-dev flag when running composer).

Unit Tests

These PHPUnit tests are designed to:

• confirm that each API Method assembles a valid request that matches the OpenAI API OpenAPI specification.
• verify the behaviour of other parts of the package, such as the Client and Manager classes.

The unit tests can be run using the following command, which needs to be run from this package's root directory.

Unit tests do not perform any real requests against the OpenAI API.

Unit tests are located in the tests/Unit directory.

Integration Tests

Integration tests are located in the tests/Integration directory.

These PHPUnit tests are designed to confirm that each API Method parses a valid response, according to the OpenAI API OpenAPI specification. Out of the box the integration tests are designed to work with the Prism Mock Server.

Using Prism as the Target

Make sure Prism is installed. Please see the Prism documentation for details on how to install Prism.

Once Prism is installed, you can run prism and the integration tests side by side in separate terminal windows, or using the following command, which need to be run from this package's root directory.

Those commands will start the Prism mock server, then run the integration tests, and then stop the Prism mock server when the tests are completed.

In this case the integration tests do not perform any real requests against the OpenAI API.

Using a Different Target

By setting the OPENAI_CLIENT_TEST_BASE_URI environment variable, you can set a different API endpoint target for the integration tests.

For example, instead of using Prism, you can use a different mocking/staging/test server of your choice, or you can use the OpenAI API's live endpoints.

Do not forget to set the appropriate credentials in the OPENAI_CLIENT_TEST_AUTH_USERNAME OPENAI_CLIENT_TEST_AUTH_PASSWORD environment variables.

After your setup is complete simply run the following command.

We do not recommend running integration tests against the live OpenAI API endpoints. This is because the tests will send example data to all endpoints, which can result in new data being created, or existing data being deleted.

Writing Your Own Tests

If you are writing your own tests, you will likely need to mock the responses from the OpenAI API.

One way of doing this is to install the php-http/mock-client package into your project, and then use the \Http\Mock\Client class (instead of a real PSR-18 client) when instantiating the Tectalic OpenAI REST API Client.

This allows you to mock the responses from the OpenAI API, rather than performing real requests.

Please see the Mock Client documentation for details.

Support

If you have any questions or feedback, please use the discussion board.

License

This software is copyright (c) 2022-present Tectalic.

For copyright and license information, please view the LICENSE file.