Skip to content

Mismatching between Openapi specification and api call results #53

Description

@villaflaminio

I have noticed some differences between the response model reported in the OpenAPI specification and the actual API response.
I am referring specifically to the /export APIs, where I have noticed that some of the fields in the response are not defined in the specification.
For example , by calling the API https://console.runzero.com/api/v1.0/export/org/services.json I see that these fields are present in the response but not in the specification:

  • service_organization_id
  • service_source_ids
  • service_custom_integration_ids
  • service_protocol # Spec says string, Response uses array
  • service_has_screenshot
  • service_screenshot_key
  • os_vendor
  • os_product
  • hw_vendor
  • hw_product
  • hw_version
  • tag_descriptions
  • subnets
  • software_count
  • first_task_id
  • first_task_created_at
  • service_protocols # Spec: service_ports_protocols
  • service_products # Spec: service_ports_products
  • source_ids
  • custom_integration_ids
  • custom_integration_names
  • surface_types
  • outlier_score
  • outlier_raw
  • risk_rank
  • modified_risk_rank
  • criticality_rank
  • ownership

I am also experiencing this issue with other export APIs. Could you please clarify this for me?
Thank you for your support.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions