Projekte-API

In Rankion ist ein Projekt der zentrale Container — pro Projekt eine Domain, ein Team-Owner, und alle Sub-Resourcen (Artikel, Keywords, Internal-Link-Maps, Storylines) hängen daran. Daneben gibt es Tracking-Projekte als eigene Ressource für AI-Visibility-Monitoring (siehe unten).

CRUD

# Liste
curl -H "Authorization: Bearer $TOKEN" "$BASE/projects"

# Anlegen
curl -X POST "$BASE/projects" \
     -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"name":"Mein Blog","domain":"meinblog.de","language":"de","country":"DE"}'

Response (gekürzt):

{
  "data": {
    "id": 12,
    "name": "Mein Blog",
    "domain": "meinblog.de",
    "language": "de",
    "country": "DE",
    "team_id": 7,
    "created_at": "2026-05-01T08:30:00Z"
  }
}

Projekt-bezogene Subressourcen

Articles

Alle artikel-bezogenen CRUD- und Generierungs-Endpoints hängen am Projekt:

Volle Artikel-API → Artikel-API.

Keywords

Internal Linking

Weitere Projekt-Subressourcen

Tracking-Projekte (eigene Ressource!)

Tracking-Projekte sind getrennt von normalen Projekten. Sie sind die Datenbasis für AI-Visibility Tracking — pro Tracking-Projekt eine Brand, ein Set Keywords, ein Set Plattformen.

Endpoint-Namespace: /v1/tracking-projects/...

Wizard-Flow

Das Web-UI hat einen 5-Schritt-Wizard, den du 1:1 über die API nachstellen kannst:

# Step 1+2: Analyse starten
RESP=$(curl -s -X POST "$BASE/tracking-projects/analyze" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"mode":"domain","domain":"example.com","language":"de","country":"DE"}')
PID=$(echo $RESP | jq -r .project_id)

# Step 3+4: Pollen bis completed
while [ "$(curl -s "$BASE/tracking-projects/$PID/analysis-status" \
  -H "Authorization: Bearer $TOKEN" | jq -r .analysis_status)" != "completed" ]; do
  sleep 3
done

# Step 5: Atomic-Activate
curl -X POST "$BASE/tracking-projects/$PID/activate" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{
    "keywords":["best crm","crm software"],
    "competitors":[{"domain":"hubspot.com"}],
    "prompts":[{"prompt":"What is the best CRM?","category":"recommendation"}],
    "platforms":["chatgpt","perplexity"],
    "frequency":"weekly",
    "with_search":true,
    "reality_check_enabled":true
  }'

Laufende Operations

Komplette Tabelle aller ~30 Tracking-Endpoints in docs/API_REFERENCE.md.

Beispiel-Workflow: Projekt + erster Artikel

# 1) Projekt anlegen
PID=$(curl -s -X POST "$BASE/projects" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"name":"Demo Site","domain":"demo.example","language":"de","country":"DE"}' \
  | jq -r .data.id)

# 2) Artikel-Stub anlegen
ART=$(curl -s -X POST "$BASE/projects/$PID/articles" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"title":"Beste AI-Tools 2026","status":"draft"}' \
  | jq -r .data.id)

# 3) Artikel-Inhalt generieren (5 Credits, async)
curl -X POST "$BASE/articles/$ART/generate" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"keyword":"AI Tools 2026","article_type":"blog","target_length":1500}'

# 4) Pollen bis fertig
while [ "$(curl -s "$BASE/articles/$ART" \
  -H "Authorization: Bearer $TOKEN" | jq -r .data.processing_status)" != "ready" ]; do
  sleep 5
done

Detail-Workflows für Artikel: Artikel-API.

Verwandt: Authentifizierung & API-Tokens · Credits & Rate-Limits · AI-Visibility Tracking.