ticket-integrations

Ticket Integrations

Wire a project's ticket board to another system, in both directions:

• Outbound — webhooks. Wick POSTs a JSON event to your endpoint whenever a ticket is created, moved, assigned, or deleted.
• Inbound — REST API. Your system creates and updates tickets with a Personal Access Token.
• Custom buttons. A button on every ticket's page that POSTs the ticket to your URL on click — see Custom buttons.

All three are configured per project, under Project settings → Ticket system → Integrations. All are off (empty) until you add one.

Setup

1. Open Project settings → Ticket system, make sure ticket mode is on.
2. Expand Integrations.
3. For the API: switch REST API on. Copy the base URL shown there.
4. For webhooks: Add webhook, fill in the URL, set a signing secret, pick the events, then Send test to prove the endpoint before a real ticket depends on it.
5. For a custom button: Add button, fill in a label and a URL, and save — see Custom buttons.

You need a Personal Access Token for the REST API. Create one at /profile/tokens — see Access Tokens. A token acts as you: it reaches exactly the projects your user can see, and no others.

::: warning The API toggle is per project A token cannot touch a project whose REST API is switched off — those requests answer 403 with the REST API is disabled for this project. A project you cannot see at all answers 403 you don't have access to this project; one that does not exist answers 404. :::

---

REST API

Base URL and auth

https://<your-wick-host>/api

Every endpoint path in this reference is relative to this base URL — append it as-is. GET /projects/{id}/tickets means:

https://<your-wick-host>/api/projects/{id}/tickets

Every request carries the token:

-H "Authorization: Bearer $WICK_TOKEN"

Set up the shell for every example below:

export WICK_HOST="https://wick.abc.com"
export WICK_API="$WICK_HOST/api"
export WICK_TOKEN="wick_pat_..."
export PROJECT="proj_7f21c9"