GLBSE json API up and running

[Nefario]

Hello all, we've got a json API up and running for glbse.


get a list of all assets on glbse
http://dev.glbse.com:4567/json_assets

orderbook/depth
http://dev.glbse.com:4567/orderbook/asset/ASSET_ID

Trade history (gives up to 7 days history)
http://dev.glbse.com:4567/trades/asset/ASSET_ID

Replace asset id with the assets actual id such as  SIN, UBX, ir DISHWARA

Feedback appreciated.

Nefario.

[1715442840]

1715442840

[1715442840]

1715442840

[1715442840]

1715442840

[1715442840]

1715442840

[1715442840]

1715442840

[Clark]

It's great to have these up and running, however it would be extremely helpful to make them friendly to cross-domain AJAX queries.

Here's how:

• Enable JSONP wrapping on the server side. (PHP example in the link)
• Change data type header to application/javascript to avoid type mismatch warnings in the browser

[filharvey]

One question from me is, are you going to allow people to withdraw funds less than 1btc? 0.1 or even 0.01 would be nice, especially for what I'm thinking of. To get to 1btc could take 5-10 weeks of dividends per share and hence could affect people wanting to invest.

[Nefario]

One question from me is, are you going to allow people to withdraw funds less than 1btc? 0.1 or even 0.01 would be nice, especially for what I'm thinking of. To get to 1btc could take 5-10 weeks of dividends per share and hence could affect people wanting to invest.

The reason for the fee was to cover costs for transaction fees, setting the minimum to withdraw would prevent a fee hitting the system with that particular account being empty.

I'm unsure what the situation with transaction fees currently is as I've been too busy to check in the last couple of weeks, but I know this gave me untold headaches when I had to deal with it last time.

What I will do is enable bitcoin transfers, so you can send to someone else who has an account instantly.

[Nefario]

It's great to have these up and running, however it would be extremely helpful to make them friendly to cross-domain AJAX queries.

Here's how:

• Enable JSONP wrapping on the server side. (PHP example in the link)
• Change data type header to application/javascript to avoid type mismatch warnings in the browser

I'll see what I can do to add jsonp, this is actually something I'd like myself, would sort out a lot of headaches.

[Nefario]

It's great to have these up and running, however it would be extremely helpful to make them friendly to cross-domain AJAX queries.

Here's how:

• Enable JSONP wrapping on the server side. (PHP example in the link)
• Change data type header to application/javascript to avoid type mismatch warnings in the browser

Sorted, JSONP should now be supported (for nearly all requests to the server actually) I've not tested it, so give it a try and let me know.

Nefario

[Clark]

Awesome! It works for me with no warning messages whatsoever.

Thanks for the quick turnaround on this.

[Nefario]

Update on the URL's since adding ssl.


get a list of all assets on glbse
https://glbse.com/GLBSE/json_assets

orderbook/depth
https://glbse.com/GLBSE/orderbook/asset/ASSET_ID

Trade history (gives up to 7 days history)
https://glbse.com/GLBSE/trades/asset/ASSET_ID

[brendio]

What I will do is enable bitcoin transfers, so you can send to someone else who has an account instantly.

Is this currently enabled, and if so, how is it done? I've set up another account and want to transfer some BTC from my old account to the new one.

[Nefario]

What I will do is enable bitcoin transfers, so you can send to someone else who has an account instantly.

Is this currently enabled, and if so, how is it done? I've set up another account and want to transfer some BTC from my old account to the new one.

I've not implemented this yet, we've had a lot of non-coding related issues to deal with over the last few weeks that have, for want of a better word kept us from adding functionality.

I really think this would be an awesome feature, and would probably lead a lot of people to start using GLBSE more as an online account than say for trading, as our security is much better than a typical web based system.

Timescale...
After we add: showing what asset dividend payments are from and what asset a vote is for, this will be next.

Then there is going to be a freeze on feature adding as we clean up some of our code.

Nefario.

[alfred]

Is there, or will there be, an API for placing orders. API would need to:

o) Query existing orders in the owners account
o) Cancel or adjust said orders
o) Create new ones

Then I could write a market maker for what I have planned....

Also, can I request a 'GTD' order type (Good 'Til Date) so that you can place an order that will automatically expire at a given date/time.

[Nefario]

Is there, or will there be, an API for placing orders. API would need to:

o) Query existing orders in the owners account
o) Cancel or adjust said orders
o) Create new ones

Then I could write a market maker for what I have planned....

Also, can I request a 'GTD' order type (Good 'Til Date) so that you can place an order that will automatically expire at a given date/time.

We're in the process of having a client lib that would allow full interaction with GLBSE, it's written in python and there already but is being tested, with a few bugs to fix.

I'd say give us about a week for this.

Nefario.

[alfred]

I look forward to it.

BTW, is the GLBSE platform designed to scale?

[Nefario]

I look forward to it.

BTW, is the GLBSE platform designed to scale?

A few changes in the backend (the database) need to be made, but apart from that it should easily scale. It's designed as a finite state machine for most parts of the system except the actual order matching, so scaling is really just a case of adding more machines.
I'm planning on making the needed changes to have it run on Heroku, in which case scalability is only a matter of cost then.

Nefario.