Atlas API Discussion Thread

[Harsha]

I believe either all should have it or none . Nothing in between

[Garon4DWS]

as flumpi already says,

there are also other ways to build a warning bot, such as via banner evaluation. But certainly not many can do this and you can’t prevent the belief. so a few teams would have an advantage over all the others. therefore, it is fairer with the API.

[LEER0YJENKINS1]

there are 3 major services that i know of that offer it to large groups … and then another 30 individual players that have it available for their friends and teams … and those are just the ones i know about … so this idea that it’s not available to everyone is kinda silly.

[LEER0YJENKINS1]

@LEER0YJENKINS1

In another thread you said (@PGGalileo) that you are putting shuffle on the back burner for a while. I hope that means some work can return to the API which needs some serious LOVE. Here’s where we are:

1. Castle endpoint upped from 25 to 200+ /api/v1/castle_info?cont_ids=
2. Team endpoint updated to include /api/v1/atlas/teams/metadata?k_id=1&realm_name=Celestial_Haven&teams=

"Team": {
    "team_name": "Team",
    "alliance": "AllianceName",
    "roster": [
      {
        "id": string, **NEW** We need SOMETHING even if not pgid to uniquely identify players
        "player_name": "PlayerName",
        "level": integer,
        "position": "Leader/Officer/Member", **NEW**
        "dp": integer, **NEW** Defense Power
        "ap": integer, **NEW** Highest Single Dragon Attack Power (include runes AND rider please)
        "tier": string **NEW** New suggestion as of this moment: what is their current breeding tier. this would be better / more useful than top 3 dragons
        "online": boolean **NEW** Online Status
      },
      ...
    ],
    "free_passages": [
      "Team1",
      "Team2",
      "Team3",
      "Team4",
      "Team5"
    ]
  }
}

3. Castle metadata to include castle element (this is optional as I believe PG is considering some other way to do shard farming after the shuffle), nml / sz access, road connections /api/v1/atlas/castles/metadata/macro?realm_name=Celestial_Haven&k_id=1
4. Events endpoint to include regular game /api/v1/atlas/player/event/score
5. NEW Endpoint: Prims Trained for YOUR team. I don’t know why this was rejected, but it would help us. Level of Prim would be nice, but Tier would be great.
6. NEW Endpoint: Team Player Applicants for YOUR team. It would return: Name, Last or Current Team, Level, DP, AP, Current Tier Breeding, Current Kill Count, Current Troop count, Last 4 Atlas event scores, Last 4 PvP event scores, Last Breed / Fort event score (to be honest, I don’t know how any leader could make a player decision without this data)
7. Ability for Developers to delete our apps
8. Webhook notification when a user REVOKES their apikey
9. A way to see if a castle was surrendered or conquered

Since I last posted this list, I added no. 8 and 9, but 8 is a forgotten request that was made very early on in the API development.

@PGCarlos we are now on 2.5 years since this post on an API update … i think we are well over do for some API love

[Harsha]

Read what I wrote again , either available to all or available to nobody is what I prefer .

[PGCarlos]

i’ve brought up the API and there’s discussion around updates - don’t have any more info right now tho

[LEER0YJENKINS1]

@Harsha

Read what I wrote again , either available to all or available to nobody is what I prefer .

the whole point of this api is that it is available to everyone (equally) … if they aren’t willing to ask for access or have a player develop something (like we all had to do) then that is their CHOICE. but with a public api … it IS available to everyone.

people can’t chose not to get / make an api tool and then complain they don’t have one. grant it, mine requires a no-hit … obviously, I don’t want something I’ve poured thousands of hours into be used against my own team / castles, but that still covers about 1/3 (or more) of all teams in atlas who can gain access to my tools.