Authentication

The Luqra Now API uses Bearer token authentication with organization-level API keys. Luqra account administrator will provide you with your organization's API key. Every request must include a valid API key in the Authorization header.

API key types

TypePrefixPurpose
Sandboxluqra-now.org.testSandbox payments and testing
Productionluqra-now.org.liveLive payment processing

Making authenticated requests

Include your API key as a Bearer token:

curl https://staging.api.now.luqra.com/v1/contacts/?originatorId=ORIGINATOR_ID \
  -H "Authorization: Bearer luqra-now.org.test.YOUR_API_KEY"

Key management

API keys are provisioned by your Luqra account administrator. Contact your admin to obtain or rotate keys.

Note -- The full API key is provided but not stored by Luqra. Store it securely; it cannot be retrieved later.

Error responses

Invalid or missing authentication returns a 401 Unauthorized response:

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Invalid API key"
  }
}

Possible messages vary by cause:

CauseMessage
No token providedMissing or invalid Authorization header. Expected: Bearer <api_key>
Key not foundInvalid API key
Key revokedAPI key has been revoked
Key expiredAPI key has expired

A key that is valid but is not an organization key returns 403 Forbidden instead, with the message This key type cannot be used on organization endpoints. Organization keys have the form luqra-now.org.{env}.*.

Authentication runs before the endpoint's own logic, so both responses -- along with the retry-safe 503 returned when the key lookup cannot reach its database -- are possible on every /v1 endpoint. See Errors for the full reference.