Skip to content

Releases: RapidSpike/rapidspike-api-wrapper-php

v1.1.1

28 Jun 08:31
b703c0b
Compare
Choose a tag to compare

Just a patch release for the updated Guzzle dependancy.

v1.1.0

10 Mar 12:57
Compare
Choose a tag to compare

In this minor version update I've added some more type casting for function return types and the ability to add custom headers to the request. I've also updated composer dependencies.

Added

  • Function return type casting
  • Ability to add custom headers

Updates

  • Composer dependencies:
Package operations: 1 install, 2 updates, 0 removals
    - Installing ralouphie/getallheaders (3.0.3): Loading from cache
   - Updating guzzlehttp/psr7 (1.4.2 => 1.6.1): Loading from cache
   - Updating guzzlehttp/guzzle (6.3.3 => 6.5.2): Loading from cache 

v1.0.6

11 Jul 10:49
Compare
Choose a tag to compare

Added

  • Issue templates
  • Code of conduct file
  • End-point path standardisation

Fixed

  • call() functionality - now callPath()

Updates

  • Documentation

v1.0.5

09 Jul 12:23
Compare
Choose a tag to compare

Functionality added to RapidSpike\API\Exception\FailedRequest so that the API response body can be retrieved a little simpler when trying to debug failed requests.

v1.0.4

29 Jun 10:47
Compare
Choose a tag to compare

Removed urlencode() function from the KeyAuth class because the http_build_query() does the encoding for us.

v1.0.3

29 Jun 10:30
Compare
Choose a tag to compare

Fix for a rushed previous release.

v1.0.2

29 Jun 09:49
Compare
Choose a tag to compare

Removed the requirement for a public and private key to be supplied when instantiating the Client object. Some end-points do not require keys.

v1.0.1

27 Jun 14:28
Compare
Choose a tag to compare

Some README changes and version tagging tests.

v1.0.0

27 Jun 14:13
Compare
Choose a tag to compare

Basic Functionality Completed

This is the first major release and is a complete package. Its handles key-authentication, multiple HTTP request verbs and is future proof to new API end-points being released. Check out the README to learn about the package's development concepts and see an example of how to use it. Further working examples can be found in the /examples directory.