- Index - API Documentation
- Parameters - API Parameter Details
- Profiles - Manage user profiles
- Resources - Manage resources
- Rules - Manage the ACRs for resources
- EML - Manage EML documents and associated ACRs
- Groups - Manage groups and group members
- Search - Search for profiles and groups
- Tokens and API keys - Manage tokens and API keys
This document describes the API for managing permissions via EML documents.
POST /auth/v1/eml
Parse a valid EML document, create a corresponding data package resource tree, and add its ACRs to the ACR registry. The token profile becomes the owner (changePermission) of all associated resources.
The key_prefix sets the prefix for the resource keys for the package root resource and the Metadata branch of the resource tree (e.g., https://pasta.lternet.edu — no trailing slash). For entities in the Data branch, the full resource key is read from the /physical/distribution/online/url element of each entity.
Required permission: Caller must be in the Vetted system group.
| Parameter | In | Required | Description |
|---|---|---|---|
edi-token |
Cookie | Yes | See Parameters |
eml |
JSON body | Yes | A valid EML XML document |
key_prefix |
JSON body | Yes | Prefix for the package root and Metadata resource keys (e.g., https://pasta.lternet.edu) |
| Status | Description |
|---|---|
200 OK |
EML parsed and resources/ACRs created successfully |
400 Bad Request |
EML is invalid, or related resources already exist |
401 Unauthorized |
See Parameters |
403 Forbidden |
Caller is not in the Vetted group |