Documentation
One subsection per page, so each topic stays readable. Use the tabs above to move between them.
Drop-in iframe
One endpoint serves every app. Theme, button colour and the displayed app name are query parameters, so the same portal matches whichever app is hosting it.
<iframe src="https://issue-ticca.buyerkraze.com/tickets/get-ticket-portal/issue-ticca-portal/?theme=#0891b2&button_color=#006C73&app_name=issue-ticca.buyerkraze.com&embed=1" style="width:100%;border:0;height:640px" title="Support tickets"></iframe>
The page is served with frame protection exempted, so a managed app on another origin can
embed it. Everything else in the portal stays SAMEORIGIN.
Parameters
| Parameter | Effect |
|---|---|
| app | Slug of the app the tickets belong to. Defaults to the portal itself. |
| app_name | Name shown to reporters. Defaults to the app's domain. |
| theme | Accent colour as a hex value; falls back to the app's brand colour, then to issue-ticca. |
| button_color | Button colour; defaults to the accent. |
| embed | 1 renders the stripped, iframe-friendly layout. |
Hex values must be URL-encoded: #22d3ee becomes %2322d3ee.
Auto-resizing
The embedded page reports its height, so the host can grow the iframe instead of showing a scrollbar:
window.addEventListener('message', function (event) {
if (event.data &&
event.data.type === 'issue-ticca:ticket-portal-height') {
document.querySelector('iframe').style.height =
event.data.height + 'px';
}
});
What reporters can do
Raise
Title, details, the screen or endpoint, and a priority of normal or high.
Follow
Their own ticket history, details, and the conversation โ internal agent notes stay hidden.
Close or reopen
Once resolved, the reporter confirms the fix or reopens it. Reopening is counted, so a ticket that keeps coming back is visible.
Why not critical?
Critical and negligible are reserved for the assigner: reporters describe impact, the team triages severity.