Skip to main content

OAuth2 bearer tokens on /services/api

Hello everyone,

We tested the 2026-11-03 release with our automation on the AI - POC release of the L'Oréal tenant, using the OAuth2 client credentials you provided for the Knowledge Platform.

What works

  • OAuth2 authentication: The client credentials (POST https://api.syniti.eu/oauth2/tokens) are now accepted as a bearer token on /v1, /odata and the new /v1/etl-jobs/* endpoints. An API key is no longer required.

  • Build and compiled SQL: Both the Build endpoint (POST /v1/etl-jobs/{id}/rebuild) and the compiled SQL endpoint (GET /v1/etl-jobs/{id}/compiled-sql) return results that match the Service API byte for byte. Thank you for these additions.

Where we stand

Of the 45 Service API (/services/api) endpoints used by our automation:

  • 20 are now fully covered by the public API or an OData view.

  • 5 are partially covered, with one or more required fields missing.

  • 20 have no public equivalent.

The attached document provides a detailed breakdown of each endpoint, its purpose, how we use it and the closest available public API equivalent.

However, the OAuth2 bearer token is still rejected (401) on /services/api. As a result, the 25 endpoints that are not fully covered still require us to rely on the browser session token (concento-authtoken), which expires after 300 seconds and has no dedicated issuing endpoint.

What we need to finalise the integration

Either of the following options would close the remaining gap:

  1. Accept OAuth2 bearer tokens on /services/api. This would be the simplest and fastest solution, requiring no further changes to the existing endpoints or our automation.

  2. Provide public /v1 or odata equivalents for the 25 remaining endpoints. The "What we ask Syniti" table in the attached document groups these into two priority levels:

    • Priority 1 (18 endpoints): Essential to our Build-to-load workflow, which cannot run end-to-end without them.

    • Priority 2 (7 endpoints): Required for the remaining automation capabilities.

We would be happy to walk you through the document or arrange a joint test on AI - POC at your convenience.

public-api-coverage.pdf

359.6 KB• Document

public-api-coverage.md

17 KB

Log in to comment and vote

No comments yet

Be the first to share your thoughts.