fixed openapi specification

[pk8189]

What does this PR do?

Fix the errors in the OpenAPI specification

OpenAPI linting before:
"errors": 52,
"infos": 4,
"warns": 1538

After:
"errors": 0,
"infos": 4,
"warns": 1538

• Fixes Multiple or incomplete openAPI specs #17314

Visual Demo (For contributors especially)

Functional Python and Typescript SDKs created using the fixed specification:
https://github.com/Sideko-Inc/calcom_py
https://github.com/Sideko-Inc/calcom_ts

Mandatory Tasks (DO NOT REMOVE)

• [x ] I have self-reviewed the code (A decent size PR without self-review might be rejected).

• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  I'm assuming this new spec needs to be fed into your documentation provider.

• [ N/A] I confirm automated tests are in place that prove my fix is effective or that my feature works.

[vercel]

@pk8189 is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "fixed openapi specification". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (03/26/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (03/26/25)

1 label was added to this PR based on Keith Williams's automation.

[TusharBhatt1]

The issue states issue with docs/api-reference/v1/openapi.json while the PR has changes to docs/api-reference/v2/openapi.json

[pk8189]

The issue states issue with docs/api-reference/v1/openapi.json while the PR has changes to docs/api-reference/v2/openapi.json

Hi Tushar, should I create a new issue? As you can see in the description, there were 51 issues with the v2 OpenAPI specification, which is also mentioned in the issue.

[keithwillcode]

@pk8189 Thanks for the fixes. I'm curious - do you know the root cause? We currently auto-generate this doc so even with these fixes, more errors will pop up if we don't fix root cause.

[TusharBhatt1]

The issue states issue with docs/api-reference/v1/openapi.json while the PR has changes to docs/api-reference/v2/openapi.json

Hi Tushar, should I create a new issue? As you can see in the description, there were 51 issues with the v2 OpenAPI specification, which is also mentioned in the issue.

Hey , you can create a new issue - the point is the issue and the PR doesn't really match.
Plus as Keith mentioned these files are auto generated - I guess you have done manual changes , so investigating and fixing the root cause is the ideal fix

[TusharBhatt1]

@pk8189 still working on it ?

[TusharBhatt1]

Thanks for the PR , closing it due to staleness (let me know if you wish to continue)