SENEGALA API CONTACT DOCUMENTATION LINKS

api.senegala.com/v1

There is a protection against spamming:
You can get the HTTP status 429 (Too Many Requests) with the message:
You can only do x requests per y seconds with this IP address.

curl -H 'Content-Type: application/json' -d '{ "hash":"you_have_to_put_a_hash_here"}' -X POST https://api.senegala.com/v1/push

If 'hash' is not a 32 bytes hexadecimal string,
you will get a http 400 code failure and a json error message.

If 'hash' is a 32 bytes hexadecimal string,
you will get a http 200 code success and a json message.
The json message will be:
"The hash is already waiting"
or
"The hash has been added"
You will get an error with the message:
"Cannot insert more than x hashes with the same IP address"
if you try to put too many hashes with the same IP address.
Later you will be able to add more hashes with that IP address.
You will get an error with the message:
"Cannot insert more than x hashes"
if the system cannot handle more hashes.
Later you will be able to add more hashes.

curl https://api.senegala.com/v1/status/:hash

If 'hash' is not a 32 bytes hexadecimal string,
you will get a http 400 code failure and a json error message.

If 'hash' is a 32 bytes hexadecimal string,
you will get a http 200 code success and a json message.
The json message will have a key "status".
It can be 'absent' if the 'hash' is not in the system.
It can be 'processing' if the 'hash' is in the system
and the system is processing it.
It can be 'ready' if the 'hash' is in the system
and the proof is ready.
In that case, there will be two additional keys:
'proof' and 'bitcointxid'.