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-forms-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 Approval Requests V2 Forms 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.<br />\n <h5>Rate Limits</h5>30 requests per minute per account, aggregated across all tokens.<br />\n If the threshold is exceeded, a 5-minute cooldown is applied to the account, aggregated across all tokens.<br />\n During the cooldown period, further requests may be rejected until the cooldown ends.<br />\n In rare cases, an endpoint may have a different rate limit than the default. When that happens, the differing limit will be explicitly stated in the API documentation for that endpoint.<br />\n <h5>Access Key</h5>In order to be able to access any API you have to create an access token.Therefore you have to follow these steps:-\n <ul>\n <li>Go to your profile page and click on Personal Access Tokens on the left side bar</li><li>Click on the 'Create Access Token' top right button in order to create a new access token.</li><li>Copy the created token and paste it into the field that pops up when you click on the 'Authorize' button </li><li>Note: you can copy the token only once.</li><li>Now you can easily access any API</li>\n </ul>\n <h5>V2 APIs</h5>We are currently working on upgrading all our APIs to v2, and we recommend that you use v2 APIs if it is available.\n <p>V2 APIs are faster, robust and more flexible than v1 APIs</p>"
servers:
- url: /
tags:
- name: Forms V2
description: Get your PlanRadar forms
paths:
/api/v2/{customer_id}/projects/{project_id}/ticket_types/ticket_type_project:
get:
summary: Returns all ticket types of a specific project
tags:
- Forms V2
security:
- apiKey: []
description: This API returns all forms aka ticket_types of a specific project or all the projects the user is involved in.</br>
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
- name: project_id
in: path
description: if you want to load the ticket types of all projects set the project_id to 0
required: true
schema:
type: string
- name: last_sync_date
in: query
description: is a Unix Timestamp. If it is set, only ticket types that were created after that timestamp will be returned
schema:
type: string
- name: page
in: query
description: sets the number of pages for the returned ticket types
schema:
type: integer
- name: pagesize
in: query
description: sets the number of ticket types that should be returned per page<br/>Maximum is 500, default is 100
schema:
type: integer
- name: apply_form_display_permission
in: query
required: false
description: (KFT-338) when <code>true</code>, filters bound ticket_type_projects to forms the caller's role can see (<code>capabilities.visible_to</code> match or unrestricted). Watchers bypass. Results are cached per flag value. Default <code>false</code>.
schema:
type: boolean
- name: apply_form_edit_permission
in: query
required: false
description: (KFT-338) when <code>true</code>, filters bound ticket_type_projects to forms the caller's role can edit (<code>capabilities.editable_by</code> match or unrestricted). Independent of the display flag. Default <code>false</code>.
schema:
type: boolean
responses:
'406':
description: Unsupported Accept Header
components:
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/