Jump to content

API suggestions

Axle Change

Recommended Posts

A few suggestions for the API:


1) Add listing_id to the response of the create listing API

This doesn't really matter for sell orders because the format is predictable, however for buy orders the id is not predictable. You can sift through your own buy orders to find it, but it seems unnecessary. The listing_id is needed so that you can later remove buy orders.


2) API to request backpack update. 

Similar thing again. You can just request the HTML of your backpack to do this and parse for the date string, but this isn't ideal. Ideally would return success or failure and the unix timestamp of when backpack was last updated (same as in getuserdetails iirc).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...