Guide

Click "Sign in" and authenticate with your GitHub account (Google sign-in is also supported).

The OAuth flow redirects you to GitHub (or Google), you authorize Signalshoot, and you are sent back to the dashboard.

On your first sign-in, Signalshoot automatically creates your developer account and provisions your first app with a unique App ID, a live API key (fb_live_...), and a test API key (fb_test_...).

There is no separate registration form or email verification step.

After your first sign-in, you are redirected to Settings where your API keys are displayed once.

Copy them immediately — they cannot be shown again.

You get two keys: a live key (fb_live_...) for production use and a test key (fb_test_...) for development.

Feedback sent with the test key is stored separately and does not appear in your production inbox, so you can test freely without creating noise.

If you lose a key or suspect it has been compromised, you can regenerate new keys from Settings at any time — the old key is immediately invalidated.

Add one fetch() call to your app — in a contact form, bug report button, or feedback modal.

The code looks like this: POST to https://your-ingest-url/api/v1/ingest/{YOUR_APP_ID} with an X-API-Key header and a JSON body containing type, message, and optionally channel, user_id, and metadata.

For example: fetch(url, { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-API-Key': 'fb_live_...' }, body: JSON.stringify({ type: 'bug', message: userInput, channel: 'contact-form' }) }).

That is the entire integration.

The Setup Guide page has copy-paste snippets for React Native, Swift, Kotlin, and other platforms.

Send your first feedback using the test API key (fb_test_...) so it does not mix with real production data.

You can use cURL from your terminal, the "Send test feedback" button in Settings, or your actual app code with the test key.

The feedback appears in your inbox within seconds.

Switch to the live key (fb_live_...) only when you are ready to ship.

The difference between the two keys: test-key submissions are flagged as test data and stored separately; live-key submissions appear in your production inbox and count toward your monthly limit.

You can verify the submission arrived by opening the Feedback page in the dashboard.

Once feedback starts arriving, open the inbox and work through items.

A typical triage session: filter to "unread only" or "high priority only" to focus on what needs attention.

Open each item, read the message and any attached metadata (device, OS, app version).

Set the status to "in progress" if you are investigating, or "resolved" if it is already fixed.

Add tags to group related reports — e.g. tag three separate reports about the same crash with "timezone-bug".

Create an action item if the feedback requires a code change, and link related reports to it.

Write a reply if the user included their user_id.

As feedback accumulates over days and weeks, the dashboard's recurring topics section reveals which tags appear most often, showing you where to focus your development effort.