Versioning

Looms APIs may be versioned in the request path.

Examples may include route segments such as v1, v2, or v21.

Versioning Rules

• use the exact endpoint path shown in the API Catalog
• do not remove or change version segments in the URL
• treat different path versions as separate contracts
• test every version upgrade before rollout

Integration Guidance

When implementing a versioned endpoint:

• code against the documented request and response schema for that version
• avoid assuming backward compatibility across different versions
• verify payload changes, required fields, and response shapes during upgrades
• coordinate migrations with your Looms or AND Global technical contact when needed

If A New Version Is Introduced

If a newer version becomes available:

1. review the new endpoint contract in the API Catalog
2. compare request and response differences
3. validate authentication and environment compatibility
4. test before replacing an existing production integration

Source Of Truth

Always use the generated API reference as the contract for the version you call.