01.software Docs

Update Events

Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.

All HTTP operations
PATCH
/api/events/{id}

Update a document by ID. Server-side code should prefer createServerClient from @01.software/sdk. Direct REST writes require a publishable key and a server Bearer token.

Authorization

publishableKeybearerAuth
headerX-Publishable-Key<token>

Tenant publishable key for authentication (sent via X-Publishable-Key header)

headerAuthorizationBearer <token>

Public integration credentials: verified opaque sk01_ secret key or pat01_ personal access token; operation policy and read/write scopes still apply. These credentials are not Customer JWTs.

Path Parameters

id*string

Document ID

Request Body

application/json
  1. body

Collection payload. Field names are tenant and collection specific; inspect the tenant-aware schema through MCP get-collection-schema before sending writes.

[key: string]?any

Response Body

Updated Events

application/json
  1. response
message?string
doc*

Collection document. Use MCP get-collection-schema for tenant-aware field details before generating typed application code.

Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.

Example Request
curl -X PATCH 'https://api.01.software/api/events/string' \  -H 'Content-Type: application/json' \  -d '{  "status": "published"}'
Example Response
{  "message": "string",  "doc": {    "id": "string",    "createdAt": "2019-08-24T14:15:22Z",    "updatedAt": "2019-08-24T14:15:22Z"  }}