🔐 ENSPACE API authentication

The API uses token-based authentication through the x-api-key header. This guide details the entire authentication process.

Authentication Flow

📋 Mandatory Headers

⚠️ Important: Every request to the ENSPACE API requires the authentication header:

Workspace Header

The en-workspace header is required only on endpoints that operate in the context of a specific workspace:

When is the en-workspace header required?

Endpoints that manipulate specific data from a workspace (types, items, members, etc.)

Endpoints that check member permissions

Endpoints that access workspace settings

When is it NOT necessary?

Authentication and token generation endpoints

Available workspace listing endpoints

User profile endpoints

💡 Tip: Each endpoint in the documentation clearly indicates whether the en-workspace header is required or not.

🔑 Generating your API Token

Prerequisites

✅ Active account on ENSPACE

✅ Access to at least one workspace

✅ Permissions to generate tokens (check with administrator)

Step by Step

1️⃣ Access ENSPACE

Go to https://be.enspace.io (or your dedicated domain)

You will be directed to the workspace list

2️⃣ Access User Settings

In the top right corner, click on the user menu (your avatar/photo)

Select "User Settings"

3️⃣ Navigate to the Dev Tab

In the settings, click on the "Dev" tab

Scroll to the "API Tokens" section

4️⃣ Create New Token

Click "Create your first token" (or "New token")

Fill in the fields:

Field	Description	Example
Description	Identifier name	"ERP Integration", "Mobile App"
Expiration	Expiry date	`1M`, `6M`, `1y`, `never`
Scopes	Token Permissions	☑️ read ☑️ write ☐ delete
Workspaces	Authorized workspaces	☑️ Workspace A ☑️ Workspace B

Click "Generate Token"

5️⃣ Save the Token

⚠️ ATTENTION: The token will be displayed ONLY ONCE!

en.ushcHQHcREdPpe3ZKFCSfAASFE5VawTwTH (example)

Safety recommendations:

🔒 Save to a password manager

🔒 Use environment variables

❌ NEVER commit to code

❌ NEVER share publicly

🚀 Using the Token

Configuration by Environment

.env

# For Global API
ENSPACE_API_KEY=en.ushcHQHcREdPpe3ZKFCSfAASFE5VawTwTH
ENSPACE_API_URL=https://api.leif.enspace.io
ENSPACE_WORKSPACE_ID=ws-123

# For Dedicated API (example)
# ENSPACE_API_URL=https://acme.api.enspace.io

Usage Examples

JavaScript

cURL

Python

🔄 Multi-Workspace Tokens

A single token can access multiple workspaces. Specify which one to use in each request:

❌ Common Problems

Missing Workspace Header

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Missing required header: en-workspace"
}

Solution: Always include en-workspace in all requests.

Invalid Token

{
  "statusCode": 401,
  "error": "Unauthorized",
  "message": "Invalid or missing API key"
}

Solutions:

Check if the token is correct

Confirm that it has not expired

Generate a new token if necessary

Unauthorized Workspace

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Token not authorized for this workspace"
}

Solution: Generate a new token including the required workspace.

🔒 Good Practices

✅ DO

Use specific tokens per environment

Configure suitable expiration

Monitor token usage

Store in a safe place

❌ DON’T

Expose tokens in code

Use 'wildcard' tokens with full access

Ignore expiration

Share tokens

📞 Support

Need help?

📧 Email: support@be-enlighten.com

💬 Chat: Available on the dashboard

📚 Docs: https://docs.stage.enspace.io/api/auth

When contacting support, please provide:

First 10 characters of the token

Reference of the workspace used

Request timestamp with error

Full error code

Authentication

🔐 ENSPACE API authentication#

Authentication Flow#

📋 Mandatory Headers#

Workspace Header#

🔑 Generating your API Token#

Prerequisites#

Step by Step#

1️⃣ Access ENSPACE#

2️⃣ Access User Settings#

3️⃣ Navigate to the Dev Tab#

4️⃣ Create New Token#

5️⃣ Save the Token#

🚀 Using the Token#

Configuration by Environment#

.env#

Usage Examples#

JavaScript#

cURL#

Python#

🔄 Multi-Workspace Tokens#

❌ Common Problems#

Missing Workspace Header#

Invalid Token#

Unauthorized Workspace#

🔒 Good Practices#

✅ DO#

❌ DON’T#

📞 Support#