Nexla Access Control API
Operations for managing access control to resources
Nexla Access Control API is one of 72 APIs that Nexla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Access Control. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 48 operations across 12 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://{nexla-api-host}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 5
Nexla Access Control API declares
5 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (NexlaSessionToken).
An API key is passed in the query as api_key (NexlaApiKeyQuery).
It accepts HTTP basic authentication (NexlaApiKeyHeader).
It accepts HTTP basic authentication (basicAuth).
It accepts HTTP bearer tokens (JWT) (GoogleSSOToken).
By default, every request must be authenticated.
NexlaSessionToken— The first step in calling the Nexla API or Nexla CLI is to fetch a Session access token by logging on to your Nexla UI instance. This ensures that your authent…NexlaApiKeyQuery— Important: Never share your API keys. Keep them guarded and secure. If you think the key has been compromised, you can rotate the API key by calling relevant A…NexlaApiKeyHeader— Important: Never share your API keys. Keep them guarded and secure. If you think the key has been compromised, you can rotate the API key by calling relevant A…GoogleSSOToken— The token that is used when logging into Nexla via Google SSO.
Paths & Operations 48
Across 12 paths, the API surfaces 48 operations — 12 DELETE, 12 GET, 12 POST, 12 PUT. Each is listed below with its method, path, parameters, and response codes.
Operations for managing access control to resources
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are RequestUserAccessor (4 properties), ResponseOrgAccessor (3 properties), ResponseUserAccessor (2 properties), RequestOrgAccessor (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Nexla 12
Other APIs Nexla publishes across the network.
This is an independent, third-party profile of Nexla Access Control API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.