mwUid) across all industries, at any point in time, using JSON. This guide walks a new API client through the full flow: authenticate, look up rates by location, and look up rates by mwUid.
Prefer a UI over building your own integration? See the Quickstart: Look up rates in Portal instead. For a comparison of the two, see Portal vs. API.
Before you begin
You’ll need an API key to follow this guide. If you don’t have one, contact your Symmetry Client Success representative or reach out through the Client Support Center. See Prerequisites for the account setup your administrator needs to complete, and the entitlement that controls whether rates are returned at all. To try the endpoints before writing any code, download the Postman collection and environment, or explore them interactively in the MWF API overview.Environments
Always develop and test against the staging environment before pointing your integration at production.
Step 1: Authenticate
Every MWF API endpoint other than/authentication/login itself requires a JWT access token. Request one by calling the authentication endpoint with your API key.
accessToken:
Authorization header on every other request in this guide. Tokens are valid for 24 hours. See the MWF API overview for error responses and the difference between your API key and your access token.
Step 2: Look up minimum wage rates by location
With your access token, call/mwf/v1/location with a work address (or a latitude/longitude pair) and an effective date. The response contains every minimum wage rate applicable to that location for that date.
Step 3: Look up minimum wage rates by mwUid (optional)
Each rate returned in Step 2 includes an mwUid, a unique identifier for that specific rate. Use /mwf/v1/id to look up a rate directly by its mwUid, including its full effective-date history.
*) can be used in place of any mwUid element to broaden the search. For example, mwUid=04-*-*-*-*-* returns every rate for Arizona regardless of authority, wage type, industry, or attribute. See Minimum wage unique IDs for what each element in the ID represents.
Next steps
API reference
Every endpoint with its parameters and schema, generated from the OpenAPI spec.
Retrieve recent rate updates
Poll for rates that changed, instead of re-running every location.

