Jenkins Pipeline
Append the webhook call to your Jenkinsfile using the curl step. Replace WEBHOOK_SECRET with the key generated in your dashboard. The pipeline will pause until JSON-Werkstatt returns a 200 OK with a validation_passed flag.
CI/CD Integration
Configure Webhooks
Your precise tool for JSON data
Setup Guide
Connect JSON-Werkstatt to your build servers to trigger automated schema validation and payload transformation on every commit. The webhook endpoint expects a POST request with a valid Bearer token and a JSON body containing the repository metadata.
GitLab CI
Define a validate_json stage in .gitlab-ci.yml. Use the curl command within the script block to POST your payload to https://api.json-werkstatt.de/v1/hooks/validate. Set the CI_JOB_TOKEN as the authorization header for secure handshakes.
Payload Structure
Standardize your webhook submissions by following the required schema. JSON-Werkstatt parses the source_ref, trigger_type, and data fields to route your request to the correct validation engine.
Schema Validation Event
{"event": "schema_check", "source_ref": "refs/heads/main", "trigger_type": "push", "data": {"file_path": "/configs/api-schema.json", "version": "2.4.1", "strict_mode": true}}
Transformation Trigger
{"event": "transform", "source_ref": "refs/heads/develop", "trigger_type": "merge_request", "data": {"input_format": "xml", "output_format": "json", "ruleset": "flatten_nested_objects", "timeout_ms": 5000}}