monzo-api-stub
Stub API for Monzo.
Note about Monzo API deprecation
The Monzo API is essentially deprecated at this point. It has not been in active development since early 2016 (as far as I can tell), and will likely not be worked on until mid-2018, as the UK are introducing new regulations for open banking infrastructure which will influence the future of Monzo’s API. I’ll happily accept PRs to this repo, but given the state of the API’s development I have ceased working with the Monzo API myself so will not be maintaining this until API development picks up again.
Installation
The package is available on PyPI:
$ pip install monzo-api-stub
Usage
To run a server:
$ monzo-api
You can parse optional arguments to change the behaviour:
$ monzo-api --help
Usage: monzo-api [OPTIONS]
Stub Monzo API
Options:
--host TEXT Address to bind to.
--port INTEGER Port for the HTTP server.
--num-accounts INTEGER Number of accounts to give the user
--currency TEXT Currency to use, pass "random" to use random
currencies
--help Show this message and exit.
Note: This is not guaranteed to be API compatible. It is a best-effort attempt to provide a useful tool for developers building for the Monzo API.
Features
OAuth flow with immediate redirect, no need to enter an email address.
Test with pre-defined or random currencies.
Test as a user with multiple accounts.
Completeness
Since this is a stub API, most “business logic” on the server side isn’t implemented, and likely won’t be.
This should however be considered a work in progress, and any PRs that bring responses/endpoints closer to those of the real API, or any that add entirely missing endpoints, are very welcome.
Things that are missing:
OAuth exchange is fake - I’d like to add this in a basic way to make it easier to test the OAuth flow.
No auth headers required - Would be good to have a basic (optional?) auth check.
Verbose request logging - to help see what your client application is sending.
Loading custom data - to allow testing of specific cases that your app wants to handle.
Webhooks.
Metadata
Release files for monzo-api-stub 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| monzo-api-stub-0.1.3.tar.gz | 6.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| monzo_api_stub-0.1.3-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 16.8 kB
Release files / monzo-api-stub-0.1.3.tar.gz
| Download URL | monzo-api-stub-0.1.3.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea10f9a033829ef57e54a535631f4f509faacca128027a9fade65e520e4e5f93
|
|
BLAKE2b-256 checksum How to use checksums |
c4c19c8f2b03e02e0010a17322a181497838264c8f60db18cba2e54fa462f50e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / monzo_api_stub-0.1.3-py2-none-any.whl
| Download URL | monzo_api_stub-0.1.3-py2-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
990bdbee4844447f23863c4c609ce6eebec4b84cf8fb3d19fa23e7999ac0690e
|
|
BLAKE2b-256 checksum How to use checksums |
0d6c58bbfb5558d850cb85001d922eda166cb3785bec0f10f5718a331bdd156c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for monzo-api-stub 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.