Fix the schedule entry create cURL example#412
Conversation
There was a problem hiding this comment.
Pull request overview
This PR corrects the “Create a schedule entry” cURL example in the Schedule Entries documentation so the ends_at timestamp reflects the two-hour meeting shown in the JSON request example. This is a documentation consistency fix within the Basecamp API docs.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Changes:
- Update the cURL payload for “Create a schedule entry” so
ends_atis02:00:00Zrather than matchingstarts_at.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c6593a62d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Small docs fix: the "Create a schedule entry" cURL example's
ends_atwas identical to itsstarts_at, while the JSON request example above it shows a two-hour meeting. The cURL payload now matches — copying it creates the meeting the example describes.Documentation-only; no API changes.