JSON Body
To get started, change your method to POST, PUT or PATCH depending on the requirements of the API. After that, you will need to add the HasBody
interface to your request. Without this interface, Saloon will not send any request body to the HTTP client.
Next, you will need to add the HasJsonBody
trait to your request. This trait will implement the body()
method that the HasBody
interface requires. It also provides a method defaultBody()
which you can extend to provide a default body on your request.
Saloon will automatically send the Content-Type: application/json
header for you when using the HasJsonBody
trait, however, if you would like to overwrite this behaviour then you can use the defaultHeaders
method on the request or modify the headers before the request is sent.
Default Body
There are a couple of ways to interact with the request body to prepare it to be sent. You can either use the methods mentioned below to add to the body on any given instance or you can use the defaultBody
method on your request. This is recommended because you could then define any requirements as constructor arguments in your request and then standardise your request even more.
Sometimes there can be too many items to define as constructor arguments. If this is the case for you, you can require the user to provide an array, or even a DTO to populate the default body of your request.
Interacting with the body() method
While you can define the default body on your request, it might be useful to add or modify the body at runtime on a per-request basis. Saloon has the following methods to allow you to modify the JSON request body:
add(string $key, mixed $value) -> Add items to the JSON body
remove(string $key) -> Remove items from the JSON body
merge(β¦$values) -> Merge another array of items into the JSON body
set(array $value) -> Overwrite the JSON body entirely
all(): array -> Get all the values of the JSON body
isEmpty(): bool -> Check if the body is empty
isNotEmpty(): bool -> Check if the body is not empty
Connector Body
If you would like to also have JSON body on your connector, you can add the same interface and trait to your connector. If you have the trait on both the connector and the request, the properties will be merged. This is useful if you want to have a shared JSON body across every request, like an authentication token.
JSON Flags
When using the HasJsonBody
trait, you may want to customise the flags used when encoding the body to be sent to the API you are integrating with. You may do this with the setJsonFlags
method. It's recommended that you set this within the constructor of your request or connector to ensure that the flags are always used.
For example, if I know that my JSON will contain URLs, but I don't want the URL slashes to be escaped, I can use the JSON_UNESCAPED_SLASHES
flag. You can also specify multiple flags at once by using the |
pipe to separate the flags.
Last updated