How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nexla Marketplace API

Operations for managing the marketplace domains and items.

Nexla Marketplace API is one of 72 APIs that Nexla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Marketplace. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 13 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{nexla-api-host}.

13 operations 5 paths 6 schemas 2 DELETE5 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://dataops.nexla.io/nexla-api
Authentication
HTTP Bearer, API Key, HTTP Basic, HTTP Basic, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 5

Nexla Marketplace 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 13

Across 5 paths, the API surfaces 13 operations — 2 DELETE, 5 GET, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Marketplace 13

Operations for managing the marketplace domains and items.

GET
/marketplace/domains
Get marketplace domains.
get_domains 1 param → 200403
POST
/marketplace/domains
Create marketplace domains.
create_domains 1 param body → 200401403
GET
/marketplace/domains/for_org
Get marketplace domains for organization.
get_domains_for_org 2 params → 200403
GET
/marketplace/domains/{domain_id}
Get a single marketplace domain.
get_domain 2 params → 200403
PUT
/marketplace/domains/{domain_id}
Update a single marketplace domain.
update_domain 2 params body → 200401403
POST
/marketplace/domains/{domain_id}
Create a single marketplace domain.
create_domain 1 param body → 200401403
DELETE
/marketplace/domains/{domain_id}
Delete a single marketplace domain.
delete_domain 2 params → 200401403
GET
/marketplace/domains/{domain_id}/items
Get marketplace items for a domain.
get_domain_items 2 params → 200403
POST
/marketplace/domains/{domain_id}/items
Create a marketplace item for a domain.
create_domain_item 2 params body → 200401403
GET
/marketplace/domains/{domain_id}/custodians
Get custodians for a marketplace domain.
get_domain_custodians 2 params → 200401403
PUT
/marketplace/domains/{domain_id}/custodians
Update custodians for a marketplace domain.
update_domain_custodians 2 params body → 200401403
POST
/marketplace/domains/{domain_id}/custodians
Add custodians to a marketplace domain.
add_domain_custodians 2 params body → 200401403
DELETE
/marketplace/domains/{domain_id}/custodians
Remove custodians from a marketplace domain.
remove_domain_custodians 2 params body → 200401403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are MarketplaceDomain (8 properties), MarketplaceDomainCreate (6 properties), MarketplaceDomainsItem (6 properties), MarketplaceDomainsItemCreate (3 properties). Each schema is shown below with its type and property counts.

MarketplaceDomain
object
8 properties
MarketplaceDomainsItem
object
6 properties
MarketplaceDomainsItemCreate
object
3 properties
CustodiansPayload
array
MarketplaceDomainCreate
object
6 properties
CustodiansResponse
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nexla-marketplace-api-openapi.yml Raw ↑

Other APIs Nexla publishes across the network.

Nexla Access Control API
Nexla Approval Requests API
Nexla Async Tasks API
Nexla Audit Logs API
Nexla Bulk Evaluation API
Nexla Bulk Query API
Nexla Clear Dataset Cache API
Nexla Clear Token Cache API
Nexla Code API
Nexla Code Containers API
Nexla Credential Mappings API
Nexla Credentials API
Where this information came from

This is an independent, third-party profile of Nexla Marketplace 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.