ADME Technical Reference

Factual reference for Equinor's Azure Data Manager for Energy (ADME) deployment.

Instances

Environment	Instance	Data Partition	Base URL
Dev	equinorswedev	`dev`	`https://equinorswedev.energy.azure.com`
Test	equinorswetest	`test`	`https://equinorswetest.energy.azure.com`
Prod	equinorswe	`data`	`https://equinorswe.energy.azure.com`

Each instance is a complete, independent OSDU deployment with its own data, entitlements, and services. See Configuration Files for ready-made configs per environment.

Service endpoints

All instances expose the same services. Replace {instance} with the base URL above.

Core ServicesDDMSSupporting Services

Search


Path	`/api/search/v2/*`
Health	`{instance}/api/search/v2/actuator/health`
Swagger	`{instance}/api/search/v2/swagger-ui.html`

Storage


Path	`/api/storage/v2/*`
Health	`{instance}/api/storage/v2/health`
Swagger	`{instance}/api/storage/v2/swagger-ui.html`

Schema


Path	`/api/schema-service/v1/*`
Health	`{instance}/api/schema-service/v1/`
Swagger	`{instance}/api/schema-service/v1/swagger-ui.html`

Indexer


Path	`/api/indexer/v2/*`
Health	`{instance}/api/indexer/v2/actuator/health`
Swagger	`{instance}/api/indexer/v2/swagger-ui.html`

File


Path	`/api/file/v2/*`
Health	`{instance}/api/file/v2/`
Swagger	`{instance}/api/file/v2/swagger-ui.html`

Entitlements


Path	`/api/entitlements/v2/*`
Health	`{instance}/api/entitlements/v2/actuator/health`
Swagger	`{instance}/api/entitlements/v2/swagger-ui.html`

Legal


Path	`/api/legal/v1/*`
Health	`{instance}/api/legal/v1/actuator/health`
Swagger	`{instance}/api/legal/v1/swagger-ui.html`

Wellbore DDMS


Path	`/api/os-wellbore-ddms/ddms/v2/*`
Health	`{instance}/api/os-wellbore-ddms/ddms/v2/status`
Swagger	`{instance}/api/os-wellbore-ddms/docs`

Seismic DDMS


Path	`/seistore-svc/api/v3/*`
Swagger	`{instance}/seistore-svc/api/v3/swagger-ui.html`

Workflow


Path	`/api/workflow/v1/*`
Health	`{instance}/api/workflow/v1/`
Swagger	`{instance}/api/workflow/v1/swagger-ui.html`

Notification


Path	`/api/notification/v1/*`
Health	`{instance}/api/notification/v1/actuator/health`
Swagger	`{instance}/api/notification/v1/swagger-ui.html`

Register


Path	`/api/register/v1/*`
Health	`{instance}/api/register/v1/actuator/health`
Swagger	`{instance}/api/register/v1/swagger-ui.html`

Partition


Path	`/api/partition/v1/*`
Health	`{instance}/api/partition/v1/actuator/health`
Swagger	`{instance}/api/partition/v1/swagger-ui.html`

CRS Catalog


Path	`/api/crs/catalog/*`
Health	`{instance}/api/crs/catalog/v2/actuator/health`
Swagger	`{instance}/api/crs/catalog/swagger-ui.html`

CRS Converter


Path	`/api/crs/converter/*`
Health	`{instance}/api/crs/converter/v2/actuator/health`
Swagger	`{instance}/api/crs/converter/swagger-ui.html`

Unit


Path	`/api/unit/*`
Health	`{instance}/api/unit/v2/`
Swagger	`{instance}/api/unit/swagger-ui.html`

APIs

OSDU provides many service APIs. The following are available on the Equinor ADME instance:

Service	Description
CRS Catalog	Coordinate reference system catalog
CRS Conversion	Coordinate reference system conversion
Dataset	Dataset management
Entitlements	Access control and permissions
File	File upload and download
Indexer	Search indexing
Legal	Legal tag management
Notification	Event notifications
Register	Service registration
Schema	Schema management
Search	Data search
Storage	Record storage
Unit	Unit of measure management
Workflow	Workflow orchestration
Wellbore DDMS	Wellbore domain data management
Seismic DDMS	Seismic domain data management
Reservoir DDMS	Reservoir domain data management
Rock and Fluid Sample DDMS	Rock and fluid sample domain data management

Testing the APIs

Swagger definitions are available for each service. You can explore and test all API calls at Microsoft ADME Samples.

You can also use our Postman collection to test the APIs directly.

Authentication

All access to ADME goes through Microsoft Entra ID using OAuth2.

Your client app requests an access token from Entra ID
Entra ID returns the token
Your app sends the API request to ADME with the token attached

Without a valid token, the request is rejected at the security barrier. For a conceptual overview of how authentication works, see ADME — Authentication.

OSDU vs ADME

	OSDU	ADME
What	Open standard and API specification	Microsoft's hosted implementation
Who runs it	Defined by The Open Group	Operated by Microsoft on Azure
APIs	Standard OSDU APIs	Same APIs, hosted on Azure endpoints
Identity	Supports multiple identity providers	Uses Microsoft Entra (AAD)

To understand the relationship between OSDU and ADME, see ADME — How ADME relates to OSDU.