Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/planradar:planradar-filters-v2-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: PlanRadar's API Documentation Filters V2 API
version: '2.0'
description: Welcome to PlanRadar's API documentation, here you can find all the details about our APIs as well as test them online.
servers:
- url: /
tags:
- name: Filters V2
description: Read and manage ticket filters
paths:
/api/v2/{customer_id}/projects/{project_id}/filters:
get:
summary: Returns all filters of a project
tags:
- Filters V2
description: This API returns all filters of the logged in costumer.
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
- name: last_sync_date
in: query
description: is a Unix Timestamp. If it is set, only filters that were created after that timestamp will be returned
schema:
type: string
- name: pagesize
in: query
description: sets the number of filters that should be returned per page <br> Maximum is 500, default is 100
schema:
type: string
- name: page
in: query
description: sets the number of pages for the returned filters
schema:
type: string
- name: search
in: query
description: keyword, based on which the roles will be filtered
schema:
type: string
- name: load_all
in: query
description: sets whether or not all filters should be loaded
schema:
type: boolean
responses:
'404':
description: Filters Not Found
operationId: getApiV2ByCustomerIdProjectsByProjectIdFilters
x-operation-id-source: derived
post:
summary: Creates new filter
tags:
- Filters V2
security:
- apiKey: []
description: 'This API is used for creating a new filter.
The filters object contains all the filter data. Each filter is an array that consists of the attributes "predicate" and "value". The default field-keys of the filters object are "sequential-id", "subject", "status-id", "priority-id", "assigned-to-id", "author-id", "created-at", "updated-at", "updated-by-id", "due-date", "progress", "component-id", "company". If a filter is a custom created one its field key will be generated and look similar to the following example. Example: "tf37e04757dabbca63"
Available Predicates: "eq" (=), "starts-with", "ends-with", "like", "not_like", "ge"(>=), "le"(= 3. Filter Example:
{ "data": { "attributes": { "name": "filter_ticketid_greater_than_2", "visibility": 3, "visibile_for_projects": true, "filters": { "sequential-id": [ { "predicate": "ge", "value": "3" } ] } } } }'
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
responses:
'404':
description: Filters not found
requestBody:
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
attributes:
$ref: '#/components/schemas/Filter'
operationId: postApiV2ByCustomerIdProjectsByProjectIdFilters
x-operation-id-source: derived
/api/v2/{customer_id}/projects/{project_id}/filters/check_name_duplication:
post:
summary: Checks for filter name duplication
tags:
- Filters V2
security:
- apiKey: []
description: This API is used for checking if the name of a filter already exists.
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
responses:
'404':
description: Filter Not Found
requestBody:
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
attributes:
type: object
properties:
name:
type: string
description: name of the filter that should be checked
operationId: postApiV2ByCustomerIdProjectsByProjectIdFiltersCheckNameDuplication
x-operation-id-source: derived
/api/v2/{customer_id}/projects/{project_id}/filters/{id}:
get:
summary: Returns specific filter
tags:
- Filters V2
description: This API returns a specific filter based on its id.
security:
- apiKey: []
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
- name: id
in: path
required: true
schema:
type: string
responses:
'404':
description: Filter Not Found
operationId: getApiV2ByCustomerIdProjectsByProjectIdFiltersById
x-operation-id-source: derived
delete:
summary: Deletes specific filter
tags:
- Filters V2
description: This API is used for deleting a specific filter based on its id.
security:
- apiKey: []
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
- name: id
in: path
required: true
schema:
type: string
responses:
'404':
description: Filter Not Found
operationId: deleteApiV2ByCustomerIdProjectsByProjectIdFiltersById
x-operation-id-source: derived
put:
summary: Updates specific filter
tags:
- Filters V2
security:
- apiKey: []
description: 'This API is used for updating a specific filter based on its id.
The filters object contains all the filter data. Each filter is an array that consists of the attributes "predicate" and "value". The default field-keys of the filters object are "sequential-id", "subject", "status-id", "priority-id", "assigned-to-id", "author-id", "created-at", "updated-at", "updated-by-id", "due-date", "progress", "component-id", "company". If a filter is a custom created one its field key will be generated and look similar to the following example. Example: "tf37e04757dabbca63"
Available Predicates: "eq" (=), "starts-with", "ends-with", "like", "not_like", "ge"(>=), "le"(= 3. Filter Example:
{ "data": { "attributes": { "name": "filter_ticketid_greater_than_2", "visibility": 3, "visibile_for_projects": true, "filters": { "sequential-id": [ { "predicate": "ge", "value": "3" } ] } } } }'
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
required: true
schema:
type: string
- name: id
in: path
description: id of the filter that should be updated
required: true
schema:
type: string
responses:
'404':
description: Filter Not Found
requestBody:
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
attributes:
$ref: '#/components/schemas/Filter'
operationId: putApiV2ByCustomerIdProjectsByProjectIdFiltersById
x-operation-id-source: derived
/api/v2/{customer_id}/projects/{project_id}/filters/filterable_fields:
get:
summary: List available filterable fields for a given type
tags:
- Filters V2
security:
- apiKey: []
description: Returns all available filter fields for a given entity type (e.g., tickets, dms, approval-requests). Each field includes its ID, name, type, predicates, and display options.
parameters:
- name: customer_id
in: path
description: ID of the customer
required: true
schema:
type: string
- name: project_id
in: path
description: ID of the project
required: true
schema:
type: string
- name: type
in: query
description: Type of entity to get filterable fields for
schema:
type: string
enum:
- tickets
- dms
- ticket-attachments
- groups
- approval-requests
responses:
'400':
description: Invalid Parameters
operationId: getApiV2ByCustomerIdProjectsByProjectIdFiltersFilterableFields
x-operation-id-source: derived
/api/v2/{customer_id}/projects/{project_id}/filters/list_options:
get:
summary: List available options for a specific field
tags:
- Filters V2
security:
- apiKey: []
description: This API returns all options for a specific field based on its id.
parameters:
- name: customer_id
in: path
description: ID of the customer
required: true
schema:
type: string
- name: project_id
in: path
description: ID of the project
required: true
schema:
type: string
- name: field_id
in: query
description: Field ID for which options are listed (e.g., "ticket.status-id", "ticket.approval-status")
schema:
type: string
- name: type
in: query
description: Type of filter (e.g., tickets, dms, approval-requests)
schema:
type: string
- name: selected_ids
in: query
schema:
type: array
items:
type: string
description: Array of selected option IDs
- name: search
in: query
description: Search term to filter options
schema:
type: string
responses:
'404':
description: Field Not Found
operationId: getApiV2ByCustomerIdProjectsByProjectIdFiltersListOptions
x-operation-id-source: derived
components:
schemas:
Filter:
type: object
properties:
name:
type: string
example: filtername
description: name of the filter - has to be unique
visibility:
type: integer
example: 1
description: 'sets to whom the filter that is being created is visible <br /> 1 = visible to all users, 2 = only visible to in-house users, 3 = only visible to the logged in customer '
visibile_for_projects:
type: boolean
description: set to true if the filter for all projects otherwise it should be false.
filters:
type: object
description: contains the data of the filter
securitySchemes:
apiKey:
type: apiKey
name: X-PlanRadar-API-Key
in: header
externalDocs:
description: Find out more about our development portal
url: https://www.planradar.com/knowledge-base-overview/