Skip to content

Conversation

lpereira
Copy link
Contributor

No description provided.

Copy link
Member

@s3lph s3lph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @lpereira

Thanks for updating your endpoint. While you're at it, we'd like to recommend the following changes:

  • Your endpoint only claims support for SpaceAPI v0.13, which was released almost (if not more than) a decade ago. Since all you're endpoint's fields are complient with v14 and v15 (the most recent release), in your case upgrading is as simple as adding the necessary versions to the api_compatibility key:
    {
      "api": "0.13",
      "api_compatibility": ["14", "15"],
      ...
    }
    (Starting with v14, we introduced the new api_compatibility field to claim support for more than one version. v0.13 support can still be advertised in the legacy api key.)
  • Your endpoint does not set a CORS header. This prevents it from being queried in browser-based clients. To resolve this, simply add a Access-Control-Allow-Origin: * header to your endpoint's response.

You can check your endpoint for issues yourself using our validator: https://validator.spaceapi.io/ui/?url=https://status.lhc.net.br/

@lpereira
Copy link
Contributor Author

Yeah, I know. I'm unfortunately using the spaceapi integration from Home Assistant and they only support version 0.13. I'll poke around and see what I can do there.

Thanks!

@s3lph
Copy link
Member

s3lph commented Mar 15, 2025

Yeah, it's a known issue that the Home Assistant integration still only supports v0.13, see home-assistant/core#109158

@s3lph s3lph merged commit 4701beb into SpaceApi:master Mar 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants