Versioning strategy
The PingRep API uses URL-based versioning. The current version is v1 and all endpoints are prefixed with /api/v1/.
When we introduce breaking changes, they will be released under a new version prefix (e.g., /api/v2/). The previous version will continue to work for a deprecation period of at least 6 months.
Non-breaking changes
We may add new fields to response objects, new optional parameters, or new endpoints without incrementing the version. Your client should be written to ignore unknown fields gracefully.
What counts as a breaking change
| Breaking (new version) | Non-breaking (same version) |
|---|---|
| Removing a response field | Adding a new response field |
| Changing a field's type | Adding a new optional parameter |
| Removing an endpoint | Adding a new endpoint |
| Changing required parameters | Expanding enum values |
| Changing authentication method | Adding new error codes |
Recent changes
March 2026
API launch (v1)
- Initial public release of the PingRep REST API
- Authentication via magic link (JWT) and API keys
- AI Representative endpoints (ask, chat with streaming)
- Directory search with filters
- Profile management (CRUD)
- Content management (blog posts, social links)
- Billing and subscription management via Stripe
- Organizations and team member management
- MCP Server for AI tool integration
- Rate limiting with per-tier allowances
Planned
| Feature | Target | Status |
|---|---|---|
| Webhooks | Q2 2026 | In development |
| Official TypeScript SDK | Q2 2026 | Planned |
| Official Python SDK | Q3 2026 | Planned |
| Batch API operations | Q3 2026 | Planned |
| Analytics API | Q3 2026 | Planned |
Migration guides
Migrating from Keynodex/KeynodeCard APIs
If you were using the previous Keynodex or KeynodeCard domains, update your integration:
| Old | New |
|---|---|
api.keynodex.com | api.pingrep.com |
api.keynodecard.com | api.pingrep.com |
keynodex.com | pingrep.com |
The endpoint paths and authentication methods remain the same. Only the base domain has changed.
Old domains sunset
The previous API domains will continue to redirect for a transition period. Update your integrations to use api.pingrep.com as soon as possible to avoid disruption.
Deprecation policy
- Minimum notice: 6 months before removing any API version or endpoint
- Communication: Deprecation notices appear in this changelog and via email to all API key holders
- Headers: Deprecated endpoints return a
Sunsetheader with the removal date and aDeprecationheader with a link to the migration guide
Stay updated
Check this page regularly or contact support@pingrep.com to be notified of upcoming changes.