{
"vendor_offer" : {
"listing" : {
"metadata" : {
"version" : "",
"expiry" : "",
"category" : "",
"category_sub" : "fixed price"
},
swagger: '2.0' | |
info: | |
title: OpenBazaar API | |
description: Let's make trade free | |
version: "1.0.0" | |
# the domain of the service | |
host: localhost | |
# array of all schemes that your API supports | |
schemes: | |
- http |
OpenBazaar has two distinct components: a server and a client.
The ‘server’ is the network daemon that connects with the OpenBazaar P2P network and contains the node’s database. It is the ‘business end’ of the OpenBazaar application, as it connects directly with other nodes on the network, caches data, digital signs contracts, and holds private keys etc. The server can either run locally (i.e. on your computer) or remotely on a virtual private server (e.g. Digital Ocean, Docker, Heroku).
The ‘client’ is what the user interacts with operate the functions of the server. The client uses a combination of REST and Websocket (WS) APIs to control the network and market function of the server. This enables developers to create alternative or feature-specific clients for OpenBazaar.
If the OpenBazaar server is running locally, the base URL will be:
OpenBazaar has two distinct components: a server and a client.
The ‘server’ is the network daemon that connects with the OpenBazaar P2P network and contains the node’s database. It is the ‘business end’ of the OpenBazaar application, as it connects directly with other nodes on the network, caches data, digital signs contracts, and holds private keys etc. The server can either run locally (i.e. on your computer) or remotely on a virtual private server (e.g. Digital Ocean, Docker, Heroku).
The ‘client’ is what the user interacts with operate the functions of the server. The client uses a combination of REST and Websocket (WS) APIs to control the network and market function of the server. This enables developers to create alternative or feature-specific clients for OpenBazaar.
If the OpenBazaar server is running locally, the base URL will be:
{ | |
langName: "English", | |
langCode: "en", | |
/* Use capitalized keys for widely reused text that must be capitalized */ | |
Next: "Next", | |
IAgree: "I Agree", | |
Back: "Back", | |
EnterMessage: "Enter message...", | |
Skip: "Skip", | |
Done: "Done", |
I hereby claim:
- I am drwasho on github.
- I am drwasho (https://keybase.io/drwasho) on keybase.
- I have a public key whose fingerprint is 0614 43F9 9FC1 4F63 5DB8 2E7B 5818 FAC9 E224 0372
To claim this, I am signing this object:
#!/bin/bash | |
sudo apt-get update && sudo apt-get upgrade | |
sudo apt-get install git | |
sudo apt-get install build-essential libssl-dev libffi-dev python-dev openssl python-pip libzmq3-dev | |
sudo add-apt-repository ppa:chris-lea/libsodium | |
sudo apt-get update | |
sudo apt-get -f install | |
sudo apt-get install libsodium-dev | |
sudo pip install cryptography |
#!/bin/bash | |
sudo apt-get update && sudo apt-get upgrade | |
sudo apt-get install git | |
sudo apt-get install build-essential libssl-dev libffi-dev python-dev openssl python-pip libzmq3-dev | |
sudo add-apt-repository ppa:chris-lea/libsodium | |
sudo apt-get update | |
sudo apt-get -f install | |
sudo apt-get install libsodium-dev | |
sudo pip install cryptography |
#!/bin/bash | |
apt-get update && apt-get upgrade | |
apt-get install git | |
apt-get install build-essential libssl-dev libffi-dev python-dev openssl python-pip libzmq3-dev | |
add-apt-repository ppa:chris-lea/libsodium | |
apt-get update | |
apt-get -f install | |
apt-get install libsodium-dev | |
pip install cryptography |