This is a Python SDK for Sweetpay's different APIs. Note that this library is not production ready yet. The checkout (v1), creditcheck (v2) and subscription (v1) API is currently only supported.

The documentation of the underlying APIs can be found here.

Some tests have been written for the subscription API, which makes it the currently most stable part of the SDK.

Only Python3.3+ is supported. There is currently no plan to implement support for Python2.

Table of Contents - API Documentations

Subscription API

Installation

You can use pip to install the SDK.

pip install sweetpay

Configuring the SDK

from sweetpay import SweetpayClient
client = SweetpayClient(
    "<your-api-token>", stage=True, version={"subscription": 1})

Note that all code examples below this point will assume that you've already configured the SDK as shown above.

General use

# Use an operation
data = client.subscription.search(merchantId="<your-merchant-id>")

# If all went well, a dictionary with the JSON data is returned.
# If something went wrong, an exception is raised.
print(data)

Error handling

If you're calling an operation on a resource (e.g. client.subscription.create) and no exception is raised, you can rest assured that the operation succeeded. If something goes wrong, an exception will always be raised.

All exceptions exposes the data, response, status, code and exc attribute. None of them are guaranteed to have a value other than None, but they can be useful when you want to know the source of the error.

from sweetpay.errors import *

try:
    # Use an operation
    resp = client.subscription.create(amount=200)

except FailureStatusError as e:
    # Whenever you get this, you would do best to inspect the 
    # status, to figure out what went wrong. 
    if e.status == "NOT_MODIFIABLE":
        print(
            "The subscription can't be modified, possibly "
            "because it's regretted or expired")
    else:
        print("Something else went wrong")
        
except UnauthorizedError as e:
    # You are simply unauthorized. Make sure your
    # API token is indeed correct.
    print("Incorrect API token!")
    
except NotFoundError as e:
    # The resource ID (e.g. `subscription_id`) did not match 
    # an existing resource. Can also be raised if an API endpoint
    # isn't found; in that case, something is wrong with the API
    # client and a bug report should be filed.
    print("The resource couldn't be found on the server")

except ProxyError as e:
    # A proxy error occurred. It's usually best to just
    # retry in this case.
    print("Maybe retry?")

except MethodNotAllowedError as e:
    # If you receive this status, there is something wrong with  
    # the SDK, as no invalid HTTP methods should used when  
    # communicating with the server. Contact Sweetpay's developers.
    print("Wrong HTTP method sent to the API endpoint!")

except UnderMaintenanceError as e:
    # Just try again later.
    print("The API is under maintenance.")

except (BadDataError, InvalidParameterError) as e:
    # Inspect `e.status` or `e.data`.
    print("You passed bad data to the server")

except InternalServerError as e:
    # Contact Sweetpay's developers if this happens. It 
    # shouldn't happen.
    print("Something went wrong on Sweetpay's server.")

except TimeoutError as e:
    # Try again, and maybe set a higher timeout.
    print("A timeout occurred!")

except RequestError as e:
    # The parent of all errors stemming from the underlying 
    # `requests` library. If you want to know the details, 
    # try inspecting the `e.exc` for gaining access to the 
    # real exception.
    print("The real exception:", e.exc)

except SweetpayError as e:
    # The parent of all errors.
    print("You can catch all errors with this one")

It should be noted that every exception has a .to_dict method which can be used to get the status, data, etc. in a dictionary. This can in turn be used for logging. For example:

import logging

# Get your logger instance
logger = logging.getLogger(__name__)

try:
    client.subscription.search()
except SweetpayError as e:
    # Something went wrong, let's log it.
    data = e.to_dict()
    logger.error(
        "Could not search subscriptions, exception data: %s", str(data))

Testing & Mocking

If you want to test your code without sending requests to server, you can easily do so by making use of the mock method of each API operation. All arguments passed to the mock method will be passed to the __init__ method of unittest.mock.Mock.

import pytest
from sweetpay.errors import InvalidParameterError

# Testing the successful creation of a subscription
def test_subscription_creation(client):
    with client.subscription.create.mock(return_value={"status": "OK"}) as mock:
        data = client.subscription.create(amount=200)
    mock.assert_called_once_with(amount=200)
    assert data == {"status": "OK"}

# If we instead want to raise an exception
def test_subscription_creation_failure(client):
    exc = InvalidParameterError()
    with client.subscription.mock(side_effect=InvalidParameterError):
        with pytest.raises(InvalidParameterError) as excinfo:
            client.subscription.create(amount=200)
    assert excinfo.value is exc

For mocking on the actual request level you can for example use requests-mock. However, this is discouraged, since that would rely on the internals of the library.

Instead of using the built-in mocking support (which is just a convenience wrapper around unittest.mock.Mock()), you could of course do the mocking manually yourself. You could need to do the mocking yourself if you don't have a global instance of sweetpay.SweetpayClient.

NOTE: The mocking support is not thread-safe if you are using a global instance of sweetpay.SweetpayClient.

Callbacks & Deserialization

This library provides no helpers for receiving callbacks and deserializing the API request data. You can use something like Flask or Django for that, and then use marshmallow for deserializing data (turning JSON data into Python objects, e.g. converting ISO formatted strings into datetime.datetime objects).

API Documentations

This part of the documentation will describe how you can call the API.