Skip to main content
GET
/
2
/
pulse
Get bonding pool information (new, bonding, bonded)
curl --request GET \
  --url https://demo-api.mobula.io/api/2/pulse
{
  "type": "sync",
  "payload": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.mobula.io/llms.txt

Use this file to discover all available pages before exploring further.

This endpoint is available for all plans.

​
GET Method Overview

The GET method allows you to retrieve pulse data by passing parameters in the query string. This method is suitable for simple configurations with basic parameters.

​
Base Endpoint:

https://api.mobula.io

​
Request Format

GET /api/2/pulse
Example Full URL: 
curl -X GET "https://api.mobula.io/api/2/pulse"

​
Asset Mode

By default, the API returns pool-focused data. Set assetMode=true to switch to token-centric analytics with comprehensive token statistics, holder data, and social information. 
GET /api/2/pulse?assetMode=true&chainId=solana:solana&poolTypes=pumpfun

​
Basic Usage Examples

​
Pool-based data (default)

GET /api/2/pulse?chainId=solana:solana&poolTypes=pumpfun&limit=30

​
Token-based data with Asset Mode

GET /api/2/pulse?assetMode=true&chainId=evm:8453&poolTypes=moonshot-evm&limit=50

​
Multiple chains

GET /api/2/pulse?chainId=evm:8453&chainId=solana:solana&poolTypes=pumpfun&poolTypes=moonshot-evm

​
Available Parameters

  • assetMode (boolean): Switch to token-centric analytics (default: false)
  • excludeLPTokens (boolean): In Asset Mode, exclude LP wrapper tokens by requiring poolAddress to be present (default: true). Set to false to include LP wrapper tokens.
  • model (string): Data model - use default for automatic views
  • chainId (string | repeated): Blockchain identifiers
  • poolTypes (string | repeated): Pool types to monitor
  • limit (number): Number of results (max 100, default 30)
  • offset (number): Pagination offset (default 0)

​
Available Pool Types

Full list can be queried on /api/1/system-metadata

​
When to Use GET vs POST

​
Use GET when:

  • Simple configuration with basic parameters
  • URL-friendly parameter passing
  • Basic filtering is sufficient

​
Use POST when:

  • Complex filtering required
  • Custom views configuration
  • Advanced filter combinations
  • Large number of parameters

📝 POST Method

Learn about the POST method for advanced configurations

Query Parameters

​
model
enum<string>
Available options:
default
​
compressed
boolean

Enable compressed response

​
assetMode
boolean

Use asset mode instead of pool mode

​
chainId

Chain ID(s) to filter

​
poolTypes

Pool type(s) to filter

​
excludeDuplicates
boolean

Exclude duplicate pairs (default: true)

​
pagination
boolean

Enable pagination

​
views
object[]

Response

200 - application/json

Pulse endpoint response

​
type
enum<string>
required
Available options:
sync
​
payload
object
required