Taps

Cookie taps are essentially bubbles "hi" but your client can choose to render them as 🍪. There is no separate cookie tap type.

Get received taps

Requires Authorization.

GET /v2/taps/received

Response:

• profiles — array of TapProfile

Send a tap

Requires Authorization.

POST /v2/taps/add

Body:

• recipientId — profile id
• tapType — Tap ID, invalid or nonexistent Tap IDs are still recorded as successful

Response:

• isMutual — boolean

Errors:

• 400 — Repeated requests result in Invalid request error and HTTP status 400.

Get sent taps

Requires Authorization.

GET /v1/interactions/taps/sent

Response:

Array of objects:

• senderId — long integer
• receiverId — long integer
• tapType — Tap ID
• sentOn — unix timestamp in milliseconds
• deleted — boolean
• readOn — long integer, unknown or null

Tap ID

Tap ID.

• 0 — FRIENDLY ("hi" or 🍪 based on client's rendering settings)
• 1 — HOT (🔥)
• 2 — LOOKING (😈)
• 3 — NONE

TapProfile

• everything from ProfileMaskedMin
• everything from ProfileMin
• timestamp — unix timestamp in milliseconds
• tapType — Tap ID
• lastOnline — unix timestamp in milliseconds
• isBoosting — boolean
• isMutual — boolean
• rightNowType — string
• isViewable — boolean
• rightNowStatus — RightNowAttributionStatus, Right Now attribution status. Added in app 26.11.0 under key rightNowStatus (distinct from rightNow). or null, optional
• hasChatted — boolean
• unreadMessageCount — integer