I really appreciate that you offer an API to easily access the conference info. That being said, if I remember correctly, that’s the third year in a row that the API is changed significantly (different URLs, different data structure).
I’m probably over-thinking this (feel free to tag this as super-low-priority), but at this point, I think it would be great to add some kind of API versioning support. So if you decide to change the API next year, apps could handle the migration gracefully.
Practical suggestions:
Specify HTTP header value (Accept: application/vnd.myapi.v2 + json)
I really appreciate that you offer an API to easily access the conference info. That being said, if I remember correctly, that’s the third year in a row that the API is changed significantly (different URLs, different data structure).
I’m probably over-thinking this (feel free to tag this as super-low-priority), but at this point, I think it would be great to add some kind of API versioning support. So if you decide to change the API next year, apps could handle the migration gracefully.
Practical suggestions:
Accept: application/vnd.myapi.v2 + json
)X-MyAPIVersionRequest-Header: 2
)http://api.mixitconf.org/v2/...
)Many thanks!