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

Convert Section Versions API

Convert Experience's Versions provides API to update Versions inside an experience's Section

Convert Section Versions API is one of 33 APIs that Convert publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Section Versions. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 3 base URLs: https://api.convert.com/api/v2, https://apidev.convert.com/api/v2, http://apidev.convert.com:5000/api/v2.

3 operations 3 paths 42 schemas 1 DELETE2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.convert.com/api/v2
Authentication
API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Convert Section Versions API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (requestSigning). It accepts HTTP bearer tokens (secretKey). An API key is passed in the cookie as sid (cookieAuthentication).

  • requestSigning — See [API Key Authentication](tag/API-KEY-Authentication) for more information.
  • secretKey — See [API Key Authentication](tag/API-KEY-Authentication) for more information.
  • cookieAuthentication — Cookie authentication is used against Convert's own IdentityProvider or third party identity providers and is described more in the "[Cookie Authentication](ta…

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 DELETE, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Section Versions 3

Convert Experience's Versions provides API to update Versions inside an experience's Section

POST
/accounts/{account_id}/projects/{project_id}/experiences/{experience_id}/sections/{section_id}/versions/add
Add a new version to an MVT section
addExperienceSectionVersion 6 params body → 201default
POST
/accounts/{account_id}/projects/{project_id}/experiences/{experience_id}/sections/{section_id}/versions/{version_id}/update
Update a version within an MVT section
updateExperienceSectionVersion 7 params body → 200default
DELETE
/accounts/{account_id}/projects/{project_id}/experiences/{experience_id}/sections/{section_id}/versions/{version_id}/delete
Delete a version from an MVT section
deleteExperienceSectionVersion 5 params → 200default

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are ErrorData (3 properties), BaseSectionVersion (3 properties), ExperienceChangeBase (2 properties), SuccessData (2 properties). Each schema is shown below with its type and property counts.

UpdateSectionVersionRequestData
ExperienceChangeRichStructureDataBase
object
Defines a complex change, often involving multiple DOM manipulations or structured data, typically generated by advanced Visual Editor interactions or specific…
ExperienceChangeId
object
Represents the unique identifier of an existing change within an experience variation. Used when updating or referencing a specific change.
1 property 1 required
ExperienceChangeDefaultCodeDataAdd
object
Data for creating a new 'defaultCode' type change.
CreateSectionVersionRequestData
ExperienceChangeRichStructureData
object
Represents a 'richStructure' type change, including its system-assigned ID.
ExperienceChangeBase
object
The fundamental structure representing a single modification applied within an experience's variation. The specific content and behavior of the change are dete…
2 properties
ExperienceChangeFullStackFeatureUpdate
object
Data for updating an existing 'fullStackFeature' type change, identified by its id.
ErrorData
object
3 properties
ExperienceSectionVersionResponseData
object
Response containing the details of a single MVT section version.
1 property
ExperienceChangeDefaultRedirectData
object
Represents a 'defaultRedirect' type change, including its system-assigned ID.
ExperienceChangeFullStackFeatureAdd
object
Data for creating a new 'fullStackFeature' type change.
ExperienceChangeAdd
Data structure for adding a new change to an experience variation. The id field is omitted as it will be assigned upon creation.
SectionVersion
ExperienceSectionVersionIncludeFields
string
ExperienceChangeDefaultCodeMultipageData
object
Represents a 'defaultCodeMultipage' type change, including its system-assigned ID.
ExperienceChangeDefaultCodeMultipageDataBase
object
Defines a standard code-based change that applies to a specific page within a Multi-page Funnel experiment. This allows different code (CSS, JS) to be applied…
ConcurrencyKey
string
A server-generated hash that represents the object's state at the time of retrieval. When included in an update request, the operation will only succeed if the…
ExperienceChangeDefaultCodeDataUpdate
object
Data for updating an existing 'defaultCode' type change, identified by its id.
ExperienceChangeDefaultRedirectDataAdd
object
Data for creating a new 'defaultRedirect' type change.
ExperienceChangeRichStructureDataAdd
object
Data for creating a new 'richStructure' type change.
ExperienceChangeFullStackFeature
object
Represents a 'fullStackFeature' type change, including its system-assigned ID.
ExperienceChangeCustomCodeDataUpdate
object
Data for updating an existing 'customCode' type change, identified by its id.
ExperienceChangeDefaultCodeMultipageDataAdd
object
Data for creating a new 'defaultCodeMultipage' type change.
ExperienceChangeCustomCodeDataAdd
object
Data for creating a new 'customCode' type change.
ExperienceChangeDefaultCodeDataBase
object
Defines a standard code-based change, typically generated by the Visual Editor for modifications like text replacement, style changes, or element removal. It c…
ExperienceChangeUpdate
Data structure for updating an existing change within an experience variation. Requires the id of the change to be modified.
BaseSectionVersion
object
3 properties
ExperienceChangeDefaultRedirectDataBase
object
Defines a URL redirect, typically used in Split URL experiments. It specifies how to match an original URL and construct the URL for the variation page.
ExperienceChangeIdReadOnly
object
Represents the unique identifier of a change, typically when returned by the API after creation or in a list.
1 property
ExperienceChangeFullStackFeatureBase
object
Defines a change for a Full Stack experiment that involves enabling or configuring a specific 'Feature' and its variables for this variation.
ExperienceChange
Represents a single, specific modification applied as part of an experience's variation. The exact structure and content depend on the type of change.
ExperienceSectionVersionExpandFields
string
ExperienceChangeDefaultRedirectDataUpdate
object
Data for updating an existing 'defaultRedirect' type change, identified by its id.
ExperienceChangeDefaultCodeMultipageDataUpdate
object
Data for updating an existing 'defaultCodeMultipage' type change, identified by its id.
ExperienceChangeRichStructureDataUpdate
object
Data for updating an existing 'richStructure' type change, identified by its id.
SectionVersionUpdate
ExperienceChangeCustomCodeDataBase
object
Defines a change applied purely through custom-written CSS and/or JavaScript code, bypassing the Visual Editor's generated code. This offers maximum flexibilit…
SectionVersionCreate
ExperienceChangeCustomCodeData
object
Represents a 'customCode' type change, including its system-assigned ID.
ExperienceChangeDefaultCodeData
object
Represents a 'defaultCode' type change, including its system-assigned ID.
SuccessData
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

convert-section-versions-api-openapi.yml Raw ↑

Other APIs Convert publishes across the network.

Convert Experiences REST API v2
Convert Accounts API
Convert AI content API
Convert API Keys API
Convert Audiences API
Convert Bulk API
Convert Cdn Images API
Convert Collaborators API
Convert Cookie Authentication API
Convert Domains API
Convert Experience Sections API
Convert Experience Variations API
Where this information came from

This is an independent, third-party profile of Convert Section Versions 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.