Salfio
APIReference

Create a manual activity (Stubbed — SAL-230 follow-up)

**Stubbed in v1.0.** Returns `200 { data: null, meta: {} }` without side effects. Full implementation requires an `archived_at` column on the conversations table plus the source/operation matrix from the v1.0 spec — tracked as a SAL-230 follow-up.

POST
/clients/{clientId}/activities

Authorization

bearerAuth
AuthorizationBearer <token>

Salfio API tokens start with the literal prefix sk_live_ followed by 32 base62 characters (≈190 bits of entropy). Tokens are hashed at rest with argon2id and shown to the user only once at creation.

In: header

Path Parameters

clientId*string
Formatuuid

Response Body

application/json

application/json

curl -X POST "https://api.salfio.com/v1/clients/497f6eca-6276-4993-bfeb-53cbbbba6f08/activities"
{
  "data": null,
  "meta": {}
}
{
  "error": {
    "code": "unauthorized",
    "message": "Authentication required"
  }
}

List activities for a client

Returns the client's activities (emails, calls, meetings, notes) ordered by most-recent first. Offset-based pagination via an opaque `cursor` string (decoded internally). Supported query params today: `limit`, `cursor`, `type`. The spec's additional filters (`source`, `from`, `to`, `includeArchived`) are validated but currently have no effect — archival filtering needs the `archived_at` column on the conversations table, tracked as a follow-up. List responses omit `content` for cost reasons — fetch the single-resource endpoint to get message bodies.

Get an activity

Fetch a single activity by UUID. The response includes the full concatenated message content, truncated at 10 KiB. Cross-tenant lookups and activities that don't belong to the path's client return `404 not_found`.