bunck v0.1.5 Bunck

Bunck is a client for the Bunq API.

Configure an API key in config.exs:

config Bunck. api_key: System.get_env("BUNQ_API_KEY")

Then you can make calls using the Bunq API. Bunck takes care of public / private keys, installation, device servers, and sessions.

Example:

Bunck.Client.with_session(fn(client) ->
  %Bunck.User.List{} |> Bunck.Client.request(client) # get all users
  %Bunck.User.Get{user_id: 4} |> Bunck.Client.request(client) # get user with id 4
end)

You can also iterate over a response using Enum:

Bunck.Client.with_session(fn(client) ->
  with {:ok, res} <- %Bunck.User.List{} |> Bunck.Client.request(client),
  do: Enum.map(fn(user) -> do_something_with(user) end)
end)

Link to this section Summary

Functions

start(type, args)

Called when an application is started

Link to this section Functions

start(type, args)

Called when an application is started.

This function is called when an the application is started using Application.start/2 (and functions on top of that, such as Application.ensure_started/2). This function should start the top-level process of the application (which should be the top supervisor of the application’s supervision tree if the application follows the OTP design principles around supervision).

start_type defines how the application is started:

:normal - used if the startup is a normal startup or if the application is distributed and is started on the current node because of a failover from another mode and the application specification key :start_phases is :undefined.
{:takeover, node} - used if the application is distributed and is started on the current node because of a failover on the node node.
{:failover, node} - used if the application is distributed and is started on the current node because of a failover on node node, and the application specification key :start_phases is not :undefined.

start_args are the arguments passed to the application in the :mod specification key (e.g., mod: {MyApp, [:my_args]}).

This function should either return {:ok, pid} or {:ok, pid, state} if startup is successful. pid should be the PID of the top supervisor. state can be an arbitrary term, and if omitted will default to []; if the application is later stopped, state is passed to the stop/1 callback (see the documentation for the c:stop/1 callback for more information).

use Application provides no default implementation for the start/2 callback.

Callback implementation for Application.start/2.