Recent creations
Programmatic access to the most recent creations of the user behind your API key.
Recent creations
Fetch the most recent creations withGET /v1/creations/recent. Results are paginated and ordered from newest to oldest. The identity is resolved automatically from the API key — you always get the creations of that key’s user.
Example response
Query parameters
| Parameter | Description | Default |
|---|---|---|
page | Page number to retrieve | 1 |
per_page | Number of creations per page | 5 |
tool_name | Filter by the tool that produced the creation (e.g. text-to-image) | — |
Authentication
Authenticate with theX-Magnific-API-Key header. The user is identified automatically from the API key — you cannot request another user’s creations. See Authentication for details.
Rate limits
The endpoint is limited to 300 requests per minute (300 RPM) per API key. Exceeding it returns429 Too Many Requests.
API reference
Recent Creations
List the user’s most recent creations, newest first
Frequently Asked Questions
Whose creations does it return?
Whose creations does it return?
Always the creations of the user associated with the API key. Identity is resolved server-side from the key, so a client cannot request another user’s creations.
Does it consume credits?
Does it consume credits?
No. The Creations API is a read-only endpoint and does not consume credits.
How do I paginate?
How do I paginate?
Use the
page and per_page query parameters. The response meta.pagination block reflects the current page and page size.Can I filter by tool?
Can I filter by tool?
Yes. Pass
tool_name (for example text-to-image) to return only the creations produced by that tool.