fix: Use correct parent-child endpoint for TicketNotes (fixes 404 error)#1
Open
aybouzaglou wants to merge 1 commit into
Open
fix: Use correct parent-child endpoint for TicketNotes (fixes 404 error)#1aybouzaglou wants to merge 1 commit into
aybouzaglou wants to merge 1 commit into
Conversation
The Autotask REST API requires TicketNotes to be created using a
parent-child URL pattern (/Tickets/{id}/Notes), not a standalone
endpoint (/TicketNotes).
Changes:
- Changed endpoint from POST /TicketNotes to POST /Tickets/{id}/Notes
- Removed ticketID from payload (now in URL path)
- Updated docstrings to reflect correct endpoint pattern
This fixes HTTP 404 errors when attempting to create ticket notes.
Tested against Autotask instance ww14.autotask.net.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the
autotask_create_ticket_notetool which was returning 404 errors when attempting to create ticket notes.Problem
The Autotask REST API requires TicketNotes to be created using a parent-child URL pattern (
/Tickets/{id}/Notes), not a standalone endpoint (/TicketNotes). The current implementation was using the incorrect endpoint, causing all note creation attempts to fail with HTTP 404.Changes
POST /TicketNotestoPOST /Tickets/{ticket_id}/NotesticketIDfrom request payload (now specified in URL path)autotask_update_ticket_status_with_notehelperTesting
Tested against Autotask instance (ww14.autotask.net):
Related
This fix aligns with Autotask REST API documentation on child collection access URLs.