API Versioning Policy

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.lwolf.com/doc/spacio-api/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Spacio API MCP server": {
    "url": "https://apidocs.lwolf.com/doc/spacio-api/mcp"
  }
}
Close

API Versioning

Version Strategy

Spacio uses semantic versioning:

  • Major (v1, v2) - Breaking changes
  • Minor updates - New features, backward compatible
  • Patch updates - Bug fixes

Current Versions

v1 (Stable)

  • Mature, widely used
  • Full feature set
  • Long-term support

v2 (Current)

  • New features
  • Improved performance
  • Enhanced error messages

Upgrade Timeline 

Today        6 months      12 months
  v2            v1           v1
  v1          Support      Sunset

Breaking Changes Policy

  1. Announcement - 3 months notice via email
  2. Transition Period - Both versions available
  3. Sunset - Old version disabled

What Constitutes Breaking

❌ Breaking changes:

  • Endpoint URL changes
  • Required field removal
  • Response format changes
  • Authentication changes

✅ Non-breaking changes:

  • New optional fields
  • New endpoints
  • New status values
  • Performance improvements

Version-Specific Features

v1 Features

  • Basic property queries
  • Lead retrieval
  • Agent authentication

v2 Features

  • All v1 features plus:
  • Enhanced metadata
  • Improved pagination
  • Better error details

Checking Version

Responses include version info:

{
  "success": true,
  "api_version": "2.0.0",
  "data": [...]
}

Support

Contact support@spac.io for version questions.