Skip to main content
Livestock Developer Hub

Tagging API authentication

Overview

Access to the Tagging service application is controlled by Azure B2C authentication. Client applications use client credentials to request an access token before calling secure Tagging API endpoints.

To consume the Tagging API, register an application and subscribe under the My Apps & Data area, then copy the credentials shown for your application and subscription.

  • Register an application and subscribe to the Tagging service.
  • Use the provided client ID, client secret, scope, and subscription key.
  • Request an access token using the client credentials flow.
  • Call Tagging API endpoints with the access token and subscription key.

Client application

Ear tag manufacturer applications are confidential clients, such as server-side web applications, web APIs, or background services. These applications can keep configuration and secrets secure.

Each manufacturer is provided with distinct configuration including a client ID and client secret. These values are used only to obtain access tokens.

Client credential flow diagram

Authentication process flow

  • The client application requests an access token from the authentication service.
  • The authentication service returns an access token.
  • The client application calls the Tagging API with the access token and subscription key.
  • The service validates both values before granting access.
Authentication process flow diagram

The token request includes the client ID, client secret, and scope supplied for the registered application.

Token request fields

Implementation details vary by programming language and framework. Microsoft documentation provides reference material and examples for OAuth 2.0, OpenID Connect, and Azure B2C flows.