Base URL
Authentication
Every request requires an API key passed as a Bearer token in theAuthorization header:
Request format
Send request bodies as JSON with theContent-Type: application/json header:
Response format
All responses are JSON. Successful responses return a2xx status code. Error responses return a 4xx or 5xx status code with an error object:
Pagination
List endpoints support pagination vialimit and offset query parameters:
| Parameter | Default | Max | Description |
|---|---|---|---|
limit | 20 | 100 | Number of results per page |
offset | 0 | — | Number of results to skip |
total, limit, and offset fields.
Error codes
| HTTP Status | Error Code | Meaning |
|---|---|---|
400 | invalid_request | Missing or invalid request parameter |
401 | unauthorized | Missing or invalid API key |
403 | forbidden | API key lacks permission for this action |
404 | not_found | The requested resource does not exist |
422 | unprocessable_entity | Valid request but business rule violation |
429 | rate_limited | Too many requests — slow down |
500 | internal_error | PIK server error — try again later |
Rate limits
The PIK API enforces rate limits to ensure stability. If you exceed the limit, you receive a429 response. Implement exponential backoff when retrying after a rate limit error.
Endpoints
Authentication
API key management reference
Payment Links
Create and retrieve payment links
Transactions
Query payment transactions
Webhooks
Register and manage webhook endpoints
