Basic information about the API. You can find the technical API docs under 'Integrate' in the portal.
API documentation mainly provides you with information about graphical aspects, delivery specifications, links with data sources, and other explanations.
To use the API, you need an API key. This allows Print.one to securely verify who is sending commands.
JSON is a way to structure data to be passed to a system, such as Print.one. If you are not yet familiar with JSON, you can view it as a list of keys and values that indicate which information should go where. It is the way you send data to Print.one so that your cards can be automatically personalized.
API status codes indicate whether a request was successful or if something went wrong.
Our Print.one API automatically checks whether addresses are filled in correctly when you submit an order. This is to prevent shipping errors. There is a general address check that applies to all countries, and specific validations for the Netherlands, Germany, and Belgium.
Unless otherwise stated in the API documentation, all endpoints have a rate limit of 60 requests every 30 seconds.
Our API supports idempotency, which allows you to safely resend a request without accidentally performing the same operation twice.
Postman is an application used by many developers for testing APIs. On many (marketing) platforms, you can test API requests or webhooks directly, so Postman is not always necessary.
With a CSV file, you can easily create multiple orders simultaneously. Each row in the CSV file becomes a new order (card).
With outgoing webhooks, you automatically receive notifications as soon as something changes in Print.one. Your own systems (e.g., a CRM, dashboards, or external software) can therefore respond directly to these updates. Outgoing webhooks are also called HTTP callbacks.