The Squadron Builder uses a public RESTful API that other tools could interact with to obtain squadron details, costs, or any kind of data, really.

https://squadbuilder.fantasyflightgames.com/api/squads/7c31c7db-ff77-402e-8c3e-b57a7152c2c7/

That is one of my squadrons. The important part is the UUID number at the end, that is present on your browser URL anytime you are looking at your squadron, and any shared link to it, and encoded in the QR.

I remember several community members expressed their despair at FFG not be willing of supporting meta-wing, squadron builders, etc. But here we have it, anyway.
Perhaps we should @ them so that they know they can still use their tools with 2.0?

It's no as simple as that. Some information cannot be easily obtained by using the API from what I could tell. Variable costs are marked like this, for example:

"costs":"*"

And only get their real value when requested from a context where the costs can be resolved (for example when adding as a modification for a ship).

But yeah, as it stands that's very open. I don't believe squad builders would want to let everything run against their API, but it will make imports of changes (or crossimports) very easy.

We'll see if this will remain open. The developers could close this down, hash or encode the data. I haven't seen any official information supporting an open API.

But I think it would be great for the community if the keep it like this or even expand it with some documentation. It would make it simpler for hobby developers to make better apps and mods. Both data data and card images. That would be awesome.

Thank you @Azrapse for posting this. I hope they make a public statement about keeping this API public, that would be reassuring. Is there any way for someone within an app (android or iOS) to be able to find and share a link to their squad in this format?

1 minute ago, J1mBob said:

Thank you @Azrapse for posting this. I hope they make a public statement about keeping this API public, that would be reassuring. Is there any way for someone within an app (android or iOS) to be able to find and share a link to their squad in this format?

The URL to the API is identical all the time, only changing the final part that is the code of the squad.

In the app, you can get the code of the squad by sharing it as FFG forum code. It includes a link with your squad code. Use that code in the URL I posted.

53 minutes ago, Azrapse said:

The URL to the API is identical all the time, only changing the final part that is the code of the squad.

In the app, you can get the code of the squad by sharing it as FFG forum code. It includes a link with your squad code. Use that code in the URL I posted.

Awesome. I’m leaning toward making a FFG API -> XWS converter, but I’m wondering what other members of the community think, like @raithos and whoever is behind LaunchBayNext...

1 hour ago, J1mBob said:

Awesome. I’m leaning toward making a FFG API -> XWS converter, but I’m wondering what other members of the community think, like @raithos and whoever is behind LaunchBayNext...

I have been watching this very closely. However, without the ability to import into the FFG app, it has limited usefulness. I'm hoping that FFG sees the value of importing lists into their builder (for example, someone posts a list they created on these forums, and another person likes it so much they would like to build it) since they already have an export function, then we could adapt YASB lists to work for that import function.

On 9/15/2018 at 12:06 AM, guildmaster said:

We'll see if this will remain open. The developers could close this down, hash or encode the data. I haven't seen any official information supporting an open API.

But I think it would be great for the community if the keep it like this or even expand it with some documentation. It would make it simpler for hobby developers to make better apps and mods. Both data data and card images. That would be awesome.

I'm not sure if they can, actually. They can certainfly obfuscate it (hide a key inside the JavaScript somewhere and encrypt it with that), but as long as your browser does the work in working with the data it has to be readable in some form.

But yeah, if they really put the work in they can certainly make it a **** of a lot more difficult.