Authentication release notes

 

October 31, 2026

Documentation

(4)

• Fixed the Content-Type for token requests in the OAuth reference and the grant type guides. It's now application/x-www-form-urlencoded.
• Updated Token exchange grant type (OAuth) to send the token request with an Authorization: Basic header.
• Clarified in the OAuth reference which parameters each grant type uses. The 3-legged code exchange doesn't use scope, and token exchange needs openid only in some cases.
• Updated the Log in with Indeed example to request only the email scope.

June 30, 2026

Security change

(1)

• Documented the new iss parameter, the authorization server's issuer ID returned in OAuth responses, and refreshed the redirect-URL examples in the OAuth reference.

June 15, 2026

Documentation

(1)

• Updated the Partner Console and OAuth credential guidance to separate steps for partners in Japan and outside Japan, clarifying how to get client_id and client_secret in each market.

May 15, 2026

Documentation

(1)

• Clarified the 3-legged OAuth employer parameter requirement across the OAuth reference, Client credentials grant type (2-legged OAuth), Authorization code grant type (3-legged OAuth), OAuth glossary, Token exchange grant type (OAuth), and Get started topics. Tokens that represent an advertiser must include employer for Employer Registration and Job Sync node queries.

March 31, 2026

Documentation

(1)

• Corrected the parameters in the two-legged OAuth curl example for employer access tokens in Client credentials grant type (2-legged OAuth).

February 28, 2026

Documentation

(1)

• Guidelines updated on redirect URI configuration for 3-legged OAuth. Partners can avoid common OAuth errors by ensuring redirect URIs match the registered value exactly.

August 15, 2025

Documentation

(2)

• Improved the Authorization code grant type (3-legged OAuth) documentation for partner developers. Clarified how to get an authorization code by building the request URL and redirecting users to the OAuth consent screen, replaced an incorrect POST example with the correct redirect flow, and clarified how to capture the authorization code from redirect_uri.
• Added clearer explanations and example URLs for requesting email, offline_access, and employer_access permissions in the 3-legged OAuth documentation. Standardized the language for POST requests to the token endpoint, and improved example request and response descriptions and formatting.

August 4, 2025

Documentation

(1)

• Improved the Japanese 2-legged OAuth documentation for getting access tokens and employer-specific tokens. Clarified steps and terminology, revised the request header and body parameter tables and examples, and added guidance for employer selection screens.

April 30, 2025

Documentation

(2)

• Aligned the Japanese Authorization sidebar with the English.
• Fixed broken links in Client credentials flow (2-legged OAuth).

 

Was this page helpful?