ENA Feedback

API Overview & Authentication

Base URL, authentication, rate limiting, error codes, and conventions for the Enafeedback REST API.

Last updated on

The Enafeedback REST API lets you read and write data programmatically. Use it to build custom integrations, extract data into your data warehouse, or automate workspace management tasks.

Base URL

https://api.enafeedback.com/api

All endpoints are prefixed with /api. Requests must use HTTPS.

Authentication

All API requests require a Bearer token. See Authentication for how to obtain a token.

Authorization: Bearer efa_sk_your_token_here

Request format

  • Content-Typeapplication/json for request bodies.
  • Acceptapplication/json (default; all responses are JSON).
  • Dates — ISO 8601 with timezone, e.g. 2026-06-07T10:30:00Z.

Response format

Successful responses return HTTP 2xx with a JSON body. List endpoints return paginated responses:

{
  "data": [...],
  "meta": {
    "total": 284,
    "page": 1,
    "per_page": 20,
    "pages": 15
  }
}

Single-resource responses return the resource object directly.

Pagination

Add ?page=2&per_page=50 to any list endpoint. Maximum per_page is 100.

Filtering & sorting

Most list endpoints accept filter query parameters. Common ones:

ParameterExampleDescription
from2026-01-01T00:00:00ZStart of date range
to2026-06-30T23:59:59ZEnd of date range
location_idloc_abc123Filter by location
sortcreated_at:descSort field and direction

Error codes

HTTP statusMeaning
400 Bad RequestInvalid parameters or request body
401 UnauthorizedMissing or invalid Bearer token
403 ForbiddenValid token but insufficient permissions
404 Not FoundResource does not exist in this workspace
409 ConflictDuplicate resource or constraint violation
422 Unprocessable EntityValidation error (body has field-level errors)
429 Too Many RequestsRate limit exceeded
500 Internal Server ErrorUnexpected server error

Error responses have a consistent shape:

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Survey not found"
}

Rate limiting

1,000 requests per minute per workspace. See Authentication for header details.

Idempotency

POST requests that create resources are not idempotent by default. To prevent duplicate creation on retry, include an Idempotency-Key header with a unique string (UUID recommended). The same key within a 24-hour window returns the original response without creating a duplicate.

Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

API versioning

The current API version is v1 (implicit in the base URL). Breaking changes will be introduced with a new base URL path prefix (/api/v2). Non-breaking additions (new fields, new optional parameters) may be made without a version bump.

OpenAPI spec

The canonical OpenAPI 3.1 specification ships with this documentation site (openapi/enafeedback-api.yaml). Browse the interactive reference under REST API Reference, or import the YAML into Postman, Insomnia, or any OpenAPI-compatible client.

Generated endpoint pages stay in sync with the spec at build time. Propose changes via your account manager or support channel.