DeedPlotter AI is now BoundaryLogic. Read the story

Authentication

API key authentication with the x-api-key header, 401 causes, and key handling.

Availability: Arranged through sales

The BoundaryLogic API authenticates every request with an API key passed in the x-api-key header. Your key arrives with your access materials; the API is served from api.boundarylogic.com.

Making authenticated requests

Include the key on every request:

curl -H "x-api-key: YOUR_API_KEY" 
  https://api.boundarylogic.com/projects

When a request returns 401

  • The x-api-key header is missing.
  • The key value is wrong or incomplete.
  • The key has been deactivated or rotated.

Key handling

  • Store keys in environment variables or a secrets manager, never in code or version control.
  • Use separate keys for development and production environments.
  • Rotation issues a new key before the old one is retired.

If a key checks out and 401 persists, or you need a rotation, support@boundarylogic.com reaches the team.

Still stuck?

If you cannot find an answer here, our team is glad to help.