/v1/. There is no version header.
Build for change
- Ignore fields you do not know. New fields can appear in an answer at any time. Your code must not break on them.
- Do not rely on the wording of errors. Decide from the HTTP status. Texts can improve at any time.
- Do not rely on the order of fields.
- Send only the fields a route documents. Most routes ignore unknown fields today, but the connections import refuses them.