LaunchLibraryDev

Due to numerous requests, we will renaming some of our statuses to more appropriate names and adding some new launch statuses on April 9th. The new status structure is as follows:

1. GO == Confirmed launch date and time by a reputable source. Formerly Green

2. TBD - Unknown date or time; scrub with no backup window specified, or no sourced date/time available yet. Formerly Red.

3. Success - Same as before, a successful launch and deployment of primary mission.

4. Failure - Launch failed, same as before.

5. HOLD - This is for UNPLANNED holds only.

6. In Flight - Visual confirmation of liftoff

7. Par

The 1.4 version of the api is now in open beta. This includes two major additions:

1. Added payloads array to missions:
   Payloads are a child array of objects in missions. The purpose is to prove more information about the satellites, telescopes, rovers, probes, crew and the like for each mission. Properties include name, description, country codes, agencies, dimensions weight, number of payload type (an example would be a crew of 7, or many cubesats), and type. This is brand new, so it will take some time for data to be collected and entered, especially for historical launches, so don't worry if something seems missing - we're on it.

2. Added changed property to

Good day, all. I'm pleased to announce the 1.3 version of the API. Changes:

• Filters now work with /next

• NEW: Launch Service Provider s (LSPs)

• LSPs are Agencies with a flag set (islsp)

• Launches now have an LSP property pointing at their agency, so it is clear who is providing launch services

• You can get a list of LSPs by calling /lsp or /agency?islsp=1

• All previous launches have had their LSP attatched, so all the data is ready to be used.

https://launchlibrary.net/docs/1.3/api.html

This release starts a two-week "beta" process (for lack of a better term). Essentially, if anyone comes across a glaring issue, I may make minor changes to it over the next two weeks (af

After some discussion, we have added suborbital and test flight mission types to the system. No code change was necessary, so they are available right now.

As we haven't gotten any bug reports in the last few weeks, we're locking the 1.2 api as in release. This means the feature set is locked in, and no new development will happen for it/it will not be taken down to add anything. In case you missed the original thread and don't want to open it:

We've added some new data points to our api returns in the 1.2 version. You can find the documentation here: http://launchlibrary.net/1.2/docs/api.html

For those using 1.1, calls should be made the same, and the return structures should be the same (with some new properties), so you should be able to simply change your URLs from 1.1 to 1.2 to begin checking.

Some of the new features:

• More URLs! La

Hi folks,

We've added some new data points to our api returns in the 1.2 version. You can find the documentation here: http://launchlibrary.net/1.2/docs/api.html

Calls should be made the same, and the return structures should be the same (with some new properties), so for the most part, you should be able to simply change your urls from 1.1 to 1.2 to begin checking.

Please keep in mind this is open beta. If we find any glaring bugs during this time, we may take it down temporarily while fixing. The current plan is to end the open beta in the beginning of April and cement it in. There are currently no plans to remove either 1.0 or 1.1, so you do not need to move at this time, however you

Hi all, I made a small change this morning to the behavior of the next command for launches. It used to return launches with a net > the current time. Now I am returning net > current time minus an hour. This should keep launches in your lists during countdowns when in hold/being scrubbed, etc.

I just wanted to leave some warning for you folks. It should be seamless. Server moves never cause problems, right?

I will post here again when it is done and we feel it is stable. The old server will remain open for a little while afterwards keep folks from erroring while DNS propagates.

Ok folks, no one has come up with anything major for a while now, so I'm locking 1.1 in. The 1.0 api will still stay up and running so older apps should see no interruptions.

Read here for the list of changes: https://www.reddit.com/r/LaunchLibrary/comments/3mow7q/library_api_11_beta/ (some are in comments as well).

Main API docs are here: http://launchlibrary.net/1.1/docs/api.html

If anyone does come across a bug, feel free to let me know here and I'll fix it as soon as I'm able, thanks.

Greetings folks, (man this became a wall of text fast...)

I've put up the 1.1 version of the API for public beta. Documentation can be found here: http://launchlibrary.net/1.1/docs/api.html

The input certainly differs, but at this time, the format of the responses themselves are the same as 1.1, so there will be no need to change existing handlers.

Major changes include:

• GETs instead of POSTs.

• URL parameters instead of posting JSON bodies

• Support for using multiple values for the same parameter where appropriate, for example id=120&id=121 would return objects with an ID of 120 and 121, should they exist. Things like start and end dates on launches do not support this.

• Pro