curl --request POST \
  --url https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "profiles": [
    "<string>"
  ]
}
'

import requests

url = "https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary"

payload = { "profiles": ["<string>"] }
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: JSON.stringify({profiles: ['<string>']})
};

fetch('https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_POSTFIELDS => json_encode([
    'profiles' => [
        '<string>'
    ]
  ]),
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>",
    "Content-Type: application/json"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary"

	payload := strings.NewReader("{\n  \"profiles\": [\n    \"<string>\"\n  ]\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"profiles\": [\n    \"<string>\"\n  ]\n}")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://vanguard.profilebehavior.com/api/v4/playbook/ai/team-summary")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"profiles\": [\n    \"<string>\"\n  ]\n}"

response = http.request(request)
puts response.read_body

{
  "code": 200,
  "id": "60e9ca73c500a9001534ad84",
  "content": "This team skews high on Influence and Organization, with one very strong Dominance voice and a solid bench of Steadiness and Correctness. Expect energetic dialogue, quick rapport, and a bias to collaborate, balanced by process-minded partners who keep quality high. Communication is split: several are highly talkative and spontaneous, while a few are quiet, analytical contributors who prefer time to think. In DISC terms: the D brings direct, decisive drive (fear: loss of control); many I’s add people-focused energy (fear: being ignored); multiple S’s provide loyalty and patience (fear: instability or change); and the C-leaning members ensure precision and rigor (fear: being wrong or criticized). With Organization scores broadly strong, the group executes well; varied Flexibility and a couple of very low Communication scores mean ideas may concentrate among the loudest unless airtime is structured.\nCore values cluster around Freedom, Integrity, Responsibility/Order, and Advancement/Power—blending autonomy with high standards and ambition. Several also prize Economic Security and Family Happiness, which pulls toward sustainable pacing and predictable plans. This mix creates a culture that wants room to move, but not at the expense of ethics, clarity, or results. Tensions may surface between Freedom and Order (how much autonomy vs. process), and between Power/Competitiveness and Friendship/Helpfulness; naming these trade-offs will keep motivation high without undercutting cohesion.\nUnder pressure, expect the strong D to press for fast decisions, I’s to seek visibility and rally others, S’s to slow the pace for stability, and C’s to ask for data and risk checks. Most members are emotionally steady, though one or two may spike in reactivity; give them clear roles and support. The upside: resilience, disciplined execution, and strong stakeholder management. The caution: decision whiplash—loud voices racing ahead while steady/precise teammates hesitate. In fast change, S-heavy folks may resist, and I’s can oversell; C’s may stall if standards feel fuzzy.\nTo sharpen performance: 1) Define decision rights and “good enough” criteria up front—pair the D’s speed with C/S guardrails. 2) Run meetings with structured airtime (round-robins, timeboxes) and pre-reads to elevate low-Communication, high-accuracy voices. 3) Protect Freedom through clear guardrails: objectives, boundaries, and check-ins—autonomy inside agreed lanes. 4) Balance ambition with trust: celebrate wins (feeds I/Power), track commitments visibly (reassures S/C and Integrity), and use pilots to de-risk change. 5) In tense moments, use a two-step: quick provisional decision, then a short validation pass for risks and impacts—keeps momentum without sacrificing quality.\n",
  "status": "success"
}

{
  "code": 400,
  "error": {
    "message": "Invalid request body",
    "timestamp": "2025-01-01T09:42:52.329056-05:00"
  },
  "status": "error"
}

{
  "code": 401,
  "error": {
    "message": "Invalid token",
    "timestamp": "2025-01-01T09:42:52.329056-05:00"
  },
  "status": "error"
}