Sign-in

LiquidPlanner
30-day free trial
30-second sign-up

API Guide > RESTful Resources > Scoping and Nesting of Resources

Developer Forum - Ask the LiquidPlanner development team questions. Note that the LP iPhone app uses this same API.

API Sample Code – See the API in action then give it a try.


Enter a search term or try the Dev Forums for more answers.

LiquidPlanner uses a RESTful web service API. You can download the API Guide (PDF) for offline reference. Most actions that you can perform within the application can be automated using the API -- for example, you can create a task, comment on the task, track time against it, and then mark it done.

NEED HELP? Please post API questions in the API forums


Resources (except for your account and workspaces themselves) are scoped by or nested within a workspace. This scoping is represented in the request path, so e.g. to list the tasks in a given workspace, do:

GET /api/workspaces/:workspace_id/tasks

and to show a single task, do:

GET /api/workspaces/:workspace_id/tasks/:task_id

This nesting pattern may be repeated, e.g. with the comments for a task:

GET /api/workspaces/:workspace_id/tasks/:task_id/comments