PingCode Open API

Problem

Work items, projects, sprints, comments, and workloads in PingCode are spread across many REST endpoints. Manual paging, cross-endpoint data collection, and report scripting create repetitive work; in self-hosted setups, an incorrect /open path can also return HTML instead of JSON.

How It Works

The skill wraps the PingCode Open API as a configurable data access layer:
- Uses PINGCODE_BASE_URL and PINGCODE_OAUTH2_ROOT to adapt to public cloud or self-hosted deployments.
- Supports enterprise tokens for organization-wide data and user tokens for personal data such as “my work items”.
- Provides a general caller covering 588 endpoints across 70 groups, allowing group lookup before calling a target endpoint.
- Includes ready-made entries for common flows such as project lists, work item CRUD, sprints, comments, workloads, and weekly report generation.

Limits and Notes

• Rate limit is 200 requests per minute, and tokens are valid for about 30 days.
• Some list endpoints ignore page_size, and total may be inaccurate; pagination should stop based on the actual number of returned records.
• Self-hosted deployments usually need the API root with /open, while the OAuth2 root does not.
• Credentials are stored in a local .env file, and enterprise and user token credentials should be configured separately.