Skip to main content

Authentication

The GS1 EPCIS 2.0 API currently supports the static token authentication mechanism.

Access Tokens​

Static Tokens can be set for each platform user, and never expire. Static Tokens are created in user settings inside of the TrackVision UI User Module, or by updating the user's token value via API.

Access tokens are passed in using the request's Authorization Header

Learn more here: native REST API Authentication Guide

Authorization Header​

Authorization: Bearer <token>

EPCIS-Specific Authentication​

Capture Endpoint Authentication​

The capture endpoint requires write permissions to submit events:

POST https://epcis.yourdomain.trackvision.ai/v2/epcis/capture
Authorization: Bearer your-token
Content-Type: application/json

{
  // EPCIS Document
}

Query Endpoint Authentication​

Query endpoints require read permissions based on data access policies:

GET https://epcis.yourdomain.trackvision.ai/v2/epcis/events?bizStep=shipping
Authorization: Bearer your-token

Subscription Authentication​

Creating and managing subscriptions requires specific permissions:

POST https://epcis.customer.trackvision.ai/v2/epcis/subscriptions
Authorization: Bearer your-token
Content-Type: application/json

{
  // Subscription configuration
}