Migration Guide (v1 to v2)

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

Migration from v1 to v2

What Changed

v2 introduces improved performance and new features.

Endpoint Changes

Most endpoints remain compatible. Changes:

  • New fields in responses
  • Improved error messages
  • Better pagination support

URL Migration 

# v1
url = 'https://ws.spac.io/api/v1/getProperties'

# v2
url = 'https://ws.spac.io/api/v2/getProperties'

Response Format

All responses maintain compatibility:

{
  "success": true,
  "data": [...],
  "pagination": {...}
}

New Fields in v2

Some responses include additional fields:

  • updated_at - Last modification timestamp
  • source - Data source identifier
  • metadata - Additional context

Migration Checklist

  • [ ] Update base URL in config
  • [ ] Test all endpoints in v2
  • [ ] Verify response parsing still works
  • [ ] Check rate limit handling
  • [ ] Monitor error responses
  • [ ] Update documentation
  • [ ] Plan rollout schedule

Backward Compatibility

v1 will be maintained for 12 months. Use v2 for new projects.

Support

Contact Spacio support for migration questions.