Skip to main content

Memida REST API

The Memida API follows the REST architecture style and provides a standardized interface to the platform. Through HTTP methods such as GET, POST, PUT, and DELETE, plus JSON as data format, you can access Memida data directly.

Typical API scenarios:

  • Synchronization of master data with ERP, MES, or CMMS systems
  • Creating and updating test equipment from external systems
  • Automated reporting in BI tools
  • Integration into own portals and internal applications

Set up API access​

Before you can use the API, you need an API token:

  1. Open your user profile in Memida.
  2. Navigate to the API settings.
  3. Generate a token and store it securely.

The token must be sent in the Auth header with every request.

Base URL​

All API requests are made via:

https://api.memida.de/api/v1

You can find the full API reference in the API documentation.

Authentication and standard headers​

-H "Auth: live YOUR_API_TOKEN"
-H "Accept: application/json"

For POST and PUT requests, add:

-H "Content-Type: application/json"

Practical examples​

Replace YOUR_API_TOKEN with your token. All UUIDs in the examples are placeholders; use the IDs of the appropriate records in your Memida inventory. If additional required fields have been configured for inspection equipment or inspection reports, provide their values under customFields as described in the corresponding API reference.

Fetch inspection equipment​

curl -X GET "https://api.memida.de/api/v1/apparatuses" \
-H "Auth: live YOUR_API_TOKEN" \
-H "Accept: application/json"

Search for PS-13N, sort by ID no. in ascending order, and return 50 entries per page:

curl -X GET "https://api.memida.de/api/v1/apparatuses?search=PS-13N&limit=50&page=1&sort=identno&direction=asc" \
-H "Auth: live YOUR_API_TOKEN" \
-H "Accept: application/json"

Create new inspection equipment​

New inspection equipment requires identno, costcenter_id, and apparatus_basedata_id. The following example enables the calibration requirement with checkup: true and sets the inspection interval to twelve months using check_interval and interval_unit. Use an existing cost center and suitable device master data.

curl -X POST "https://api.memida.de/api/v1/apparatuses" \
-H "Auth: live YOUR_API_TOKEN" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"identno": "PS-13N-01",
"serial_number": "DM-2024-001",
"costcenter_id": "8b8a2528-c1a4-4bc2-8d57-9ce45b033f65",
"apparatus_basedata_id": "346dbd74-b81d-5e1b-87a1-1a86f4b9e881",
"checkup": true,
"check_interval": 12,
"interval_unit": "months"
}'

The API reference for creating inspection equipment lists all available fields.

Create an inspection​

An inspection report requires apparatus_id, checked_at, and inspection_result. For apparatus_id, use the ID of existing inspection equipment or the ID returned when creating it. checked_at contains a date and time; the example also specifies the time zone offset. The technical field inspection_result contains the use decision; operational means Fit for use. The type calibration identifies a calibration and is taken into account when calculating the next inspection date.

curl -X POST "https://api.memida.de/api/v1/inspections" \
-H "Auth: live YOUR_API_TOKEN" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"apparatus_id": "91c2feba-37b0-5f0b-9e98-98c79baa4e41",
"checked_at": "2026-01-29T10:00:00+01:00",
"type": "calibration",
"inspection_result": "operational"
}'

The API reference for creating an inspection report describes other use decision values, optional fields, and file uploads.

Query master data​

curl -X GET "https://api.memida.de/api/v1/manufacturers" \
-H "Auth: live YOUR_API_TOKEN" \
-H "Accept: application/json"

Inspection intervals and digital calibration certificates​

In the inspection equipment list, checkinterval_number contains the inspection interval as a string combining a number and unit, such as "4 months". If either the number or the unit is missing, the value is null. Use the separate fields check_interval and interval_unit for further processing.

Immutable DCC inspection reports

Finalized DCC inspection reports are protected against subsequent editing and deletion through the REST API as well. This applies to DCCs created in Memida and confirmed DCC imports. Review and correct the details in the creation workflow or during import before creating the inspection report.

The XML and PDF files associated with a finalized DCC, as well as imported source files, cannot be deleted separately or shared through public file links without authentication. Downloads require authentication and the necessary inspection equipment and inspection report permissions. A DCC's electronic seal applies to the XML file. The associated PDF view represents its contents; an additional PDF attachment uploaded separately is not covered by this seal.

Further documentation​