Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HACKATHON: Add calendarhero api #110

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

Conversation

richard-rance
Copy link
Member

@richard-rance richard-rance commented Sep 27, 2022

Add documentation for the calendar hero APIs that are routed through the api-gateway as a proxy in #179

You can preview the docs on this branch here

Note: I don't want to merge this until we add actual documentation to each of the fields and APIs. We should also decide what to do about Vendasta users that should be able to access multiple CalendarHero instances and partner service accounts.

https://github.com/orgs/vendasta/teams/external-apis @jaycroll @Alkasai

Comment on lines +38 to +66
enum:
- popular
- recent
- a
- b
- c
- d
- e
- f
- g
- h
- i
- j
- k
- l
- m
- 'n'
- o
- p
- q
- r
- s
- t
- u
- v
- w
- x
- 'y'
- z
Copy link

Choose a reason for hiding this comment

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

What's this?

Copy link

Choose a reason for hiding this comment

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

Is this file just an example of how to add CH documentation?

Copy link
Member Author

Choose a reason for hiding this comment

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

I imported the existing API docs from https://api.calendarhero.com/documentation and then changed the server and auth details.

To maintain this file going forward we have two options:

  1. Improve the existing CH API docs and set up a build process to automatically make the same changes that I did while copying updates to this repo.
  2. Use this repo as the source of truth and follow this guide to edit the docs using Stoplight Studio.

If we decide to change from a raw proxy to actually rewriting the request and response bodies (so we can filter out some deprecated fields) then option 2 is the way to go.

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.

None yet

3 participants