I do pull the list of supported aircraft, and know how to pull user custom airframe definitions by their internal ID, BUT what I would like to do with the API is load and specify on our site the so called “variant or airframe” public list for a given airframe, and have that available for selection as well.
Currently a user could pull one of these as a starting airframe, create their own internal ID, give me that ID, and then it can be added and referenced on the call to SImBrief, but obviously a bit cumbersome and not a general solution.
Instead, for example, if there was a json list with the normal types listed, but each entry that has one, a variant field added (NULL if only a default one) OR leave the current type list unchanged and have a separate json list showing all the types that have public variant and their reference ID – and then you offered another API field for specification …
$sb_arg_array['type'] = $sb_type; // current field
$sb_arg_array['type_variant_id'] = $sb_type_variant_id; // proposed additional field
Or, more simply, have an “internal ID” for these publicly available configs in a json list, and just sub that ID in the current aircraft type field, one step easier.
A parallel question, and I expect this is not doable due to privacy issues, but is there a way to query all the personal aircraft profiles created by a given user, for selection when that very user is creating a dispatch, on our site?
For example, say the pilot input his SimBrief pilot ID into our site, and then a call to the SimBrief API could pull all his aircraft profile IDs – and make them also available for direct selection together with all the public ones.
I know that you can have the pilot query the internal aircraft profile ID in his simbrief aircraft profile editor, and provide that manually to our site, for the call for dispatch. But that is not as slick.