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 Transforms API

Operations for managing reusable attribute and record transforms.

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

Tagged areas include Transforms. 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 7 paths, and defines 18 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 7 paths 18 schemas 2 DELETE6 GET3 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 Transforms 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 7 paths, the API surfaces 13 operations — 2 DELETE, 6 GET, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Transforms 13

Operations for managing reusable attribute and record transforms.

GET
/transforms
Get all Reusable Record Transforms
get_reusable_record_transforms 1 param → 200403
POST
/transforms
Create a Reusable Record Transform
create_reusable_record_transform body → 200401403
GET
/transforms/{transform_id}
Get A Reusable Record Transform
get_reusable_record_transform 2 params → 200401403404
PUT
/transforms/{transform_id}
Update Reusable Record Transform
update_reusable_record_transform 2 params body → 200401403404
DELETE
/transforms/{transform_id}
Delete a Reusable Record Transform
delete_reusable_record_transform 2 params → 200401403404
POST
/transforms/{transform_id}/copy
Copy a Reusable Record Transform
copy_transform 2 params → 200401403404
GET
/transforms/public
Get all Public Reusable Record Transforms
get_public_reusable_record_transforms 1 param → 200401403
GET
/attribute_transforms
Get all Attribute Transforms
get_attribute_transforms 1 param → 200403
POST
/attribute_transforms
Create an Attribute Transform
create_attribute_transform body → 200401403
GET
/attribute_transforms/{attribute_transform_id}
Get Attribute Transform by ID
get_attribute_transform 2 params → 200401403404
PUT
/attribute_transforms/{attribute_transform_id}
Update Attribute Transform
update_attribute_transform 2 params body → 200401403404
DELETE
/attribute_transforms/{attribute_transform_id}
Delete an Attribute Transform
delete_attribute_transform 2 params → 200401403404
GET
/attribute_transforms/public
Get all Public Attribute Transforms
get_public_attribute_transforms 1 param → 200401403

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are CodeContainer (24 properties), Transform (22 properties), AttributeTransform (22 properties), CodeContainerMutable (12 properties). Each schema is shown below with its type and property counts.

code_containers_ResourceType
string
The type of resource that this code container is to be used for. - transform: For user defined code that is used in a Nexset transform. - aifunction: For user…
CodeContainer
object
24 properties
TransformMutable
object
9 properties 6 required
AttributeTransform
object
22 properties
UserSimplified
object
4 properties
CodeType
string
AttributeTransformMutable
object
9 properties 6 required
code_containers_CodeType
string
CodeContainerMutable
object
12 properties 6 required
Transform
object
22 properties
ResourceType
string
attribute_transforms_CodeType
string
OutputType
string
code_containers_OutputType
string
The type of output that this code container produces. - record: Produces a full Nexset record. Used only when the code container is used to modify a Nexset, i.…
AccessRoles
array
This property reflects all the permissions the user/team/organization has to this resource. 1. collaborator: The user/team/organization can view the resource b…
OrgSimplified
object
6 properties
DataCredentialBrief
object
5 properties
attribute_transforms_OutputType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nexla-transforms-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 Transforms 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.