{
 "categories": [
  "finance",
  "invoicing"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-10",
   "fact": "homepage",
   "note": "The homepage states that Pagero has transitioned to the Thomson Reuters brand and markets ONESOURCE Pagero for e-invoicing compliance, Peppol access, and AP and AR automation.",
   "source": "https://www.pagero.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "vendor",
   "note": "The opened site identifies Thomson Reuters as the current vendor and shows a Gothenburg Pagero address in the footer.",
   "source": "https://www.pagero.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "name",
   "note": "Thomson Reuters markets the product as ONESOURCE Pagero E-invoicing and related AP/AR automation on the Pagero Network.",
   "source": "https://www.pagero.com/solutions/e-invoicing",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "deployment",
   "note": "ONESOURCE Pagero is presented as a hosted compliance and e-document network that integrates with customer ERP systems rather than a desktop install.",
   "source": "https://www.pagero.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "license",
   "note": "The site offers demo and contact-sales paths. No public free-tier API product is published on the opened pages.",
   "source": "https://www.pagero.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.exists",
   "note": "Pagero's connectivity toolkit documents REST APIs that allow applications to integrate with Pagero Online.",
   "source": "https://pagero.github.io/partners/apis/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.kinds[0]",
   "note": "The Pagero Web API uses HTTPS GET, POST, PUT, and DELETE with JSON resource representations at https://api.{region}.pageroonline.com/{sub-API}/{version}/.",
   "source": "https://pagero.github.io/partners/apis/api-guidelines/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.auth[0]",
   "note": "Authorization-code grant with PKCE uses https://sso.pageroonline.com/oauth/v2/oauth-authorize and exchanges the code at /oauth-token. API calls send Authorization: Bearer plus the JWT.",
   "source": "https://pagero.github.io/partners/apis/api-authentication-authorization/authorization-code-grant-pkce/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.auth[1]",
   "note": "The resource-owner password grant POSTs grant_type=password plus username, password, and client credentials to https://sso.pageroonline.com/oauth/v2/oauth-token for machine access without a browser login.",
   "source": "https://pagero.github.io/partners/apis/api-authentication-authorization/resource-owner-password-credentials-grant/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.coverage",
   "note": "Public sub-APIs include Analytics, Clearance, Code List, Company, Document, File, Network, Signup, Tax Reporting, User, and Download Exports. The REST intro currently recommends the APIs for partners, not direct customers.",
   "source": "https://pagero.github.io/partners/apis/api-reference/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.docs",
   "note": "This page is Pagero's current REST API introduction and the entry point to guidelines, authentication, and the API reference.",
   "source": "https://pagero.github.io/partners/apis/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.data_access.export[0]",
   "note": "Collection and instance resources are returned as application/json, including paginated items arrays.",
   "source": "https://pagero.github.io/partners/apis/api-guidelines/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.data_access.import[0]",
   "note": "POST and PUT accept JSON resource representations. Some resources also accept other media types such as application/pdf.",
   "source": "https://pagero.github.io/partners/apis/api-guidelines/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened https://www.pagero.com/llms.txt; the URL returned 404. That is not a first-party agent documentation index.",
   "source": "https://www.pagero.com/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-10",
   "fact": "verdict.scores.api",
   "note": "REST coverage across documents, files, network, and related sub-APIs is documented with OAuth 2.0. Client credentials are issued by Pagero and the toolkit currently steers the APIs toward partners, which is a material access gate.",
   "source": "https://pagero.github.io/partners/apis/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Thomson Reuters / Pagero homepage, including the brand-transition announcement and Peppol / e-invoicing positioning.",
   "source": "https://www.pagero.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current REST API introduction, including the partner-not-direct-customer recommendation.",
   "source": "https://pagero.github.io/partners/apis/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current OAuth 2.0 authentication index for authorization-code and resource-owner password flows.",
   "source": "https://pagero.github.io/partners/apis/api-authentication-authorization/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current public sub-API catalog, including Document, File, Network, and related SwaggerHub and GitHub docs.",
   "source": "https://pagero.github.io/partners/apis/api-reference/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-10",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://www.pagero.com/"
   },
   {
    "type": "docs",
    "url": "https://pagero.github.io/partners/apis/"
   },
   {
    "type": "docs",
    "url": "https://pagero.github.io/partners/apis/api-authentication-authorization/"
   },
   {
    "type": "docs",
    "url": "https://pagero.github.io/partners/apis/api-reference/"
   }
  ]
 },
 "homepage": "https://www.pagero.com/",
 "id": "pagero",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "authorization-code",
    "resource-owner-password"
   ],
   "coverage": "partial",
   "docs": "https://pagero.github.io/partners/apis/",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": [
    "json"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. The documented Pagero Online REST APIs are the supported machine path. Browser automation of the Thomson Reuters / Pagero portal remains unassessed.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "ONESOURCE Pagero",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "basware",
   "coupa",
   "visma-proceedo"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Thomson Reuters",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 6,
   "rpa": null
  },
  "summary": "Thomson Reuters ONESOURCE Pagero is automatable through documented REST APIs on the Pagero Online platform. This record is Pagero e-invoicing and business-network connectivity, not Basware, Coupa, or Visma Proceedo. The public homepage states that Pagero has moved to the Thomson Reuters brand and markets e-invoicing compliance in 80+ countries, Peppol access, and AP and AR automation. REST APIs exchange JSON for analytics, clearance, companies, documents, files, network trading partners, signup, tax reporting, and users. The base URL is https://api.{region}.pageroonline.com/{sub-API}/{version}/. Authentication is OAuth 2.0 against https://sso.pageroonline.com. Interactive clients use authorization code, including PKCE. Trusted machine clients may use the resource-owner password grant. Callers send the resulting JWT as a Bearer token to api.pageroonline.com. Client credentials are issued by Pagero. The connectivity toolkit currently recommends the REST APIs for partners rather than direct customers because of the integration investment. First-party MCP ownership is not established. iPaaS catalogs were not opened. Computer-use viability is unassessed. API scores 6 and is the best path because the contract is documented and read/write, but access is credential-gated and partner-oriented.\n"
 }
}