Developers
Palworld data, ready for your app.
PALZ exposes the same normalized, versioned snapshot used by the website. It is read-only, cache-friendly, paginated, and currently limited to 60 requests per minute per client.
API v1
No API key required| Method | Endpoint | Purpose |
|---|---|---|
| GET | /api/v1/status | Dataset version, freshness, and collection counts. |
| GET | /api/v1/pals | Paginated Pals. Filters: q, element, work, page, limit. |
| GET | /api/v1/pals/{slug} | One normalized Pal record. |
| GET | /api/v1/items | Paginated items. Filters: q, category, page, limit. |
| GET | /api/v1/items/{slug} | One normalized item record. |
| GET | /api/v1/recipes | Paginated recipes. Filters: q, page, limit. |
| GET | /api/v1/recipes/{slug} | One normalized recipe record. |
| GET | /api/v1/search?q=anubis | Cross-dataset search. |
Pagination
Use page and limit. The default limit is 25 and the maximum is 100 records per request.
Rate limits
Responses include RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset. A 429 also includes Retry-After.
Caching
Public responses use CDN caching with stale-while-revalidate so clients and PALZ infrastructure can share work.
Current throttling is enforced per warm application instance. For globally strict distributed quotas, PALZ will move the limiter to a shared Redis/KV store as API traffic grows.