The Plutio API lets you read and write data in your Plutio workspace from your own code. Use it to automate repetitive work, connect Plutio to other tools, or build your own UI on top of the platform. It works well with tools like N8N, Make (formerly Integromat), and Zapier, as well as custom scripts and backend apps.

All endpoints follow REST conventions and return JSON. You read data with GET, create with POST, update with PUT, and delete with DELETE. HTTP status codes tell you if something went wrong.

A few things worth knowing upfront:

• Authentication - every request needs an OAuth 2 bearer token in the header. See the Authentication section to get started.
• Filtering and Search - all GET endpoints support key-value filters and MongoDB-style queries, including text search with $regex. See Filtering and Search.
• Pagination - use skip and limit to page through results. See Paging.
• Rate limit - you can make up to 1,000 requests per hour. Going over that returns a 429 error.

1 October, 2024

Introduction of new endpoints to support our latest feature updates:

• Bulk select and edit
• Archiving
• Schedulers
• Transactions

Also in this update, we introduced a way to get invitation URL and remove all items from trash via our API.

We use a standard OAuth 2 authentication method.

You can generate an application key and a secret code from your settings page inside the Plutio app and use them to create a temporary access token.

YOUR_PLUTIO_SUBDOMAIN header value should be the first part of your Plutio domain. For example YOUR_PLUTIO_SUBDOMAIN value for https://test.plutio.com would be test.

Visit the "Getting Started" section for more information.

You can make up to 1,000 API requests per hour per API key. If you go over that, you will get a 429 Too Many Requests response.

If you hit the limit, wait before retrying. A simple back-off works well: wait 1 second, then 2, then 4, and so on. The limit resets every hour.

You can use skip and limit query parameters to get a different set of items.https://api.plutio.com/v1.8/tasks?skip=20&limit=50This will return tasks 21..70

All GET endpoints support filtering. You can either pass simple key-value pairs in the URL, or use the q parameter for more complex queries using MongoDB query syntax.

Basic filtering

Add field names and values as query parameters. Dot notation works for nested fields.

Advanced filtering with the q parameter

For more powerful queries, pass a MongoDB query object as the q parameter. The value needs to be valid JSON. You can use operators like $or, $and, $regex, $in, $gte, $lte, and more. This works on every GET endpoint.

Text search with $regex

Use $regex to search by a keyword. Add $options: "i" to make it case-insensitive.

Filter by assignee

The assignedTo field is an array. You can query it directly and MongoDB will match tasks where the array contains that person ID.

To get tasks with no assignee:

Filter by custom field value

Custom field values sit inside a customFields array on each record. Use $elemMatch to find records where a specific custom field has a specific value.

Date ranges

Use $gte for "on or after" and $lte for "on or before".

Combining conditions

Use $and when all conditions must match, or $or when any one of them should match.

Important: the q value must be a valid JSON string. In your code, wrap it with encodeURIComponent() before adding it to the URL.