# Postman REPL
Postman repl uses IPython to present the user with an interface to communicate with APIs. It loads postman configuration data into global state, allowing for quick and easy communication with an API.
# Features
Interactive history
Loading postman collections and environments
postman environment variable replacement
Tab completion
Middleware
Help descriptions
# Loading
You can load middleware, environments, and requests through command line flags
You can load new collections at runtime using the load_collection function
You can load new environments at runtime using the load_environment function
You can load middleware by calling load_middleware
# Requests
Requests are loaded into global P variable. Tab completion and help functions supported.
Requests are namespaced under there folder name.
You can simply call the request with no args to use the default parameters from the Postman config
Requests use the “requests” library. You can pass the kwargs for the request.
You can pass an environment to the requests, or it will use the global “E” environment
Returns the response
# Middleware
Middleware is stored in global MW variable
- Middleware will be called when there is a foldername_request name match
For example, if you have a folder “authentication” and a request “authenticate”, your middleware function name should be authentication_authenticate
Having no folder is supported, it would just be request name (for example: “authenticate”)
Middleware should be defined in a separate python module
- Middleware is a function that takes 3 parameters
The function to run the request, taking a single argument for the kwargs
The kwargs that will be ran in the run function
The env that the run function will use
- After request, some global variables are set
R holds the response
D holds the data
J holds the data, parsed as JSON
# History
The global H variable holds the history
You can see the history by calling H()
You can rerun a history call by calling H(index)
You can inspect the history with H.history
Each history has the response, data, and JSON data attached to it
# TODO
TESTS!
Support for other serialization formats besides JSON
Add auth support
Investigate postman unsupported features
Metadata
Release files for postman_repl 0.0.1
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 | |
|---|---|---|---|---|
| postman_repl-0.0.1.tar.gz | 8.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| postman_repl-0.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 18.2 kB
Release files / postman_repl-0.0.1.tar.gz
| Download URL | postman_repl-0.0.1.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
985c14aba0cda05dfd232220fa84c74aaa3f46ded098d689a406eb0ae735a0dc
|
|
BLAKE2b-256 checksum How to use checksums |
f4855474f633b92c256bb7704bff3b1ae457f4c3d2453016062e3907fcb99808
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / postman_repl-0.0.1-py2.py3-none-any.whl
| Download URL | postman_repl-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
dcdb613b19c949134e8bbe1d01f16cc714bbd8485b460c4bcc03fae9c595daad
|
|
BLAKE2b-256 checksum How to use checksums |
b7ee2c3d3e34de1553d98fa6d2aa4e8e8bd4d410b4ee237902e672e2afdc92e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for postman_repl 0.0.1
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.