Call an Ars Nova plugin REST route
ans_rest_callInvoke any REST route in Ars Nova's own namespaces to access plugin capabilities that lack a dedicated tool, so new endpoints work immediately without rebuilding the connector.
Instructions
Call any route in one of the Ars Nova plugins' own REST namespaces. Use this for capabilities that have no dedicated tool yet — it means a new plugin endpoint is usable the moment it is deployed, with no connector rebuild.
RESTRICTED BY DESIGN to namespaces we author: ars-nova/v1, ans-ops/v1, ans-notes/v1, ansg/v1. It cannot call wp/v2, wc/v3 or third-party plugin routes — those have their own purpose-built tools with validation this does not provide.
Environment safety: this goes through the same client as every other tool, so it hits whichever site this connector is configured for. Call wp_check_environment first if you are unsure whether you are on DEV or LIVE.
Useful ars-nova/v1 routes (ars-nova-ticketing-bridge v1.4.0):
GET tickera/introspect — what is ACTUALLY registered: shortcodes, post types, taxonomies, ticket-product meta keys. Use this instead of assuming.
GET tickera/status
GET tickera/events | tickera/event/{id}
POST tickera/event/{id} — update title/date/location/status
DEL tickera/event/{id} — trash (?force=1 to delete)
GET tickera/ticket-types | tickera/ticket-type/{id}
POST tickera/ticket-type/{id} — update price/status/template/stock/virtual
POST tickera/assign-template — { template_id, event_id?, product_ids? }
GET tickera/event-categories — the season's "projects"
POST tickera/event-categories — { name, slug?, description?, ans_page_id? }
POST tickera/event-category/{id} — rename, re-describe, re-link, reassign events
GET tickera/attendees — issued tickets
Args:
namespace (enum): one of the allowed namespaces. Required.
route (string): path within it, no leading slash. Required.
method (enum): GET | POST | PUT | PATCH | DELETE. Default GET.
query (object): query-string parameters.
body (object): JSON body for writes.
response_format (enum): markdown | json.
Returns: the endpoint's JSON response verbatim.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON body for POST/PUT/PATCH, e.g. { title: 'Cross Currents — May 21' }. | |
| query | No | Query-string parameters as an object, e.g. { event_id: 6633, per_page: 20 }. | |
| route | Yes | Route within the namespace, no leading slash. e.g. 'tickera/introspect' or 'tickera/event/6665'. | |
| method | No | HTTP method. Default GET. Use POST to update an existing resource. | GET |
| namespace | Yes | Which of our own REST namespaces to call. Restricted by design. | |
| response_format | No | Output format: 'markdown' for human-readable, 'json' for machine-readable. | markdown |