apisim allows users to easily handle multiple requests, and outputs & stores usable data.
Clone the repo, in root dir of repo;
pip install .
call 'get' on an endpoint,
apisim 'https://api.agify.io?name=apisim'
call 'post' on an endpoint 100 times, fallback to tor if failed
apisim 'https://api.agify.io?name=apisim' -r=100 -m=post --commands fallback
call 'get' on an endpoint, print each step
apisim 'https://api.agify.io?name=apisim' -m=get --commands verbose
call 'get' on multiple endpoints, print out the results in a table
apisim 'https://api.agify.io?name=apisim' 'https://api.agify.io?name=python' 'https://api.agify.io?name=rest' -m=get --commands table
authenticate on a api, call 'get' on a endpoint, print out the results in a table
apisim --authurl 'https://api.test.io/api/token/' --creds testaccount bot123 --mode=get --url 'https://api.test.io/api/data/' --commands verbose
authenticate on a api, call 'get' on a endpoint, print out the results in ascii dashboard
apisim --authurl 'https://api.test.io/api/token/' --creds testaccount bot123 --mode=get --url 'https://api.test.io/api/data/' --visual
call 'get' on a endpoint, store the results in the db
apisim --mode=get 'https://api.test.io/api/data/' --commands store
query the database
apisim -q (optional filters)
change the settings
apisim -e
-
The user can run any number of requests, and get the response (meta)data in any number of formats.
-
The user can set the requests to run on a schedule/loop continuosly, and should be able to easily pipe trough the output.
-
The user can store the outputs, and qeury it easily.
-
The user can set up 'missions' that can consist of multiple unrelated requests, and tie this to a schedule.
-
The user can provide an input file for 2 goals;
- A file with endpoints that the program will call with set rules.
- A file with data that the program will push with set rules.
-
The user can provide an output file for 2 goals;
- A file that will contain all the mission data
- A file that will contain the response data of the requests