This collection covers the full lifecycle of pipeline management, webhook ingestion, and job monitoring for a local API running at http://localhost:3000.
Requests for creating, retrieving, and deleting processing pipelines. Includes pipelines with different processor types:
\nEXTRACT_ISSUE_SUMMARY – extracts structured issue summaries from incoming payloads
FILTER_SENSITIVE – filters out sensitive content before further processing
Also includes negative test cases to validate error handling, such as attempting to create a pipeline with a duplicate slug.
\nRequests for triggering pipelines via webhook endpoints. Covers:
\nSending payloads to named pipeline slugs (e.g., issue-extractor-001, uppercase-test-001)
Testing the sensitive filter pipeline
\nA negative test for routing to a non-existent pipeline slug to verify proper error responses
\nRequests for inspecting the status of background jobs spawned by pipeline executions:
\nRetrieve all jobs currently tracked by the system
\nFetch the details of a specific job by its UUID
\nCreates a new pipeline configured with the FILTER_SENSITIVE action type. This pipeline is designed to intercept incoming webhook events and filter out sensitive data before forwarding the payload to one or more subscriber URLs.
Method: POST
URL: http://localhost:3000/pipelines
Request Body
\nResponse — 201 Created
Returns the newly created pipeline object, including:
\nid — UUID of the pipelinename, sourceSlug, actionType — Echo of the submitted configurationactionConfig — Additional action configuration (null if not provided)createdAt / updatedAt — ISO 8601 timestampssubscribers — Array of registered subscriber objects, each containing their own id, url, pipelineId, and createdAt\n\n","urlObject":{"protocol":"http","port":"3000","path":["pipelines"],"host":["localhost"],"query":[],"variable":[]}},"response":[],"_postman_id":"1d2ae171-753f-477c-bb74-3aa9ffc216ce"},{"name":"Create Pipeline with Duplicate Slug (Negative Test)","id":"7b0dfc5e-b2e0-4e11-a634-c16929964086","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"name\": \"Duplicate Test\",\r\n \"sourceSlug\": \"uppercase-test-001\",\r\n \"actionType\": \"TRANSFORM_UPPERCASE\",\r\n \"subscriberUrls\": []\r\n}","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/pipelines","urlObject":{"protocol":"http","port":"3000","path":["pipelines"],"host":["localhost"],"query":[],"variable":[]}},"response":[],"_postman_id":"7b0dfc5e-b2e0-4e11-a634-c16929964086"},{"name":"Get Specific Job","id":"57fd4a41-7378-4616-bddf-13a80074196d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"body":{"mode":"raw","raw":"","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/api/jobs/a90c8264-b8f3-4925-b1c9-78177a2a7d04","description":"Note: Replace
\nhttps://discord.com/api/webhooks/your-webhook-urlinsubscriberUrlswith a valid webhook endpoint before sending.
Retrieves the details of a single job by its unique identifier. This request targets the local Job Status & Monitoring API and is useful for checking the current state or metadata of a specific job within the pipeline.
\nThe URL follows the pattern /api/jobs/{jobId}, where the UUID segment in the path represents the ID of the job to retrieve. In this example, a90c8264-b8f3-4925-b1c9-78177a2a7d04 is used as the job ID.
A successful response typically returns a JSON object containing the job's details, such as its status, associated pipeline, timestamps, and any relevant output or error information.
\nRetrieves a list of all jobs currently tracked by the system.
\nEndpoint: GET /api/jobs
Base URL: http://localhost:3000
This request fetches all job records from the local API. It is useful for monitoring the status and progress of jobs that have been created as part of pipeline executions. Use this endpoint to get a high-level overview of all jobs in the system.
\nGETA successful response returns an array of job objects, each containing details such as job ID, status, associated pipeline, and timestamps.
\n","urlObject":{"protocol":"http","port":"3000","path":["api","jobs"],"host":["localhost"],"query":[],"variable":[]}},"response":[],"_postman_id":"f220a9ba-451a-442c-8916-0d81c61e4161"},{"name":"Webhook Ingestion","id":"a330b93d-0214-40e4-9b9e-31b0e7277e4e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"message\": \"hello world\",\r\n \"user\": \"john doe\",\r\n \"priority\": \"high\",\r\n \"data\": {\r\n \"action\": \"test\",\r\n \"value\": 123\r\n }\r\n}","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/webhook/uprase-test-001","description":"Sends a webhook payload to a specific pipeline for processing. This request triggers the uppercase-test-001 pipeline, which is designed to process or transform the incoming data (e.g., uppercasing text content). It is the entry point for submitting jobs into the pipeline system.
POST http://localhost:3000/webhook/{pipelineSlug}\nThe request body is a JSON object with the following fields:
\nExample Body:
\n{\n \"message\": \"hello world\",\n \"user\": \"john doe\",\n \"priority\": \"high\",\n \"data\": {\n \"action\": \"test\",\n \"value\": 123\n }\n}\nA successful response indicates that the webhook payload has been accepted and a job has been queued for processing by the pipeline. Typically, this returns a 200 OK or 202 Accepted status along with a job ID or confirmation that can be used to monitor the job's progress via the Job Status & Monitoring endpoints.
Sends a notification to a Discord channel via an incoming webhook URL. This request is used to deliver status updates, alerts, or pipeline event summaries directly to a Discord channel as part of the job monitoring workflow.
\nEndpoint: GET https://discord.com/api/webhooks/your-webhook-url
Replace your-webhook-url in the URL with the actual webhook path generated from your Discord server's channel settings (Server Settings → Integrations → Webhooks).
{{discord_webhook_url}}) to avoid exposing it in the request URL.