1. There is no such thing as a "pending" ban or Steam admin. Anyone threatening your account is a scammer trying to scare you. Read more.

Well why are we applying for SR's Api?

Discussion in 'SteamRep API Discussion' started by Frost-Seupoj, Sep 18, 2013.

  1. Frost-Seupoj

    Frost-Seupoj New User

    Messages:
    33
    Steam:
    STEAM_0:0:29854057
    Yes why are we applying for SR's Api
    To Ban the people who are scammers From our forums or community website
    Is that correct
    We can do that with Backpack.tf's Api As its public and we can get what we need simple
    *Its in Json Format
    PHP:
    {
        
    "response": {
            
    "success"1,
            
    "current_time"1346178821// current server time
            
    "players": [
                {
                    
    "steamid""76561197960435530"// 64bit SteamID of the user
                    
    "success"1,
                    
    "backpack_value"3351.91,    // Player's last backpack value in refined
                    
    "backpack_update"1346163657,    // Player's last backpack update date in unix format
                    
    "name""Robin",        // Player's last updated name
                    
    "stats_tf_reputation"1237,    // If set, player's reputation on stats.tf network
                    
    "stats_tf_supporter"1        // Has player joined the stats.tf steam group?
                   
    "steamrep_scammer"true,    // If set, is the player a tagged scammer on steamrep ?
                    
    "ban_economy"true        // If set, is the player banned from steam trading?
                
    },
                [...]
            ]
        }
    }
    Thats better in fact cause we can 100 SteamID's at a time
    Fast Easy Simple
    Just wanted to ask what all EXTRA feature are they giving rather than this

    and i found a glitch with SR's API today Don't want to tell here
    Thanks
  2. SilentReaper(SR)

    SilentReaper(SR) Retired Staff

    Messages:
    11,991
    SteamRep Admin:
    STEAM_0:0:89705646
    I really do hope bp.tf's api is NOT doing a forward API call to us for that, if so we'd ask them to stop that. Which will end up to show then only cached results, which will never be live current results, only their last visited their bp page status. So for that it won't be usable .
  3. SilentReaper(SR)

    SilentReaper(SR) Retired Staff

    Messages:
    11,991
    SteamRep Admin:
    STEAM_0:0:89705646
    20:18 - SilentReaper(SR): don't think its advisable to "forward" status in your api..
    20:19 - Brad Pitt: it doesn't forward the call
    20:20 - Brad Pitt: it gives the data that's already cached
    20:20 - SilentReaper(SR): tho so
    20:20 - SilentReaper(SR): which makes it per definition old and not usable for status for others
    20:21 - Brad Pitt: pretty much, i have no plans to replace steamrep -- it's just there as a helper
    20:21 - SilentReaper(SR): yeah
    20:21 - SilentReaper(SR): thnx for the quick answer ;)
  4. Frost-Seupoj

    Frost-Seupoj New User

    Messages:
    33
    Steam:
    STEAM_0:0:29854057
    Well thanks for clarifying but can we use this on our websites as api rather than your beta api because getting that is harder than this
    Thanks
  5. SilentReaper(SR)

    SilentReaper(SR) Retired Staff

    Messages:
    11,991
    SteamRep Admin:
    STEAM_0:0:89705646
    getting beta access is harder for its already high in use, and more different parties using it means harder to implement changes. so mattie made some criteria.
  6. ReignBro

    ReignBro New User

    Messages:
    12
    Steam:
    STEAM_0:1:44693178
    is it worth the hassle?