Bumble

NOT AVAILABLE: Bumble retired the API these routes speak. Its endpoint answers every call, the anonymous handshake included, with 'Session not found (0030-3001-0051)', and the Bumble app does not use that endpoint at all: it speaks a binary protocol over a TLS socket to bma.bumble.com:443. No credentials get through until that transport is built, so these calls answer 502 instead of pretending to sign in. Send a Bumble message: a reply into conversation_id, or a first contact on user_id.

Live endpoint. Credit cost: 1 (1 request = 1 credit).

post/v1/bumble/messages

Request

  • Base URL: https://api.scraper-api.com
  • URL: https://api.scraper-api.com/v1/bumble/messages
  • Auth: API key in header x-api-key

Headers

x-session-idstring required
Example:b6f0a1c2d3e4f5a6b7c8d9e0f1a2b3c4

The session id returned by login. Sent as the x-session-id header.

Request body

messagestring required

The message text.

conversation_idstring

One conversation of the inbox. Omit to list the inbox.

user_idstring

The other member's id on the platform.

Example request

{
  "message": "Ist der Artikel noch verfuegbar?",
  "conversation_id": "412778905",
  "user_id": "12345678"
}

Response

Platform-native JSON payload (ScrapeCreators-compatible).

Changes

No recorded changes to this operation across all 1 revision of this API.