Skip to main content
GET
Get Coin Metadata

Single Coin Metadata

Endpoint

Authentication

This endpoint requires JWT authentication. Include your token in the Authorization header.

Path Parameters

string
required
The Solana mint address of the coin

Response

object
Metadata object for the coin

Code Examples

Response Example


Bulk Metadata Retrieval

Endpoint

Authentication

This endpoint requires JWT authentication. Include your token in the Authorization header.

Request Body

array
required
Array of Solana mint addresses to retrieve metadata for

Response

array
Array of metadata objects, one for each mint address provided

Code Examples

Response Example


Bulk Coins by Mints

For retrieving full coin data (not just metadata) for multiple mints:

Endpoint

Request Body

array
required
Array of Solana mint addresses

Code Example

cURL
This endpoint returns full coin objects including market data, not just metadata.

Use Cases

Single Coin Metadata

Use the GET endpoint when:
  • You need metadata for a single coin
  • You want to display coin information without market data
  • You’re building a coin detail page

Bulk Metadata

Use the POST /metadatas endpoint when:
  • You need metadata for multiple coins at once
  • You’re building a portfolio view
  • You want to display coin information for a list of mints
  • You need to optimize API calls (fewer requests)

Full Coin Data

Use the POST /mints endpoint when:
  • You need complete coin data including market metrics
  • You’re building a trading interface
  • You need pricing and liquidity information

Notes

  • Metadata is stored on IPFS and cached by Pump.fun servers
  • The single coin endpoint is useful for quick metadata lookups
  • Bulk endpoints are more efficient when dealing with multiple coins
  • Replace <your_token> with your actual JWT token
  • Bulk requests should be limited to reasonable batch sizes (recommend max 50 mints per request)