Virtual URL API
Publish your own REST endpoints without code, and generate an OpenAPI document for them.
- Service
- Workflow engine
- Base path
https://your-workflow-host- Authentication
- Bearer token and context headers.
A Virtual URL maps a method and path template, such as GET /vendors/{id}, to ordered steps (select, insert, update, delete) on your entities, with an output shape. Calls run under the caller's own permissions. Ask us to enable Virtual URLs on your environment.
/api/v1/virtualurls/upsertCreate or update a Virtual URL
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/virtualurlsList Virtual URLs
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/virtualurls/{id}Delete a Virtual URL
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/virtualurls/openapiGet the app's OpenAPI 3.1 document
Use it to generate a typed client for your endpoints.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/vu/{path}Call a Virtual URL
GET, POST, PUT and DELETE are supported. Send an X-Release-Id header to pin the call to a release. Update and delete steps refuse to run without criteria.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.