Properties
| Name | Type | Description |
|---|---|---|
| marketplaceOrderId | string | String that indicates the order's ID in the marketplace. |
| marketplaceOrderStatus | string | Required field including a string with the order’s status in the marketplace. If you send an order with the status APPROVED to integrate, our service will automatically try to advance its status in VT |
| connectorName | string | String with the identifier code of the connector responsible for the order. This field is optional if the connector uses the [App Template](https://developers.vtex.com/vtex-rest-api/docs/external-mark |
| connectorEndpoint | string | String with the connector's base endpoint that will receive notifications about the orders processing results, as well as status updates from VTEX OMS. This field does not accept query strings. You ca |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/UpdateOrderStatusRequest",
"title": "UpdateOrderStatusRequest",
"required": [
"marketplaceOrderId",
"marketplaceOrderStatus",
"connectorName",
"connectorEndpoint"
],
"type": "object",
"properties": {
"marketplaceOrderId": {
"type": "string",
"description": "String that indicates the order's ID in the marketplace.",
"example": "7e62fcd3-827b-400d-be8a-f050a79c4976"
},
"marketplaceOrderStatus": {
"type": "string",
"title": "marketplaceOrderStatus",
"description": "Required field including a string with the order\u2019s status in the marketplace. If you send an order with the status APPROVED to integrate, our service will automatically try to advance its status in VTEX after integrating it. This field accepts the following values: \n\n- `new` \n\n- `approved`.",
"example": "new"
},
"connectorName": {
"type": "string",
"title": "connectorName",
"description": "String with the identifier code of the connector responsible for the order. \n\nThis field is optional if the connector uses the [App Template](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-app-template) and authenticates on our request via `VtexIdclientAutCookie`. \n\nIt is required if the connector is native or does not use the App Template.",
"example": "connectorName"
},
"connectorEndpoint": {
"type": "string",
"title": "connectorEndpoint",
"description": "String with the connector's base endpoint that will receive notifications about the orders processing results, as well as status updates from VTEX OMS. This field does not accept query strings. You can use the models below: \n\n- `https://{{externalconnector}}.com` \n\n- `https://{{externalconnector.com}}/api/vtex` if you additionaly want to send a relative URL with the endpoint. \n\nThis field is optional if the connector uses the [App Template](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-app-template) and authenticates on our request via `VtexIdclientAutCookie`. \n\nIt is required if the connector is native or does not use the App Template.",
"example": "https://{{externalconnector.com}}/api/vtex"
}
},
"example": {
"marketplaceOrderId": "{{$guid}}",
"marketplaceOrderStatus": "APPROVED",
"connectorName": "Skyhub",
"connectorEndpoint": "https://connector-endpoint.com/api/vtex"
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/vtex-updateorderstatusrequest"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.