Drive Process Desk from your own code

curl -s -X POST https://api.skillsafe.ai/v1/app-api/guest -H "Content-Type: application/json" -d '{"slug":"process-desk"}'

import json, urllib.request
req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api/guest", data=json.dumps({"slug": "process-desk"}).encode(), headers={"Content-Type": "application/json"})
print(json.load(urllib.request.urlopen(req))["data"]["token"])

const r = await fetch("https://api.skillsafe.ai/v1/app-api/guest", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ slug: "process-desk" }) });
const { data } = await r.json(); console.log(data.token);

res, err := http.Post("https://api.skillsafe.ai/v1/app-api/guest", "application/json", strings.NewReader(`{"slug":"process-desk"}`))
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/guest")).header("Content-Type", "application/json")
    .POST(HttpRequest.BodyPublishers.ofString("{\"slug\":\"process-desk\"}")).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/guest")
res = Net::HTTP.post(uri, { slug: "process-desk" }.to_json, "Content-Type" => "application/json")
puts JSON.parse(res.body)["data"]["token"]

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/guest");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_POST => true, CURLOPT_HTTPHEADER => ["Content-Type: application/json"], CURLOPT_POSTFIELDS => '{"slug":"process-desk"}']);
echo json_decode(curl_exec($ch), true)["data"]["token"];

var res = await http.PostAsync("https://api.skillsafe.ai/v1/app-api/guest", new StringContent("{\"slug\":\"process-desk\"}", Encoding.UTF8, "application/json"));
Console.WriteLine(await res.Content.ReadAsStringAsync());

curl -s -X GET https://api.skillsafe.ai/v1/app-api/me \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json"

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("GET", "/me"))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("GET", "/me"));

req, _ := http.NewRequest("GET", "https://api.skillsafe.ai/v1/app-api/me", nil)
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/me"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("GET", HttpRequest.BodyPublishers.noBody()).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/me")
req = Net::HTTP::Get.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/me");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"]]);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Get, "https://api.skillsafe.ai/v1/app-api/me");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -s -X GET https://api.skillsafe.ai/v1/app-api/me \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json"

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("GET", "/me"))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("GET", "/me"));

req, _ := http.NewRequest("GET", "https://api.skillsafe.ai/v1/app-api/me", nil)
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/me"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("GET", HttpRequest.BodyPublishers.noBody()).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/me")
req = Net::HTTP::Get.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/me");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"]]);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Get, "https://api.skillsafe.ai/v1/app-api/me");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -s -X POST https://api.skillsafe.ai/v1/app-api/estimate \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}'

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("POST", "/estimate", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("POST", "/estimate", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}));

req, _ := http.NewRequest("POST", "https://api.skillsafe.ai/v1/app-api/estimate", strings.NewReader(`{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}`))
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/estimate"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("POST", HttpRequest.BodyPublishers.ofString("""
{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}
""")).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/estimate")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
req.body = "{\"task\": \"improve\", \"process_name\": \"Purchase-order approval\", \"description\": \"A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.\", \"steps\": \"step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated\", \"demand_per_week\": \"40\", \"facts\": \"<JSON string from Flow.facts(...) - see the facts section>\"}"
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/estimate");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"],
  CURLOPT_POSTFIELDS => '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}']);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Post, "https://api.skillsafe.ai/v1/app-api/estimate");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
req.Content = new StringContent(@"{""task"": ""improve"", ""process_name"": ""Purchase-order approval"", ""description"": ""A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend."", ""steps"": ""step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated"", ""demand_per_week"": ""40"", ""facts"": ""<JSON string from Flow.facts(...) - see the facts section>""}", Encoding.UTF8, "application/json");
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -s -X POST https://api.skillsafe.ai/v1/app-api/estimate \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor'\''s registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor'\''s email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}'

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("POST", "/estimate", {"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("POST", "/estimate", {"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}));

req, _ := http.NewRequest("POST", "https://api.skillsafe.ai/v1/app-api/estimate", strings.NewReader(`{"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}`))
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/estimate"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("POST", HttpRequest.BodyPublishers.ofString("""
{"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}
""")).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/estimate")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
req.body = "{\"task\": \"document\", \"process_name\": \"New vendor onboarding\", \"description\": \"Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.\", \"steps\": \"step | owner | process time | wait before | %C&A | kind\\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated\", \"demand_per_week\": \"6\", \"facts\": \"<JSON string from Flow.facts(...) - see the facts section>\"}"
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/estimate");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"],
  CURLOPT_POSTFIELDS => '{"task": "document", "process_name": "New vendor onboarding", "description": "Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor\'s registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor\'s email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence.", "steps": "step | owner | process time | wait before | %C&A | kind\\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated", "demand_per_week": "6", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}']);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Post, "https://api.skillsafe.ai/v1/app-api/estimate");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
req.Content = new StringContent(@"{""task"": ""document"", ""process_name"": ""New vendor onboarding"", ""description"": ""Onboarding a new supplier so that we can raise purchase orders against them. Procurement collects the vendor's registration form, tax certificate and bank letter; compliance screens the company and its directors against the sanctions list; legal reviews our standard terms or negotiates exceptions, which is where most of the time goes; the category manager approves the vendor for their spend category; accounts payable creates the vendor record and bank details in the ERP and verifies the bank details by calling a number taken from an independent source, never from the vendor's email; then the ERP notifies procurement. Exceptions: a vendor that fails screening is rejected and procurement told why; a sole trader has no directors to screen; a vendor already in the ERP under another entity is merged rather than created; bank detail changes later follow the same call-back rule. This process is audited annually, and the auditors want to see the call-back evidence."", ""steps"": ""step | owner | process time | wait before | %C&A | kind\nCollect the registration form, tax certificate and bank letter | Procurement | 45m | 0 | 80% | manual\nScreen the vendor and its directors against the sanctions list | Compliance | 20m | 1d | 100% | manual\nReview the standard terms or negotiate exceptions | Legal | 2h | 3d | 95% | manual\nApprove the vendor for the category | Category manager | 15m | 2d | 100% | approval\nCreate the vendor record and bank details in the ERP | Accounts payable | 30m | 1d | 90% | manual\nVerify the bank details by call-back to an independent number | Accounts payable | 15m | 4h | 100% | manual\nNotify procurement that the vendor is active | ERP | 1m | 0 | 100% | automated"", ""demand_per_week"": ""6"", ""facts"": ""<JSON string from Flow.facts(...) - see the facts section>""}", Encoding.UTF8, "application/json");
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -s -X POST https://api.skillsafe.ai/v1/app-api/run \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: po-approval-improve-2026-09-23" \
  -d '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}'

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("POST", "/run", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("POST", "/run", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}));

req, _ := http.NewRequest("POST", "https://api.skillsafe.ai/v1/app-api/run", strings.NewReader(`{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}`))
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/run"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("POST", HttpRequest.BodyPublishers.ofString("""
{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}
""")).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/run")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
req.body = "{\"task\": \"improve\", \"process_name\": \"Purchase-order approval\", \"description\": \"A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.\", \"steps\": \"step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated\", \"demand_per_week\": \"40\", \"facts\": \"<JSON string from Flow.facts(...) - see the facts section>\"}"
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/run");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"],
  CURLOPT_POSTFIELDS => '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}']);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Post, "https://api.skillsafe.ai/v1/app-api/run");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
req.Content = new StringContent(@"{""task"": ""improve"", ""process_name"": ""Purchase-order approval"", ""description"": ""A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend."", ""steps"": ""step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated"", ""demand_per_week"": ""40"", ""facts"": ""<JSON string from Flow.facts(...) - see the facts section>""}", Encoding.UTF8, "application/json");
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -s -X GET https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json"

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("GET", "/jobs/JOB_ID"))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("GET", "/jobs/JOB_ID"));

req, _ := http.NewRequest("GET", "https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID", nil)
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("GET", HttpRequest.BodyPublishers.noBody()).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID")
req = Net::HTTP::Get.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"]]);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Get, "https://api.skillsafe.ai/v1/app-api/jobs/JOB_ID");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());

curl -N -s -X POST https://api.skillsafe.ai/v1/app-api/run-stream \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" -H "Accept: text/event-stream" \
  -H "Content-Type: application/json" -d '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}'
# events: job (the job id), tick (heartbeat), done (the full output). Browsers receive ticks, not deltas.

import json, urllib.request
TOKEN = "YOUR_TOKEN"
def call(method, path, body=None):
    req = urllib.request.Request("https://api.skillsafe.ai/v1/app-api" + path, method=method, data=json.dumps(body).encode() if body is not None else None,
        headers={"Authorization": "Bearer " + TOKEN, "Content-Type": "application/json"})
    with urllib.request.urlopen(req) as r: return json.load(r)
print(call("POST", "/run-stream", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}))

const TOKEN = "YOUR_TOKEN";
async function call(method, path, body) {
  const r = await fetch("https://api.skillsafe.ai/v1/app-api" + path, { method, headers: { Authorization: "Bearer " + TOKEN, "Content-Type": "application/json" }, body: body ? JSON.stringify(body) : undefined });
  return r.json();
}
console.log(await call("POST", "/run-stream", {"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}));

req, _ := http.NewRequest("POST", "https://api.skillsafe.ai/v1/app-api/run-stream", strings.NewReader(`{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}`))
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
io.Copy(os.Stdout, res.Body)

HttpRequest req = HttpRequest.newBuilder(URI.create("https://api.skillsafe.ai/v1/app-api/run-stream"))
    .header("Authorization", "Bearer " + token).header("Content-Type", "application/json")
    .method("POST", HttpRequest.BodyPublishers.ofString("""
{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}
""")).build();
System.out.println(HttpClient.newHttpClient().send(req, HttpResponse.BodyHandlers.ofString()).body());

require "net/http"; require "json"
uri = URI("https://api.skillsafe.ai/v1/app-api/run-stream")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{token}", "Content-Type" => "application/json")
req.body = "{\"task\": \"improve\", \"process_name\": \"Purchase-order approval\", \"description\": \"A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.\", \"steps\": \"step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated\", \"demand_per_week\": \"40\", \"facts\": \"<JSON string from Flow.facts(...) - see the facts section>\"}"
puts Net::HTTP.start(uri.host, 443, use_ssl: true) { |h| h.request(req) }.body

$ch = curl_init("https://api.skillsafe.ai/v1/app-api/run-stream");
curl_setopt_array($ch, [CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => ["Authorization: Bearer $token", "Content-Type: application/json"],
  CURLOPT_POSTFIELDS => '{"task": "improve", "process_name": "Purchase-order approval", "description": "A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend.", "steps": "step | owner | process time | wait before | %C&A | kind\\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\\nApprove the PO | Line manager | 10m | 2d | 100% | approval\\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated", "demand_per_week": "40", "facts": "<JSON string from Flow.facts(...) - see the facts section>"}']);
echo curl_exec($ch);

var req = new HttpRequestMessage(HttpMethod.Post, "https://api.skillsafe.ai/v1/app-api/run-stream");
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
req.Content = new StringContent(@"{""task"": ""improve"", ""process_name"": ""Purchase-order approval"", ""description"": ""A buyer drafts the purchase order in the ERP and emails it to their line manager, who approves by replying to the email. Anything over 5,000 also goes to finance, who check the budget line in a shared spreadsheet, and spend over 25,000 needs the finance director. Once approved the buyer re-keys the PO number into the vendor portal by hand because the portal is not connected to the ERP, and the ERP then sends the PO. Orders get stuck for days when the manager travels, roughly one in ten come back from finance because the cost centre is wrong, and the portal re-keying produces typos that vendors query. We want the routine orders to go out the same day without losing the controls on big spend."", ""steps"": ""step | owner | process time | wait before | %C&A | kind\nDraft the purchase order in the ERP | Buyer | 30m | 0 | 90% | manual\nEmail the PO to the line manager | Buyer | 5m | 0 | 100% | manual\nApprove the PO | Line manager | 10m | 2d | 100% | approval\nCheck the budget line in the spreadsheet | Finance | 20m | 1d | 95% | manual\nApprove spend over the threshold | Finance director | 10m | 3d | 100% | approval\nRe-key the PO number into the vendor portal | Buyer | 15m | 4h | 85% | manual\nSend the PO to the vendor | ERP | 1m | 0 | 100% | automated"", ""demand_per_week"": ""40"", ""facts"": ""<JSON string from Flow.facts(...) - see the facts section>""}", Encoding.UTF8, "application/json");
Console.WriteLine(await (await http.SendAsync(req)).Content.ReadAsStringAsync());