Documentation REST API

REST API

Provisioned access

Authenticate every request with a user access token.

REST authorization combines a verified user identity with active organization membership and product access.

Bearer authentication

Send the access token in the Authorization header. Tokens are audience-bound and should be treated as credentials.

http 
Authorization: Bearer $ENJOYABLE_ACCESS_TOKEN

Authentication and identity

Send a bearer access token and resolve the authenticated application user.

shell 
curl --request GET "https://api.enjoyable.work/v1/me" \
  --header "Authorization: Bearer $ENJOYABLE_ACCESS_TOKEN"

Credential availability

Do not invent or reuse an API key

There is no public API-key creation workflow today. Provisioned integrations receive an approved authentication path; browser session storage is not a developer credential source.

  • Never put an access token in source control, screenshots, support tickets, or documentation examples.
  • Use the token only with https://api.enjoyable.work and the intended audience.
  • A 404 can intentionally conceal an organization the caller is not permitted to see.
Documentation