PHPackages                             prooph/link-processor-proxy - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. prooph/link-processor-proxy

ActiveLibrary[Utility & Helpers](/categories/utility)

prooph/link-processor-proxy
===========================

Processor proxy for prooph LINK

v0.2.0(11y ago)074[1 issues](https://github.com/prooph/link-processor-proxy/issues)2BSD-3-ClausePHPPHP >=5.5

Since Mar 9Pushed 11y ago1 watchersCompare

[ Source](https://github.com/prooph/link-processor-proxy)[ Packagist](https://packagist.org/packages/prooph/link-processor-proxy)[ Docs](https://github.com/prooph/link-processor-proxy)[ RSS](/packages/prooph-link-processor-proxy/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (3)Dependencies (4)Versions (4)Used By (2)

Prooph\\Link\\ProcessorProxy
============================

[](#proophlinkprocessorproxy)

Processor proxy for [prooph LINK](https://github.com/prooph/link)

HTTP Process Trigger
====================

[](#http-process-trigger)

The processor proxy module offers a way to start a process via http request.

Collect Data Trigger
--------------------

[](#collect-data-trigger)

To use this endpoint the process should be startable via a `collect-data` workflow message. What you need to do is send a POST request to the `prooph.link/processor_proxy/api/collect_data_triggers` route defined in your prooph LINK application. By default this route name resolves to the URI `/prooph/link/processor-proxy/api/collect-data-triggers`.

### Request

[](#request)

The POST request should have a JSON body containing following structure:

```
{
  "collect_data_trigger" : {
    "processing_type" : "Processing\Type\Type"
  }
}

```

As you can see the root key "collect\_data\_trigger" contains only a "processing\_type" definition. The type should point to the `Processing\Type\Type` implementation that should be collected by the first task of the process.

### Response

[](#response)

The service respond with a status code 201 and without a body. Instead the header includes a `Location` pointing to a message information service with the UUID of the generated workflow message. The message information service provides detailed information about the status of the message, the triggered process and potentially occurred errors.

Message Service
===============

[](#message-service)

GET Message
-----------

[](#get-message)

- GET `/prooph/link/processor-proxy/api/messages[/:id]` (route: prooph.link/processor\_proxy/api/messages)

Get information about the message identified by its UUID.

Messagebox
----------

[](#messagebox)

- POST `/prooph/link/processor-proxy/api/messages` (route: prooph.link/processor\_proxy/api/messages)

The message service provides the possibility to receive a [service bus message](https://github.com/prooph/service-bus) which is then passed to the workflow engine. The endpoint is mostly used when a sub process or workflow message handler should be triggered via http. In this case the main workflow processor can send a workflow message via the [psb-http-dispatcher](https://github.com/prooph/psb-http-dispatcher) to this endpoint.

Support
=======

[](#support)

- Ask any questions on [prooph-users](https://groups.google.com/forum/?hl=de#!forum/prooph) google group.
- File issues at .

Contribution
============

[](#contribution)

You wanna help us? Great! We appreciate any help, be it on implementation level, UI improvements, testing, donation or simply trying out the system and give us feedback. Just leave us a note in our google group linked above and we can discuss further steps.

Thanks, your prooph team

###  Health Score

24

—

LowBetter than 32% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity50

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~31 days

Total

3

Last Release

4026d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/7341005?v=4)[prooph](/maintainers/prooph)[@prooph](https://github.com/prooph)

---

Tags

modulezf2proophprooph LINK

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/prooph-link-processor-proxy/health.svg)

```
[![Health](https://phpackages.com/badges/prooph-link-processor-proxy/health.svg)](https://phpackages.com/packages/prooph-link-processor-proxy)
```

###  Alternatives

[dkcwd/dkcwd-zf2-munee

Zend Framework 2 module leveraging 'munee' an asset optimisation library developed by Cody Lundquist. You can find munee at http://github.com/meenie/munee

102.1k](/packages/dkcwd-dkcwd-zf2-munee)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)