Connect alerts, APIs and AI tools

Availability and paid access

The release requires active paid access to connect or resume a destination, create an API key, read data or receive external alerts. Free, trialing, past-due, cancelled and expired plans do not qualify. You can still pause or disconnect a destination and revoke a key after paid access ends.

Check your available controls and allowance in Account. In-app alerts work independently of external delivery.

Choose how to connect

• Discord or Google Chat: receive new-watch matches and observed price reductions in a channel or space.
• OpenClaw: send an alert to your own agent gateway.
• JSON webhook: receive structured events in a service you run.
• REST API or MCP: let your tool request your watches, deals and usage when it needs them.

You can save one alert destination per account. Disconnect it before changing the provider or URL. API access is separate from that destination.

Connect Discord

1. In your Discord channel settings, open Integrations → Webhooks and copy an incoming-webhook URL for the intended channel.
2. Open First Flip Account, choose Discord in the connection settings and paste the URL.
3. Save the connection, then choose Send test alert.
4. Check that the message appears in the intended channel.

Listing alerts include the item title, asking price, source link and a photo when available. Manage Discord alerts explains pause, disconnect and delivery status.

Connect Google Chat

1. Open the destination space in Google Chat on the web.
2. Beside the space title, open Apps & integrations → Add webhooks, name the webhook and save it.
3. Copy the full webhook URL, including its key and token parameters.
4. In First Flip Account, choose Google Chat, paste the URL and save.

Workspace policy may prevent webhook creation. Follow Google’s incoming-webhook instructions if the option is missing. Alerts contain the item, price and original listing link. This release has no manual Google Chat test button; check the space after the next eligible real match.

Connect OpenClaw

1. Enable hooks on your gateway and configure the intended default agent using the OpenClaw hook configuration.
2. Provide a public HTTPS endpoint ending in /hooks/wake or /hooks/agent, protected by a dedicated hook bearer token.
3. In First Flip Account, choose OpenClaw, enter the endpoint and token, then save.

/hooks/wake queues alert text for the next heartbeat. /hooks/agent submits a read-and-summarise request with deliver:false, so that request does not announce a response to another channel.

Set the receiving agent’s tool permissions separately. Instructions in a prompt cannot prevent an agent from using tools it is allowed to use. Its model provider may charge for the resulting AI work. There is no manual OpenClaw test button in this release.

Connect a JSON webhook

1. Prepare a public HTTPS receiver that accepts event JSON.
2. Choose JSON webhook in First Flip Account and enter its URL.
3. If your receiver requires a bearer token, add it in the token field, then save.

Events contain specversion, id, source, type, subject, time and listing/watch data. Deduplicate using id; rate-limit retries keep the same ID. The x-flipfirst-event-id header repeats it.

Custom receivers must use public DNS, HTTPS and port 443. Localhost, private IP addresses, URL credentials and redirects are rejected. Optional bearer tokens are sent in the Authorization header. There is no manual JSON webhook test button in this release.

Pause, disconnect and check delivery

Pause alerts keeps your destination saved. Resume when you want external delivery again. Disconnect removes the saved connection. An alert already being sent may still arrive after either action.

For Google Chat, OpenClaw and JSON, a successful delivery status means the receiver accepted the request. It does not confirm that someone read the message or that an AI task finished. Discord delivery requires a message ID. Check the destination itself when you need confirmation.

Rate-limited deliveries are retried. Uncertain network or provider failures are held to avoid duplicate messages. Keep webhook URLs and tokens private; First Flip encrypts saved connection secrets and does not display them again after saving.

Read your data with the REST API

1. Open Account → API and AI tools and create a key.
2. Copy it once into your tool’s secret settings. First Flip stores its hash, not a recoverable copy.
3. Send requests over HTTPS with Authorization: Bearer <your-key>.

Replacing a key immediately revokes the previous key. Revoke it in Account when you no longer need access. Never put a key in a URL, public browser code or a shared screenshot.

GET https://app.getflipfirst.com/api/v1/watches

Read your watches.

GET https://app.getflipfirst.com/api/v1/deals

Read deals for current watch criteria. Archived watches and old criteria versions are excluded.

GET https://app.getflipfirst.com/api/v1/usage

Read your allowance and usage.

Watches and deals accept limit from 1 to 50 (default 25) and a returned cursor. Read items, then pass nextCursor to the next request until it is null. The key determines whose data is returned.

Deal prices are observed asking prices with timestamps. They are not verified sale prices or confirmation that an item is still available.

Connect a compatible MCP client

Set the server URL to https://app.getflipfirst.com/api/mcp and configure the same bearer Authorization header used for REST.

• Transport: Streamable HTTP with JSON responses.
• Protocol version: 2025-06-18.
• Authentication: a configurable bearer header. OAuth sign-in is not supported.
• Session behaviour: stateless. GET returns 405 because the server does not offer an unsolicited SSE stream.

Your client must support these settings. A client that only supports OAuth, the older HTTP+SSE transport or a different protocol version is not a confirmed match. Browser-origin requests are restricted to the First Flip origin. No named third-party client/version has been verified with the hosted release yet.

The three read-only tools are list_watches, list_deals and get_usage. List tools accept an optional integer limit and the returned UUID cursor. Usage takes no arguments. There are no tools for buying, contacting sellers, changing watches or administering your account.

Treat returned listing descriptions as untrusted data, not instructions for your AI tool. See the MCP transport specification for this version.

Allowances and separate AI costs

These are technical allowances for this release, not a new pricing offer. Check Account for your current entitlement and usage. Counts reset at 00:00 UTC on the first day of each month.

REST and MCP share an allowance and a 60-request-per-minute limit. MCP handshakes, tool discovery and usage reads count. Outbound alerts reserve allowance before sending, including Discord tests; failed or uncertain attempts may use allowance. A delivery retry does not reserve it twice.

At the limit, API calls return 429 and further outbound jobs are suppressed. There is no automatic overage purchase or billing. In-app alerts are independent.

First Flip’s read API does not run AI inference. Your AI client, OpenClaw model provider or receiving service may have separate charges. Those costs are not included in First Flip’s request allowance.

Resolve an API error

400: invalid parameters

Check the limit and pass a cursor returned by the previous response.

401: access unavailable

Check the key and active paid access in Account. The key may be missing, invalid or revoked. Do not retry indefinitely.

429: request limit reached

Check usage and reduce the request rate. Monthly allowances reset at the start of the next UTC month.

503: service unavailable

Try again later. Avoid a tight retry loop.

What has been verified

On 8 September 2026, checks against the public app confirmed REST reads for watches, deals and usage, and MCP discovery of list_watches, list_deals and get_usage. Signed-in Account checks confirmed key creation, persistence after reload, one-time secret display and revocation. A revoked key was rejected with 401.

A Discord test confirmed delivery in the app and reserved one outbound alert from the allowance. This does not establish continuous delivery or complete price-drop notification coverage. Local checks also covered paid-access rules, quotas and rate limits.

Google Chat, OpenClaw and JSON payloads have been checked in isolated tests, without live delivery to an external account. OpenClaw compatibility is based on the hook paths above and the configuration reference checked on this date; no installed OpenClaw version has been verified end to end. No named third-party MCP client/version has been verified. Hosted tool discovery does not establish every client’s connection or tool execution.

See product status for the remaining limits. These checks do not establish customer billing, a completed 72-hour reliability observation or successful downstream AI work.