Getting 404 on Ticket Create

[Derek Gau]

Hi, I'm trying to create tickets via the API and am getting 404s in response, with the message "Tool not found for this project".  I have verified the Tickets tool is installed for the space I'm using (I also created a ticket manually just to be certain).

Request

URL:

POST https://api.assembla.com/v1/spaces/[[space_id]]/tickets.json

Headers:

Content-type: application/json

X-Api-Key: [[Key]]

X-Api-Secret: [[Secret]] 

Body:

{

    "ticket": {

        "number": "",

        "summary": "This is a test ticket",

        "description": "This is the description of the test ticket.",

        "priority": "",

        "created_on": "",

        "permission_type": "",

        "is_story": "false",

        "milestone_id": "",

        "story_importance": "",

        "working_hours": "",

        "estimate": "",

        "assigned_to_id": "",

        "reporter_id": "",

        "hierarchy_type": "",

        "is_support": "false"

    }

}

Response

HTTP-Status: 404

Body

{"error":"Tool not found for this project"}

[Stanislav Kolotinskiy]

Hi Derek,

which is the space? You could contact me directly if you wish not to post space name here.

Regards,
Stanislav

--
You received this message because you are subscribed to the Google Groups "Assembla API Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to assembla-api-d...@googlegroups.com.
To post to this group, send email to assembla...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Derek Gau]

Hey folks - just posting a resolution to this one.  Stanislav found the issue.  

It turns out that you should only pass the is_support parameter when you want the ticket to be created as a Support ticket. The absence of this parameter implies that you're creating an usual ticket.  I resolved the error I was getting by omitting this parameter when it was false (i.e. don't include it in the JSON or XML when it's false).

Ideally, the API should probably be returning an HTTP-400 in this case - not an HTTP-404, which was confusing - but at least there's a simple solution.

They are going to take care of the documentation.

[Derek Gau]

Thanks for the response guys - it's nice to get resolution on something like this in less than a business day. Kudos!

On Wednesday, February 4, 2015 at 12:06:25 PM UTC-6, Derek Gau wrote:

[Stanislav Kolotinskiy]

Thanks for the appreciation, Derek, have a nice day!

Regards,
Stanislav