API Reference

The NextSDS API gives you programmatic access to your team's SDS data, chemical inventory, storage locations, and safety card generation. Use it to build integrations with warehouse management systems, ERP platforms, barcode scanners, or custom dashboards.

Base URL

https://api.nextsds.com/v1

Authentication

Every request must include an API key in the X-API-Key header.

curl https://api.nextsds.com/v1/sds \
  -H "X-API-Key: your-api-key"

You can create and manage API keys in Settings > API Keys. Each key is scoped to your team and inherits the team's data access. There are two key types:

Team context

All data in NextSDS is scoped to a team. The API key determines which team's data you access — no additional team header is needed.

If your account belongs to multiple teams and you need to target a specific one, include the X-Team-Id header:

curl https://api.nextsds.com/v1/sds \
  -H "X-API-Key: your-api-key" \
  -H "X-Team-Id: 550e8400-e29b-41d4-a716-446655440000"

Request format

• Send JSON request bodies with Content-Type: application/json
• File uploads use Content-Type: multipart/form-data
• All IDs are UUIDs
• Timestamps follow ISO 8601 format

Response format

Successful responses return data in a data wrapper. List endpoints include pagination metadata:

{
  "data": [ ... ],
  "meta": {
    "page": 1,
    "per_page": 25,
    "total": 142,
    "has_more": true
  }
}

Single-resource endpoints return:

{
  "data": { ... }
}

Pagination

List endpoints support page-based pagination with two query parameters:

Errors

Errors follow the RFC 7807 Problem Details format:

{
  "type": "https://api.nextsds.com/errors/not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "SDS document with id '...' was not found"
}

Rate limiting

The API enforces rate limits per API key. If you exceed the limit, you'll receive a 429 Too Many Requests response. Include reasonable delays between bulk operations.

Available endpoints