Create and maintain taxpayer nexus registrations programmatically using the Vertex O Series Configuration API
domain: developer.vertexinc.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an O Series access token from the appropriate oauth/token endpoint for your deployment (Cloud VERX IDP, On-Demand, or On-Premise) using the client_credentials grant with your client ID and secret
Call the registrations creation endpoint to create one or more taxpayer registrations, specifying the owning party and registration type
List existing registrations, filtering by owningPartyId or registrationType using the eq operator
Retrieve a specific registration by ID, and update it in place, noting that a full update replaces all elements of the registration
Delete a registration by ID when it is no longer valid
Known gotchas
Do not include an Authorization Bearer header on requests to the oauth/token endpoint itself; O Series rejects token requests that carry a bearer token
The standard access token endpoint allows only up to 10 token requests per 8 hours by default, so implement local token caching rather than requesting a new token per call
A full update on a registration replaces the entire resource, so partial updates require resending all existing fields, not just the changed ones
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?