How it works
The relay has two halves:
- Sender — on the origin site you add a service of type Onyx Relay, whose credentials are the remote site's URL and an API token. When an article is dispatched, the relay forwards a snapshot of it to the remote site.
- Receiver — the remote site exposes
POST /api/index.php/v1/mokonyxsocial/receive, which reconstructs the article and runs the same enqueue logic it uses for its own content — so it queues posts to its own services, under its own rules and templates.
Setting up the sender
- On the receiving site, create a Joomla API token for a user with the Manage permission on Mokonyx Social.
- On the sending site, go to Components → Mokonyx Social → Services and add an Onyx Relay service.
- Enter the receiving site's base URL and the API token, then publish the service.
- Publish or dispatch an article — it will be forwarded to the remote site and queued there.
Loop and duplicate protection
Relayed posts are stamped with their origin (origin site + origin id). The receiving site skips the relay service for origin-tagged posts (so two sites can't bounce a post back and forth), and re-sends are de-duplicated on the origin identity. This keeps a multi-site network safe from infinite loops and double-posting.
Requirements
Both sites must run MokonyxSocial with the Web Services plugin enabled. The receiving endpoint requires the Manage permission (enforced on the API token). See Permissions & Access Control.