Zum Inhalt springen

Quick Start with Postman

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

For a quick first demo, you may use Postman. We prepared a Postman collection that allows you to step through the most important functions of this API.

  1. Download Postman

    Download the Postman application.

  2. Create credentials

    Create an API Key and API Secret via fiskaly HUB.

  3. Download Environment

    Download the fiskaly SAFE flex Postman environment JSON-based configuration file: Download Postman Environment

  4. Download Collection

    Download the fiskaly SAFE flex Postman collection JSON-based configuration file: Download Postman Collection

  5. Import

    Start Postman and import the downloaded Postman environment and collection files.

  6. Configure

    Update the API Key and API Secret values in the Postman environment to match your credentials.

  7. Upload a file

    For the Upload a file request, select the Body tab, ensure archive_file_request is listed above the file field, and click Select Files to choose the PDF you want to upload.

  8. Run

    Select the fiskaly SAFE flex Postman environment and run the requests one by one in the order listed.

The following requests only need to be executed once per environment. Re-running them will create new annotation schemas with a different random suffix, which is valid but not necessary.

  • Create a configuration — Sets the country configuration for your archive. Run this once before anything else.
  • Create a string annotation — Defines the annotation schema for store information. The annotation name is generated with a random suffix (e.g. receipt_store_info_47832) and saved automatically as an environment variable.
  • Create mix property annotation — Defines the annotation schema for receipt metadata (cashier, amount, payment methods, date). The annotation name is generated with a random suffix (e.g. receipt_metadata_62135) and saved automatically as an environment variable.

Once these are set up, you can run all other requests (Upload, Search, Export, etc.) repeatedly.

The Upload a file request uses multipart/form-data with two fields:

  • archive_file_request — a JSON object containing the file metadata and annotation values (pre-filled automatically via a pre-request script).
  • file — the actual PDF file to archive.

The custom_identifier, file name, and annotation names are resolved automatically on each request via pre-request scripts.

Was this page helpful?