Retrieve premium invoice and payment data via the Guidewire BillingCenter Cloud API.
domain: docs.guidewire.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Authenticate against the Guidewire Identity Federation Hub using an appropriate OAuth2 flow (authorization code for user-context calls, client-credentials for service-to-service calls).
Call the account resource endpoint to locate the billing account for the policy or customer in question.
Retrieve the account's invoices, using filter/sort/pagination query parameters to scope the results.
Retrieve invoice items or invoice streams for a specific invoice to get line-level charge detail.
Create a direct bill payment (or agency bill statement payment) via a POST to the relevant payment resource, including the required checksum for the resource being modified.
Confirm the BillingCenter Cloud API documentation version matches your target BillingCenter release, since endpoint availability differs by release train.
Known gotchas
The Cloud API is documented using the Swagger 2.0 specification rather than OpenAPI 3, which affects client-generation tooling choices.
Mutating calls (PATCH, business-action POST, DELETE) require a checksum from the current resource state to prevent lost updates — fetch the latest resource state first.
Endpoint availability is versioned per BillingCenter release (e.g., specific dated doc sets); mismatched documentation versus your instance's actual version can produce confusing errors.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?