API documentation

AI agents and LLMs

Agents can discover and call sponsor.ink programmatically. Use the OpenAPI spec or llms.txt for machine-readable entry points; authenticate with the same Bearer token as the REST API.

• openapi.json — full endpoint schemas (public, no auth)
• llms.txt — summary for AI crawlers and agent runtimes
• Postman collection — interactive REST docs
• Smithery MCP listing — install via Smithery gateway

Typical agent workflow (advertiser)

1. GET /marketplace — filter by DR, price, language, country
2. GET /marketplace/{site} — review publisher rules and pricing
3. GET /wallet — confirm balance before ordering
4. POST /sites/{site}/orders — place the guest post order
5. GET /orders/{order} — track until delivered

Wallet top-ups use Stripe Checkout on the web dashboard only. If balance is too low, direct the user to Wallet before retrying.

Example prompts

• “Search sponsor.ink for English marketing blogs DR 40+ under $200.”
• “Place a written guest post on the best match for https://example.com/pricing with anchor ‘workflow automation’.”
• “List my pending orders and wallet balance on sponsor.ink.”

MCP server

Connect Cursor, Claude Desktop, or any MCP client to call sponsor.ink tools with your API token. Also listed on Smithery.

{
  "mcpServers": {
    "sponsor-ink": {
      "url": "https://sponsor.ink/mcp",
      "headers": {
        "Authorization": "Bearer si_YOUR_TOKEN"
      }
    }
  }
}

Available tools depend on your role and token abilities. Advertisers get marketplace search and ordering; publishers get site management and order fulfilment.

place_order requires confirmed: true after the user approves a price preview. Call without confirmation first to get the preview, or use get_wallet and get_marketplace_site before confirming.

Calling the API directly

curl -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json" \
  "https://sponsor.ink/api/v1/marketplace?min_dr=40&max_price=200&language=en"

Authentication

Base URL: https://sponsor.ink/api/v1

After your access is approved, open Profile and create an API token. The full token is shown once. Store it like a password. Tokens use a si_ prefix and expire after 365 days unless you revoke them sooner.

Send the token on every request:

Authorization: Bearer YOUR_TOKEN
Accept: application/json

Example:

curl -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json" \
  https://sponsor.ink/api/v1/me

Web session cookies alone are not enough. The API requires a personal access token. Each token carries abilities for your role; uncheck ones you do not want that token to have.

Rate limits

• 60 requests per minute per user for reads and general calls.
• 20 requests per minute for writes (create order, transitions, messages, site mutations).

Over the limit you get 429. Back off and retry.

Account

{
  "data": {
    "id": 3,
    "name": "Jane Advertiser",
    "email": "[email protected]",
    "role": "advertiser",
    "balance": "0.00",
    "email_verified_at": null,
    "created_at": "2026-08-25T09:14:32+00:00"
  }
}

Advertiser

Browse the catalog, place orders, cancel while pending, complete or request revision after delivery, message on the order, and read your wallet.

Marketplace

Active listings only.

Orders

{
  "type": "provided",
  "target_url": "https://example.com/landing",
  "anchor_text": "optional anchor",
  "brief": "Tone and angle",
  "content": "Full article when type is provided"
}

From there use the shared order endpoints below. As advertiser you can move pending → cancelled, and delivered → completed or revision.

Advertiser quick path

1. GET /marketplace → pick a site
2. POST /sites/{site}/orders → place the order ({site} is the listing public id)
3. Wait for delivery, then POST .../transition with completed (or revision)

Publisher

List and edit your sites, handle incoming orders (accept, reject, deliver), message on the order, and read earnings.

Sites

New listings start as draft. They go live after review on the platform. You cannot set status or another user’s publisher_id through the API.

{
  "url": "https://mysite.example/",
  "name": "My Site",
  "description": "Optional",
  "language": "en",
  "country": "GB",
  "categories": ["seo", "marketing"],
  "ahrefs_dr": 40,
  "ahrefs_rd": 1200,
  "traffic_monthly": 25000,
  "price_content_provided": 120,
  "price_content_written": 180,
  "turnaround_days": 5,
  "link_type": "dofollow",
  "max_links": 1,
  "publisher_rules": "No gambling. No adult."
}

Orders

Use the shared order endpoints. As publisher you can move pending → accepted or rejected, then accepted → in_progress, then in_progress / revision → delivered (with live_url).

Publisher quick path

1. POST /sites → list a draft site
2. GET /orders → incoming work
3. Accept → in progress → deliver with live_url

Order endpoints (both roles)

Advertisers see orders they placed. Publishers see orders on their sites.

{
  "to_status": "delivered",
  "live_url": "https://publisher-site.com/guest-post",
  "note": "optional note on the timeline"
}

Status transitions

Wallet

Errors

Stuck on an order or listing? Contact us. Process detail without the API: How it works.