You are looking at the documentation for 2.x.y.. If you are looking for the documentation for 1.x.y, checkout the 1.16.0 README.md
GET
/POST
/PUT
/DELETE
/HEAD
/PATCH
requests in a fluent style interfaceBlob
s, DataPart
s as multipart/form-data
Fuel
with Maven
and Gradle
. The core package has the following dependencies:mavenCentral()
in your repositories (jcenter()
is deprecated, new releases starting from 2.2.3 are hosted on mavenCentral()
)group
is made up of com.github
as well as username and project namename
is the subproject, this may be any of the packages listed in the installation instructions eg. fuel
, fuel-coroutines
, fuel-kotlinx-serialization
, etcversion
can be the latest master-SMAPSHOT
or -SNAPSHOT
which always points at the HEAD or any other branch, tag or commit hash, e.g. as listed on jitpack.io.SNAPSHOT
builds, but a specific commit in a specific branch (like a commit on master), because your build will then be stable.kotlinx
repository when using coroutines
or serialization
fuel
forks. If a fork's username is $yourname
,group
to com.github.$yourName.fuel
version
on https://jitpack.io/#$yourName/Fuel
Fuel
namespace object, any FuelManager
or using one of the String
extension methods. If you specify a callback the call is async
, if you don't it's blocking
.Fuel
and the extension methods use the FuelManager.instance
under the hood. You can use this FuelManager to change the default behaviour of all requests:fuel
: Basic usage is all you need.