Add Task General Error 6500
Hello,
I'm trying to create a task following the guidelines on the API spec, but I can't get it to work. I tried several methidsbut I'm not getting significant enough infomation to figure out what's going on.
I'm trying to create a task following the guidelines on the API spec, but I can't get it to work. I tried several methidsbut I'm not getting significant enough infomation to figure out what's going on.
I tried POSTing the required fields (with and without &flag=internal attached) to: https://projectsapi.zoho.com/restapi/portal/xxxxxxxx/projects/xxxxxxxxxxxxxxx/tasks/?authtoken=xxxxxxxxxxxxxxxxxxx
Payload:
{
"person_responsible": xxxx,
"tasklist_id": xxxxxxxxxxxxxxxxxxxx,
"name": "Test task",
"start_date": "11-13-2018",
"end_date": "11-14-2018",
"duration": 1,
"duration_type": "days",
"priority": "Medium",
"description": "test description",
"uploaddoc": "",
"start_time": "13:00",
"end_time": "13:00",
"owner_work": [],
"work_type": "work_in_percentage",
"custom_fields": {},
"completed_on": "",
"reminder": "",
"json_string": {}
}
Which yields...
{
"error": {
"code": 6831,
"message": "Input Parameter Missing"
}
}
As far as I can tell, all required parameters are there.
Then I tried submitting them via query string, and I'm not getting a useful error:
This method yields...
Via GET:
{
"error": {
"code": 6832,
"message": "Input Parameter Does not Match the Pattern Specified"
}
}
Via POST:
{
"error": {
"code": 6500,
"message": "General Error"
}
}
Are all fields required?
Which fields are optional and what do they default to?
Which is the preferred method: query string or payload?
Which HTTP method is the correct one?
Do you have a working sample URL/payload which I can work off of?
As far as I can tell the API spec doesn't answer this. Any help would be appreciated, thank you.
Which is the preferred method: query string or payload?
Which HTTP method is the correct one?
Do you have a working sample URL/payload which I can work off of?
As far as I can tell the API spec doesn't answer this. Any help would be appreciated, thank you.
Topic Participants
elliot.bradshaw
John Hurdle
Monica P
Greg
815854898@zohoclosedAccount.com
Sticky Posts
Building extensions #10: Fetch customized user inputs, store them globally at the app level, and access them across entities
This data storage concept enables you to store data related to your extension for both entity properties and extension properties. In our previous piece, we looked at how to store data for entities using entity properties. In this post, we'll look atBuilding extensions #9: Store, retrieve, and access entity-specific data in widgets using data storage
Data storage - Overview Storing data related to the extension you are working on is essential. It can be saved as key-value pairs for an entity or extension, known as entity and extension properties, respectively. Data can be saved for the following entitiesBuilding extensions #7: Create custom widgets for a simplified end-user experience
Discover the benefits of using widgets! We explored the significance of widgets, prerequisites, and the availability of JS SDK methods as part of our previous post. In this post, let's go over a detailed example of using widgets along with certain ZohoBuilding extensions #6: Custom user interfaces with Widgets
Welcome to our post on Widgets for Zoho Projects! In our last post, we explored the significance of the connections feature, showed how to use it, and provided an example use case. In this article, we'll look at the importance of widgets, another featureBuilding extensions #5: Integrating applications with Zoho Projects through Connections
In our last post, we discussed the essential features that a Zoho Projects extension can provide. Starting with this post andin every subsequent post going forward, we'll go through each of those features in depth, one by one, with an example use case.