v1
latestOpenAPI 3.1.02026-07-13143194365.4 KBtipping
Send a tip via JSON body (recommended for bots/integrations)
Send a tip using a JSON request body. Recommended for programmatic access, bots, and integrations that need to track social graph context.
Social Graph Context
The optional context field allows you to attach attribution metadata to tips:
| Field | Description | Example |
|---|---|---|
| source_post_url | URL where the tip was triggered | https://x.com/user/status/123 |
| sender_username | Tipper's username | olshansky |
| sender_profile_url | Tipper's profile URL | https://x.com/olshansky |
| sender_platform | Platform enum | x, discord, telegram, etc. |
| recipient_username | Recipient's username | vitalik |
| campaign | Campaign/bot identifier | grove-twitter-bot-v1 |
| referrer | Referrer identifier | twitter-bot |
| custom_metadata | Free-form string (max 250 chars) | {"note": "great work!"} |
Supported Platforms
x, reddit, github, tiktok, substack, youtube, discord, telegram, farcaster, lens, other
Metadata Storage
Context is stored in the tip's metadata_json under a nested context key with ctx_ prefixed fields, preserving separation from auto-resolved metadata (like x_username from destination resolution).
post/v1/tip
Headers
authorizationstring nullable
Bearer JWT that identifies the sending account.
- Required for all tipping calls
- Format: Bearer <jwt_token>
- Obtain JWT from /v1/fund after funding your account
Bearer JWT that identifies the sending account.
- Required for all tipping calls
- Format: Bearer <jwt_token>
- Obtain JWT from /v1/fund after funding your account
Request body
Example request
{
"description": "Tip 1 USDC to a domain with llms.txt",
"summary": "Simple tip to a domain",
"value": {
"amount": "1",
"destination": "olshansky.info"
}
}Response
Successful Response