Skip to main content

Documentation Index

Fetch the complete documentation index at: https://dev.jup.ag/docs/llms.txt

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

This guide covers how to retrieve pending and historical Send invites from the sender’s perspective using the /send/v1/pending-invites and /send/v1/invite-history GET endpoints.

​
Overview

1
Get pending invites.
2
Get invite history.
NOTEBoth of the following endpoints only returns the invites that are set up by the sender and not from the perspective of the recipient.
  • Pending invites: Invites created by the sender that are not yet expired and can be clawback/claimed.
  • Invite history: Invites created by the sender and is either claimed, clawback, or expired. (You can also pass in a Recipient pubkey to get their history)
TIPDepending on how you have set up to allow connection of wallets, either via Jupiter Mobile Adapter for QR code login, wallet extensions, or any other methods, you will need to handle the passing in of their pubkey to the API to get the necessary data.

​
Get Pending Invites

const pendingInvites = await (
  await fetch(
    `https://api.jup.ag/send/v1/pending-invites?address=${pubkey}`,
    {
      headers: {
        'x-api-key': 'your-api-key',
      },
    }
  )
).json();

​
Get Invite History

const inviteHistory = await (
  await fetch(
    `https://api.jup.ag/send/v1/invite-history?address=${pubkey}`,
    {
      headers: {
        'x-api-key': 'your-api-key',
      },
    }
  )
).json();